Software provider
•
0 likes•45 views
With your great business idea, you will need a good partner to help you create software. This presentation gives you a basic idea of what a software project is all about and how you can make a good decision in choosing your partner.
Report
Share
Report
Share
Download to read offline
Recommended
Agile foundation and agile myths
The document compares predictive and agile software development approaches. It outlines that predictive approaches rely on upfront planning and strict adherence to plans, which can be unrealistic given the inherent uncertainties in software projects. Agile approaches separate estimates from execution, focus on frequent delivery of working software, and emphasize adapting to changes and feedback. While myths exist that agile means no planning, documentation, commitments, processes, or roles like project managers, when applied properly agile can dramatically improve an organization's ability to deliver working software.
DevOps for Speed and Agility - DevOpsTO May 2014
How to increase agility and speed in your organization by applying DevOps principles. How to go faster and be more flexible to the needs of your business. Easy steps to reduce bottlenecks, release faster and with more confidence.
Improve visibility
Measure state
Minimize constraints
Improve collaboration
Enable action
Practice change
Focus
Automate
AdvanScrum: To Scrum and Beyond
This document introduces AdvanScrum, which suggests practical tools and techniques based on Scrum but with a new mindset. It describes 3 roles, 5 meetings, and 3 artifacts. It notes some alternative terminology used such as "Mission Manager" instead of "Product Owner" and "Iteration" instead of "Sprint." It emphasizes flexibility in using any tools or techniques and not making anything mandatory. The goal is to deliver improved increments every iteration while also improving self, team, and company.
Cas2010 to-track-defects-or-not-to-track-defects-that-is-the-question
This document discusses different perspectives on tracking defects in Agile development and proposes an alternative approach. It argues that defects should be treated like user stories with estimates and tests rather than using separate tracking tools. Within a sprint, any issues found should be visible on the task board as tests to be fixed. This maintains visibility while avoiding separate backlogs. The document shares a case study where this approach worked well but faced challenges with remote visibility and lack of automation. It concludes defects are best addressed by tracking tests, not bugs, and prioritizing visibility and automation.
Estimating and planning Agile projects
Estimating is hard to get right;
Why is estimating hard to get right?;
Why do we need to estimate;
Agile estimating and planning;
Determine the teams velocity;
Identify features and stories;
Define stories or features;
Planning Poker;
Agile Release Plan;
What if you don’t know the teams velocity?;
Estimating from ideal team structure;
The effect of rework;
Proposals and SOW’s;
Code Yellow: Helping Operations Top-Heavy Teams the Smart Way
All engineering teams run into trouble from time to time. Alert fatigue, caused by technical debt or a failure to plan for growth, can quickly burn out SREs, overloading both development and operations with reactive work. Layer in the potential for communication problems between teams, and we can find ourselves in a place so troublesome we cannot easily see a path out. At times like this, our natural instinct as reliability engineers is to double down and fight through the issues. Often, however, we need to step back, assess the situation, and ask for help to put the team back on the road to success.
We will look at the process for Code Yellow, the term we use for this process of “righting the ship”, and discuss how to identify teams that are struggling. Through a look at three separate experiences, we will examine some of the root causes, what steps were taken, and how the engineering organization as a whole supports the process.
Why Does (My) Monitoring Suck?
Monitoring services is easy, right? Set up a notification that goes out when a certain number increases past a certain threshold to let you know that there’s a problem. But if that’s the case, why are so many teams drowning in alerts and dreading their time on call? The reason is that we tend to monitor the wrong things: reactive alerts, metrics that we don’t completely understand how they impact our service, and capacity alerts. We look at our own view of the service and fail to consider that our customers have a different view.
Come learn to let go of what does not help, and explore how to monitor for what truly matters: what the customer sees. This starts with defining our agreements with our customers, continues through building applications intelligently and instrumenting all the things, and finishes with picking the right signals out of that instrumentation to generate alerts that are actionable, not ones that introduce confusion and noise. We will also touch on capacity planning, and how it should never wake you up. You’ll find it’s possible to assure that you meet your service level objectives while still maximizing your sleep level objectives.
Are we done yet?
This document discusses the importance of team charters and definitions of ready and done in Agile development. It defines key elements of a team charter such as goals, success criteria, constraints, and team rules/working agreements. It also explains what a definition of ready and definition of done are, providing examples of criteria that could be included in each. The document emphasizes that definitions of ready and done are not static and should be informed by the team's experience. It poses questions about why teams should create charters and who is accountable for ensuring teams follow their charters.
Recommended
Agile foundation and agile myths
The document compares predictive and agile software development approaches. It outlines that predictive approaches rely on upfront planning and strict adherence to plans, which can be unrealistic given the inherent uncertainties in software projects. Agile approaches separate estimates from execution, focus on frequent delivery of working software, and emphasize adapting to changes and feedback. While myths exist that agile means no planning, documentation, commitments, processes, or roles like project managers, when applied properly agile can dramatically improve an organization's ability to deliver working software.
DevOps for Speed and Agility - DevOpsTO May 2014
How to increase agility and speed in your organization by applying DevOps principles. How to go faster and be more flexible to the needs of your business. Easy steps to reduce bottlenecks, release faster and with more confidence.
Improve visibility
Measure state
Minimize constraints
Improve collaboration
Enable action
Practice change
Focus
Automate
AdvanScrum: To Scrum and Beyond
This document introduces AdvanScrum, which suggests practical tools and techniques based on Scrum but with a new mindset. It describes 3 roles, 5 meetings, and 3 artifacts. It notes some alternative terminology used such as "Mission Manager" instead of "Product Owner" and "Iteration" instead of "Sprint." It emphasizes flexibility in using any tools or techniques and not making anything mandatory. The goal is to deliver improved increments every iteration while also improving self, team, and company.
Cas2010 to-track-defects-or-not-to-track-defects-that-is-the-question
This document discusses different perspectives on tracking defects in Agile development and proposes an alternative approach. It argues that defects should be treated like user stories with estimates and tests rather than using separate tracking tools. Within a sprint, any issues found should be visible on the task board as tests to be fixed. This maintains visibility while avoiding separate backlogs. The document shares a case study where this approach worked well but faced challenges with remote visibility and lack of automation. It concludes defects are best addressed by tracking tests, not bugs, and prioritizing visibility and automation.
Estimating and planning Agile projects
Estimating is hard to get right;
Why is estimating hard to get right?;
Why do we need to estimate;
Agile estimating and planning;
Determine the teams velocity;
Identify features and stories;
Define stories or features;
Planning Poker;
Agile Release Plan;
What if you don’t know the teams velocity?;
Estimating from ideal team structure;
The effect of rework;
Proposals and SOW’s;
Code Yellow: Helping Operations Top-Heavy Teams the Smart Way
All engineering teams run into trouble from time to time. Alert fatigue, caused by technical debt or a failure to plan for growth, can quickly burn out SREs, overloading both development and operations with reactive work. Layer in the potential for communication problems between teams, and we can find ourselves in a place so troublesome we cannot easily see a path out. At times like this, our natural instinct as reliability engineers is to double down and fight through the issues. Often, however, we need to step back, assess the situation, and ask for help to put the team back on the road to success.
We will look at the process for Code Yellow, the term we use for this process of “righting the ship”, and discuss how to identify teams that are struggling. Through a look at three separate experiences, we will examine some of the root causes, what steps were taken, and how the engineering organization as a whole supports the process.
Why Does (My) Monitoring Suck?
Monitoring services is easy, right? Set up a notification that goes out when a certain number increases past a certain threshold to let you know that there’s a problem. But if that’s the case, why are so many teams drowning in alerts and dreading their time on call? The reason is that we tend to monitor the wrong things: reactive alerts, metrics that we don’t completely understand how they impact our service, and capacity alerts. We look at our own view of the service and fail to consider that our customers have a different view.
Come learn to let go of what does not help, and explore how to monitor for what truly matters: what the customer sees. This starts with defining our agreements with our customers, continues through building applications intelligently and instrumenting all the things, and finishes with picking the right signals out of that instrumentation to generate alerts that are actionable, not ones that introduce confusion and noise. We will also touch on capacity planning, and how it should never wake you up. You’ll find it’s possible to assure that you meet your service level objectives while still maximizing your sleep level objectives.
Are we done yet?
This document discusses the importance of team charters and definitions of ready and done in Agile development. It defines key elements of a team charter such as goals, success criteria, constraints, and team rules/working agreements. It also explains what a definition of ready and definition of done are, providing examples of criteria that could be included in each. The document emphasizes that definitions of ready and done are not static and should be informed by the team's experience. It poses questions about why teams should create charters and who is accountable for ensuring teams follow their charters.
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
The document discusses the use of Agile methodologies in AAA game development. It provides an overview of Agile principles and Scrum framework, including roles, ceremonies and artifacts. While some aspects of Scrum like cross-functional teams and customer collaboration do not directly apply to embedded game development teams, the speaker argues that an iterative approach, daily stand-ups, sprint planning and retrospectives can still benefit teams. The document cautions against adopting Agile practices without understanding how they apply specifically to one's environment or "cult-like" following.
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required
This document discusses predictability in workflows and queues. It begins by defining predictability and noting that predictable systems usually have reduced cycle times and variation. It then discusses how workflows can be viewed as chains of queues and how queues can impact cycle times, throughput, and motivation if allowed to grow too large. The document provides choices that can be made to influence queues, such as using push vs pull systems and prioritization methods. It also recommends monitoring queue size and cycle time ranges as leading indicators of predictability. The overall message is that managers have control over predictability by understanding and managing their queues.
19 creamer et workshop-agile2019-wash_pp_16-9_1
The document provides an agenda for a workshop on how to coach exploratory testing sessions. It covers basics of exploratory testing including obstacles, how to determine what to test, writing charters, and isolating and recording results. The agenda includes activities for writing charters, prioritizing them, and practicing exploratory testing in pairs with one participant testing and the other coaching. The roles of the coach and participant are defined. Ways to share results are also discussed.
APIdays Singapore 2019 - Building Applications in the Cloud: Best Practices F...
Building Applications in the Cloud: Best Practices From High-Performers, Christopher Skene, Head of Business Development, Platform.sh
Measuring DevOps Performance
What is the best way to measure DevOps performance? There are many ways that people have tried to measure productivity in software delivery in the past -- what works and what doesn’t? In this webinar, Dr. Nicole Forsgren and Robert Reeves will present some lessons learned about measuring software delivery and why it’s important. The webinar will also highlight the key factors driving DevOps performance and offer a preview to some of the challenges on the horizon.
Tune into this webinar to learn about:
Flaws in previous attempts to measure performance
What really matters (hint: focus on outcomes)
The four measures that are key to delivery performance
The *big* difference between high performers and the rest
Why maturity models don’t work
What high performers can do for their organizations
What challenges are up next in technology transformations… things like data, serverless, and security.
Collaboration Through Conflict - SFAA 2013
Session at South FL's first agile conference where we talked about the 5 sources of conflict and various tools to help your team navigate it for better collaboration
Continuous integration in large programs
This document discusses continuous integration in large programs. It defines continuous integration as a practice where team members integrate their work frequently, usually daily, and each integration is verified by automated builds. The document outlines some challenges of continuous integration in large, distributed teams working on multiple sub-products with different skills. It advocates for continuous testing and having rules for the team, and notes some achievements including one-click deploys, a single branch, reduced cycle times, and rarely needing rollbacks.
Site Redesign: When Hell Freezes Over Use a Blowtorch
The document discusses plans for redesigning a website. It emphasizes taking a phased, realistic approach in the formal proposal by addressing the current state, opportunities, goals, vision, and plan. Rogue tactics are encouraged to find an advocate for the project. The proposal should discuss resource needs and allocation. Success will be demonstrated through qualitative and quantitative measures like conversion rates, drop-off, bug fixes, and customer feedback. The redesign implemented a simpler, more consistent, efficient checkout process through layered updates. This improved the user experience and allowed further optimizations.
Actionable Agile Metrics
This document discusses actionable agile metrics including work in progress, cycle time, and throughput. It defines each metric and explains why they are useful for understanding process stability, predictability, and improvements. Visualizations like cumulative flow diagrams and scatter plots of cycle times can help teams identify patterns and anomalies to investigate. Analyzing metrics over time through run charts also supports monitoring trends and capacity planning. The key message is that these quantitative metrics can trigger process improvements when used to learn rather than assess teams.
Agile Fundamentals and Best Practices (with Trello)
This document provides an overview of agile fundamentals and best practices. It outlines key concepts of Scrum like the product owner, development team, and sprint process. It also describes agile practices such as sprint planning, getting user feedback, testing, and using Trello for project management. The document is intended to recap agile concepts for the author's team.
All You Want To About Kanban Before Doing Kanban Certification | AgileFever
AgileFever is a digital transformation consulting firm headquartered in Texas that provides Agile, DevOps, and Kanban training and coaching services globally. The presentation introduces Kanban, including its history starting in 1956 at a Toyota plant. It describes Kanban principles like limiting work in progress, managing flow, and implementing feedback loops. Key Kanban practices and events like daily stand-ups and retrospectives are also outlined. The presentation concludes with discussing common Kanban metrics like cycle time, work in progress, and throughput.
Overview of Site Reliability Engineering (SRE) & best practices
In any software organization, stability & innovation are always at loggerheads - the faster you move, the more things will break. This talk defines what SRE org looks like at high-tech organizations (Google, Uber).
Agile development makes elephants dance
This document discusses agile development and how it can help address issues with traditional waterfall development approaches. It provides an overview of agile principles from the Agile Manifesto, popular agile methodologies like Scrum and XP, and how agile practices emphasize iterative development, emergent requirements, frequent inspection/adaptation, and valuing individuals/interaction over processes. A real example is given of how adopting scrum helped turn around a failing project that was over budget and delivering poor quality.
Scrum and-xp-from-the-trenches 06 testing
This document discusses testing in Scrum projects. It cannot be avoided, but can be minimized. Putting testers in the Scrum team increases quality by having developers tested by experts. Doing less per sprint also increases quality. Acceptance testing may require its own phase after sprints. Prioritize fixing old bugs found before starting new work. Alleviate bottlenecks by increasing test automation, adding testers, or adjusting sprint length. True cross-functional teams share testing duties.
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...
Performance tests are not only an important instrument for understanding a system and its runtime environment. It is also essential in order to check stability and scalability – non-functional requirements that might be decisive for success. But won't my cloud hosting service scale for me as long as I can afford it? Yes, but… It only operates and scales resources. It won't automatically make your system fast, stable and scalable. This talk shows how such and comparable questions can be clarified with performance tests and how DevOps teams benefit from regular test practise.
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019
What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?
Summer Scrum Public
This document provides an overview of Scrum, an agile project management framework. It describes Scrum as a lightweight framework using iterative and incremental development approaches. The key Scrum components include roles like the Product Owner and Scrum Master, prioritized backlogs, sprints, and events like sprint planning and retrospectives. Benefits of Scrum include increased productivity, quality, and customer satisfaction compared to traditional waterfall models. Scrum enables flexibility and incorporating feedback throughout development rather than having a fixed plan.
Situational retrospectives
This document discusses situational retrospectives in Agile development. It provides an overview of different retrospective techniques that can be used depending on the situation, including pluses/deltas, silent writing, dot voting, starfish, Niko-niko calendar, team radar, 5 whys, draw me a picture, and future-spective. The document emphasizes that the right retrospective approach depends on factors like team performance and issues. It also outlines best practices for running effective retrospectives.
Q&A with Scrum Masters
Scrum masters were asked about common team issues and ways to address them. They recommended finding collaboration tools to enforce documentation, processes, and transparency. Communication through various channels like Slack, email and Jira was also stressed. Flexibility was advised as Agile approaches will differ based on team and project. Tracking work through tools like Jira and ensuring dedicated roles helps manage multiple teams and methodologies. Questions from attendees focused on tracking metrics in Kanban, interacting with QA, and organizing and splitting up work in Jira.
Pushing the Bottleneck: Predicting and Addressing the Next, Next Thing
Finding bottlenecks in our software delivery processes is often pretty easy. But once we squash one bottleneck, another team becomes the limiting factor. This presentation looks how bottlenecks work, and how to predict the next bottleneck you'll need to work on.
Webinar: Demonstrating Business Value for DevOps & Continuous Delivery
The document discusses DevOps and continuous delivery. It begins with an introduction and agenda. It then discusses transforming IT operations for greater business value, challenges for businesses and IT that DevOps addresses, what DevOps is in terms of people, processes, and tools. It discusses continuous delivery and provides examples of goals and metrics for DevOps initiatives like release frequency, throughput time, and idle time. Finally, it discusses how DevOps tools can work with other tools and processes.
Continuous Delivery
Continuous Delivery
What it takes to move to continuous integration and Continuous Delivery/Deployment model.
www.scmtechblog.net
More Related Content
What's hot
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
The document discusses the use of Agile methodologies in AAA game development. It provides an overview of Agile principles and Scrum framework, including roles, ceremonies and artifacts. While some aspects of Scrum like cross-functional teams and customer collaboration do not directly apply to embedded game development teams, the speaker argues that an iterative approach, daily stand-ups, sprint planning and retrospectives can still benefit teams. The document cautions against adopting Agile practices without understanding how they apply specifically to one's environment or "cult-like" following.
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required
This document discusses predictability in workflows and queues. It begins by defining predictability and noting that predictable systems usually have reduced cycle times and variation. It then discusses how workflows can be viewed as chains of queues and how queues can impact cycle times, throughput, and motivation if allowed to grow too large. The document provides choices that can be made to influence queues, such as using push vs pull systems and prioritization methods. It also recommends monitoring queue size and cycle time ranges as leading indicators of predictability. The overall message is that managers have control over predictability by understanding and managing their queues.
19 creamer et workshop-agile2019-wash_pp_16-9_1
The document provides an agenda for a workshop on how to coach exploratory testing sessions. It covers basics of exploratory testing including obstacles, how to determine what to test, writing charters, and isolating and recording results. The agenda includes activities for writing charters, prioritizing them, and practicing exploratory testing in pairs with one participant testing and the other coaching. The roles of the coach and participant are defined. Ways to share results are also discussed.
APIdays Singapore 2019 - Building Applications in the Cloud: Best Practices F...
Building Applications in the Cloud: Best Practices From High-Performers, Christopher Skene, Head of Business Development, Platform.sh
Measuring DevOps Performance
What is the best way to measure DevOps performance? There are many ways that people have tried to measure productivity in software delivery in the past -- what works and what doesn’t? In this webinar, Dr. Nicole Forsgren and Robert Reeves will present some lessons learned about measuring software delivery and why it’s important. The webinar will also highlight the key factors driving DevOps performance and offer a preview to some of the challenges on the horizon.
Tune into this webinar to learn about:
Flaws in previous attempts to measure performance
What really matters (hint: focus on outcomes)
The four measures that are key to delivery performance
The *big* difference between high performers and the rest
Why maturity models don’t work
What high performers can do for their organizations
What challenges are up next in technology transformations… things like data, serverless, and security.
Collaboration Through Conflict - SFAA 2013
Session at South FL's first agile conference where we talked about the 5 sources of conflict and various tools to help your team navigate it for better collaboration
Continuous integration in large programs
This document discusses continuous integration in large programs. It defines continuous integration as a practice where team members integrate their work frequently, usually daily, and each integration is verified by automated builds. The document outlines some challenges of continuous integration in large, distributed teams working on multiple sub-products with different skills. It advocates for continuous testing and having rules for the team, and notes some achievements including one-click deploys, a single branch, reduced cycle times, and rarely needing rollbacks.
Site Redesign: When Hell Freezes Over Use a Blowtorch
The document discusses plans for redesigning a website. It emphasizes taking a phased, realistic approach in the formal proposal by addressing the current state, opportunities, goals, vision, and plan. Rogue tactics are encouraged to find an advocate for the project. The proposal should discuss resource needs and allocation. Success will be demonstrated through qualitative and quantitative measures like conversion rates, drop-off, bug fixes, and customer feedback. The redesign implemented a simpler, more consistent, efficient checkout process through layered updates. This improved the user experience and allowed further optimizations.
Actionable Agile Metrics
This document discusses actionable agile metrics including work in progress, cycle time, and throughput. It defines each metric and explains why they are useful for understanding process stability, predictability, and improvements. Visualizations like cumulative flow diagrams and scatter plots of cycle times can help teams identify patterns and anomalies to investigate. Analyzing metrics over time through run charts also supports monitoring trends and capacity planning. The key message is that these quantitative metrics can trigger process improvements when used to learn rather than assess teams.
Agile Fundamentals and Best Practices (with Trello)
This document provides an overview of agile fundamentals and best practices. It outlines key concepts of Scrum like the product owner, development team, and sprint process. It also describes agile practices such as sprint planning, getting user feedback, testing, and using Trello for project management. The document is intended to recap agile concepts for the author's team.
All You Want To About Kanban Before Doing Kanban Certification | AgileFever
AgileFever is a digital transformation consulting firm headquartered in Texas that provides Agile, DevOps, and Kanban training and coaching services globally. The presentation introduces Kanban, including its history starting in 1956 at a Toyota plant. It describes Kanban principles like limiting work in progress, managing flow, and implementing feedback loops. Key Kanban practices and events like daily stand-ups and retrospectives are also outlined. The presentation concludes with discussing common Kanban metrics like cycle time, work in progress, and throughput.
Overview of Site Reliability Engineering (SRE) & best practices
In any software organization, stability & innovation are always at loggerheads - the faster you move, the more things will break. This talk defines what SRE org looks like at high-tech organizations (Google, Uber).
Agile development makes elephants dance
This document discusses agile development and how it can help address issues with traditional waterfall development approaches. It provides an overview of agile principles from the Agile Manifesto, popular agile methodologies like Scrum and XP, and how agile practices emphasize iterative development, emergent requirements, frequent inspection/adaptation, and valuing individuals/interaction over processes. A real example is given of how adopting scrum helped turn around a failing project that was over budget and delivering poor quality.
Scrum and-xp-from-the-trenches 06 testing
This document discusses testing in Scrum projects. It cannot be avoided, but can be minimized. Putting testers in the Scrum team increases quality by having developers tested by experts. Doing less per sprint also increases quality. Acceptance testing may require its own phase after sprints. Prioritize fixing old bugs found before starting new work. Alleviate bottlenecks by increasing test automation, adding testers, or adjusting sprint length. True cross-functional teams share testing duties.
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...
Performance tests are not only an important instrument for understanding a system and its runtime environment. It is also essential in order to check stability and scalability – non-functional requirements that might be decisive for success. But won't my cloud hosting service scale for me as long as I can afford it? Yes, but… It only operates and scales resources. It won't automatically make your system fast, stable and scalable. This talk shows how such and comparable questions can be clarified with performance tests and how DevOps teams benefit from regular test practise.
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019
What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?
Summer Scrum Public
This document provides an overview of Scrum, an agile project management framework. It describes Scrum as a lightweight framework using iterative and incremental development approaches. The key Scrum components include roles like the Product Owner and Scrum Master, prioritized backlogs, sprints, and events like sprint planning and retrospectives. Benefits of Scrum include increased productivity, quality, and customer satisfaction compared to traditional waterfall models. Scrum enables flexibility and incorporating feedback throughout development rather than having a fixed plan.
Situational retrospectives
This document discusses situational retrospectives in Agile development. It provides an overview of different retrospective techniques that can be used depending on the situation, including pluses/deltas, silent writing, dot voting, starfish, Niko-niko calendar, team radar, 5 whys, draw me a picture, and future-spective. The document emphasizes that the right retrospective approach depends on factors like team performance and issues. It also outlines best practices for running effective retrospectives.
Q&A with Scrum Masters
Scrum masters were asked about common team issues and ways to address them. They recommended finding collaboration tools to enforce documentation, processes, and transparency. Communication through various channels like Slack, email and Jira was also stressed. Flexibility was advised as Agile approaches will differ based on team and project. Tracking work through tools like Jira and ensuring dedicated roles helps manage multiple teams and methodologies. Questions from attendees focused on tracking metrics in Kanban, interacting with QA, and organizing and splitting up work in Jira.
Pushing the Bottleneck: Predicting and Addressing the Next, Next Thing
Finding bottlenecks in our software delivery processes is often pretty easy. But once we squash one bottleneck, another team becomes the limiting factor. This presentation looks how bottlenecks work, and how to predict the next bottleneck you'll need to work on.
What's hot (20)
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
Михайло Кравець “Використання Agile методології в AAA розробці ігор” GameDev ...
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required
DOES SFO 2016 San Francisco - Julia Wester - Predictability: No Magic Required
APIdays Singapore 2019 - Building Applications in the Cloud: Best Practices F...
APIdays Singapore 2019 - Building Applications in the Cloud: Best Practices F...
Site Redesign: When Hell Freezes Over Use a Blowtorch
Site Redesign: When Hell Freezes Over Use a Blowtorch
Agile Fundamentals and Best Practices (with Trello)
Agile Fundamentals and Best Practices (with Trello)
All You Want To About Kanban Before Doing Kanban Certification | AgileFever
All You Want To About Kanban Before Doing Kanban Certification | AgileFever
Overview of Site Reliability Engineering (SRE) & best practices
Overview of Site Reliability Engineering (SRE) & best practices
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...
Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019
Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019
Pushing the Bottleneck: Predicting and Addressing the Next, Next Thing
Pushing the Bottleneck: Predicting and Addressing the Next, Next Thing
Similar to Software provider
Webinar: Demonstrating Business Value for DevOps & Continuous Delivery
The document discusses DevOps and continuous delivery. It begins with an introduction and agenda. It then discusses transforming IT operations for greater business value, challenges for businesses and IT that DevOps addresses, what DevOps is in terms of people, processes, and tools. It discusses continuous delivery and provides examples of goals and metrics for DevOps initiatives like release frequency, throughput time, and idle time. Finally, it discusses how DevOps tools can work with other tools and processes.
Continuous Delivery
Continuous Delivery
What it takes to move to continuous integration and Continuous Delivery/Deployment model.
www.scmtechblog.net
Continuous Delivery: why ? where to start ? how to scale ?
This document provides an overview of continuous delivery and how to get started with it. It defines key terms like continuous integration, continuous delivery, and continuous deployment. It discusses the benefits of continuous delivery like delivering value faster and with higher quality. It then presents several maturity models for assessing an organization's continuous delivery capabilities. It provides recommendations for where to start the continuous delivery journey, such as focusing on automating deployments and environments first. Finally, it discusses challenges of scaling continuous delivery across large organizations.
Agile webinar pack (2)
This document discusses the differences between waterfall and agile development approaches for SAP projects. It notes that it is not an "either/or" debate, as both approaches have advantages and neither is suitable for all situations. The document outlines some of the benefits of each approach, such as shorter time to market with agile but more extensive testing and change management with waterfall. It then discusses five fundamentals for becoming more agile with SAP: creating an enabling environment, building an agile development model, using smart bundling strategies, automating processes and shifting testing left, and focusing on culture change.
Data Governance in an Agile SCRUM Lean MVP World
Most of us learned data modeling via a waterfall-driven methodology lens. Yet Agile and other modern development methods have for the most part assumed that data governance is an anti-pattern to just getting things (software) done. Well look at questions such as:
•Are Agile and Data Governance Enemies?
•How can we get stuff done AND get systems delivered?
•And what do we do about existing systems delivered without data governance attention?
We'll also look at how data modeling fits in the answers to these questions.
Seven Keys to Navigating Your Agile Testing Transition
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? When things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. Explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale—all building agile testing excellence. Examine the mistakes, adjustments, and the successes, and learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
Seven Keys to Navigating Your Agile Testing Transition
So you’ve “gone agile” and have been relatively successful for a year or so. But how do you know how well you’re really doing? And how do you continuously improve your practices? And when things get rocky, how do you handle the challenges without reverting to old habits? You realize that the path to high-performance agile testing isn’t easy or quick. It also helps to have a guide. So consider this workshop your guide to ongoing, improved, and sustained high-performance. Join seasoned agile testing coach Bob Galen as he share lessons from his most successful agile testing transitions. You’ll explore actual team case studies for building team skills, embracing agile requirements, fostering customer interaction, building agile automation, driving business value, and testing at-scale stories of agile testing excellence. You’ll examine the mistakes, adjustments, and the successes—so you’ll learn how to react to real-world contexts. Leave with a better view of your team’s strengths, weaknesses, and where you need to focus to improve.
Challenges and Best Practices of Database Continuous Delivery
ארגונים ברחבי העולם מגבירים את השימוש בתהליכי DevOps לטובת שיפור היתרון התחרותי שלהם, הורדת סיכונים והפחתת עלויות פיתוח. כיום ניתן ליישם את ההצלחה של ה-DevOps בעולם מסדי הנתונים, על ידי ביצוע אוטומציה של תהליכי הפיתוח והעברה בין סביבות, אכיפת מנגנוני אבטחה, והפחתת הסיכונים הכרוכים בתהליך.
S.R.E - create ultra-scalable and highly reliable systems
Site Reliability Engineering enables agility and stability.
SREs use Software Engineering to automate themselves out of the Job.
My advice, if you want to implement this change in your company is to start with action items, alter your training and hiring, implement error budgets, do blameless postmortems and reduce toil.
https://events.drupal.org/dublin2016/sessions/sre-create-ultra-scalable-and-highly-reliable-systems
Agile for Me- CodeStock 2009
This document provides an overview of Agile software development. It begins by defining Agile as a project management process that encourages frequent inspection and adaptation. It then discusses some common Agile practices like Scrum and eXtreme Programming. The Agile Manifesto values individuals and interactions, working software, customer collaboration, and responding to change. Finally, it provides advice for different roles on how Agile can benefit them and their work.
! Testing for agile teams
Testing for agile teams . What's the difference between this and other testing ? What are the goals for such testing ?
Is agile testing needed at all ? Why ?
You will find some answers inside and mist likely will be directed to the right way.
The Why and How of Continuous Delivery
The document discusses continuous delivery (CD), which is a strategy for frequently releasing software changes by making the deployment process automated and ensuring the mainline code is always in a deployable state. It outlines some issues with traditional release processes like long release cycles and merge conflicts. CD aims to reduce risks by deploying changes frequently after automated testing. Benefits include being more responsive to demands and reducing pressure and waste. The core benefit is allowing teams to release changes fast while maintaining confidence. It addresses common objections to CD and argues that it is actually a risk reduction strategy.
Testing and DevOps Culture: Lessons Learned
This document discusses the speaker's background and experiences with software engineering practices. It covers his education in computational mathematics and computer science, past roles at Universal Instruments developing machine software and at Google and Etsy implementing DevOps practices. Key topics covered include the benefits of continuous integration, deployment and delivery; the importance of testing including test-driven development; and embracing interdependence between developers and other IT roles. Best practices are noted to be situational and relationships must be respected.
Engineering Velocity @indeed eng presented on Sept 24 2014 at Beyond Agile
Increasing engineering velocity through architecture. This presentation was given at the Beyond Agile meetup group in Seattle on Sept 24, 2014.
Continuous Delivery for Agile Teams
The document discusses the principles and practices of continuous delivery in an agile context. It emphasizes automating the entire software delivery process from code commits through deployment to production to minimize risks and ensure fast, reliable software updates. This includes having automated tests, continuous integration, monitoring systems, and the ability to rollback changes. It also stresses the importance of collaboration across teams to establish a shared goal of delivering value to customers through working software.
Panel Discussion Continuous Deployment in SaaS
The document discusses continuous deployment in software-as-a-service. Continuous deployment is a software engineering approach where teams produce software in short cycles to ensure it can be reliably released at any time. This allows for more incremental and frequent updates to applications in production. A repeatable deployment process is important for continuous delivery to reduce the cost, time, and risk of changes. The document provides examples of challenges with continuous deployment like consistent quality and live data migration. It also discusses techniques for continuous deployment like rolling, canary, and blue-green deployments.
ProdSec: A Technical Approach
What happens when a company either doesn’t fully empower the Security team, or have one at all? Stuff like Goto fail, Equifax, unsandboxed AVs and infinite other buzz, or yet to be buzzed, words describe failures of not adequately protecting customers or services they rely on. Having a solid security team enables a company to set a bar, ensure security exists within the design, insert tooling at various stages of the process and continuously iterate on such results. Working with the folks building the products to give them solutions instead of just problems allows one to scale, earn trust and most importantly be effective and actually ship.
There’s a whole security industry out there with folks wearing every which hat you can think of. They have influence and the ability to find a bug one day and disclose it the next, so companies must adapt both engineering practices and perspectives in order to ‘navigate the waters of reality’ and not just hope one doesn’t take a look at their product. Having processes in place that reduce attack surface, automate testing and set a minimum bar can reduce bugs therefore randomization for devs therefore cost of patching and create a culture where security makes more sense as it demonstratively solves problems.
Nvidia is evolving in this space. Focused on the role of product security, I’ll go through the various components of a security team and how they each interact and complement each other, commodity and niche tooling as well as how relationships across organizations can give one an edge in this area. This talk balances the perspective of security engineers working within a large company with the independent nature of how things work in the industry.
Attendees will walk away with a breadth of knowledge, an inside view of the technical workings, tooling and intricacies of finding and fixing bugs and finding balance within a product-first world.
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Many project teams have adopted unit testing as a necessary step in their development process. Many more use a test-first approach to keep their code lean. Yet, far too often these teams still suffer from many of the same impediments: recurrent integration failures with other enterprise projects, slow feedback with the customer, and sluggish release cycles. With a languishing feedback loop, the enterprise continues to put increasing pressure on development teams to deliver. How does an aspiring agile team improve to meet the demands of the enterprise?
Continuous integration is the next logical step for the team. In this talk, you’ll learn how continuous integration solves intra and inter-project integration issues without manual overhead, the value added by continuous integration, and how to leverage tools and processes to further improve the quality of your code. Finally, we discuss the gold standard of agile teams: continuous deployment. You’ll learn how continuous deployment helps close the feedback loop with your customers, increases visibility for your team, and standardizes the deployment process.
No more excuses QASymphony
This document promotes switching from Quality Center to qTest, citing several advantages of qTest for agile software testing. Quality Center is not well-suited for agile workflows, has poor usability and integration, and is very expensive. qTest is designed for agile teams, integrates seamlessly with popular agile tools, and provides better visibility, collaboration, and test case management capabilities. Migrating from Quality Center to qTest is straightforward and qTest users report improved efficiency and a better overall testing experience.
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014
Thanks to Liam and the crew from Magentys for arranging a fantastic evening of presentations on all things DevOps.
Attached is my presentation from the event on Enterprise Devops.
For those of you who missed it:
“Join the crowd of 100 industry leaders across the Retail, Finance and Digital sectors for an exciting evening of talks in London’s Tech City on DevOps. Enjoy networking with a chilled beer alongside the experts who are making DevOps work and those who want to make it work.
Whether you’re a corporate or start-up, DevOps should be a hot topic so listen to how the experts are achieving great things, hear their views on the trends and discuss the future of DevOps.”
Jonny
enterprisedevops.com
Similar to Software provider (20)
Webinar: Demonstrating Business Value for DevOps & Continuous Delivery
Webinar: Demonstrating Business Value for DevOps & Continuous Delivery
Continuous Delivery: why ? where to start ? how to scale ?
Continuous Delivery: why ? where to start ? how to scale ?
Seven Keys to Navigating Your Agile Testing Transition
Seven Keys to Navigating Your Agile Testing Transition
Seven Keys to Navigating Your Agile Testing Transition
Seven Keys to Navigating Your Agile Testing Transition
Challenges and Best Practices of Database Continuous Delivery
Challenges and Best Practices of Database Continuous Delivery
S.R.E - create ultra-scalable and highly reliable systems
S.R.E - create ultra-scalable and highly reliable systems
Engineering Velocity @indeed eng presented on Sept 24 2014 at Beyond Agile
Engineering Velocity @indeed eng presented on Sept 24 2014 at Beyond Agile
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Beyond TDD: Enabling Your Team to Continuously Deliver Software
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014
Recently uploaded
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
Boost Your Savings with These Money Management Apps
A money management app can transform your financial life by tracking expenses, creating budgets, and setting financial goals. These apps offer features like real-time expense tracking, bill reminders, and personalized insights to help you save and manage money effectively. With a user-friendly interface, they simplify financial planning, making it easier to stay on top of your finances and achieve long-term financial stability.
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...
Visual testing plays a vital role in ensuring that software products meet the aesthetic requirements specified by clients in functional and non-functional specifications. In today's highly competitive digital landscape, users expect a seamless and visually appealing online experience. Visual testing, also known as automated UI testing or visual regression testing, verifies the accuracy of the visual elements that users interact with.
Photoshop Tutorial for Beginners (2024 Edition)
Photoshop Tutorial for Beginners (2024 Edition)
Explore the evolution of programming and software development and design in 2024. Discover emerging trends shaping the future of coding in our insightful analysis."
Here's an overview:Introduction: The Evolution of Programming and Software DevelopmentThe Rise of Artificial Intelligence and Machine Learning in CodingAdopting Low-Code and No-Code PlatformsQuantum Computing: Entering the Software Development MainstreamIntegration of DevOps with Machine Learning: MLOpsAdvancements in Cybersecurity PracticesThe Growth of Edge ComputingEmerging Programming Languages and FrameworksSoftware Development Ethics and AI RegulationSustainability in Software EngineeringThe Future Workforce: Remote and Distributed TeamsConclusion: Adapting to the Changing Software Development LandscapeIntroduction: The Evolution of Programming and Software Development
Photoshop Tutorial for Beginners (2024 Edition)Explore the evolution of programming and software development and design in 2024. Discover emerging trends shaping the future of coding in our insightful analysis."Here's an overview:Introduction: The Evolution of Programming and Software DevelopmentThe Rise of Artificial Intelligence and Machine Learning in CodingAdopting Low-Code and No-Code PlatformsQuantum Computing: Entering the Software Development MainstreamIntegration of DevOps with Machine Learning: MLOpsAdvancements in Cybersecurity PracticesThe Growth of Edge ComputingEmerging Programming Languages and FrameworksSoftware Development Ethics and AI RegulationSustainability in Software EngineeringThe Future Workforce: Remote and Distributed TeamsConclusion: Adapting to the Changing Software Development LandscapeIntroduction: The Evolution of Programming and Software Development
The importance of developing and designing programming in 2024
Programming design and development represents a vital step in keeping pace with technological advancements and meeting ever-changing market needs. This course is intended for anyone who wants to understand the fundamental importance of software development and design, whether you are a beginner or a professional seeking to update your knowledge.
Course objectives:
1. **Learn about the basics of software development:
- Understanding software development processes and tools.
- Identify the role of programmers and designers in software projects.
2. Understanding the software design process:
- Learn about the principles of good software design.
- Discussing common design patterns such as Object-Oriented Design.
3. The importance of user experience (UX) in modern software:
- Explore how user experience can improve software acceptance and usability.
- Tools and techniques to analyze and improve user experience.
4. Increase efficiency and productivity through modern development tools:
- Access to the latest programming tools and languages used in the industry.
- Study live examples of applications
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Join us for an engaging session led by Flow Champion, Tom Kitt. This session will dive into a technique of enhancing the user interfaces and user experiences within Screen Flows using the Salesforce Lightning Design System (SLDS). This technique uses Native functionality, with No Apex Code, No Custom Components and No Managed Packages required.
Manyata Tech Park Bangalore_ Infrastructure, Facilities and More
Located in the bustling city of Bangalore, Manyata Tech Park stands as one of India’s largest and most prominent tech parks, playing a pivotal role in shaping the city’s reputation as the Silicon Valley of India. Established to cater to the burgeoning IT and technology sectors
ACE - Team 24 Wrapup event at ahmedabad.
Atlassian Team 24 event wrap-up Ahmedabad. Recap of Atlassian team24 event.
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
Orca: Nocode Graphical Editor for Container Orchestration
Tool demo on CEDI/SISTEDES/JISBD2024 at A Coruña, Spain. 2024.06.18
"Orca: Nocode Graphical Editor for Container Orchestration"
by Pedro J. Molina PhD. from Metadev
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...
Vector databases are transforming how we handle data, allowing us to search through text, images, and audio by converting them into vectors. Today, we'll dive into the basics of this exciting technology and discuss its potential to revolutionize our next-generation AI applications. We'll examine typical uses for these databases and the essential tools
developers need. Plus, we'll zoom in on the advanced capabilities of vector search and semantic caching in Java, showcasing these through a live demo with Redis libraries. Get ready to see how these powerful tools can change the game!
ppt on the brain chip neuralink.pptx
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
TMU毕业证书精仿办理
多伦多都会大学毕业证成绩单(留信网认证)【176555708微信】不能毕业办理假文凭回国找工作
【多伦多都会大学毕业证成绩单仿制】（176555708微信☀️）伪造研究生学位证书TMU毕业证文凭,多伦多都会大学文凭证书学籍信息入库,多伦多都会大学学位证书留学高校学位证书补办
【TMU毕业证【微信176555708】多伦多都会大学文凭学历】【微信176555708】【多伦多都会大学文凭学历证书】【多伦多都会大学毕业证书与成绩单样本图片】毕业证书补办 Fake Degree做学费单【毕业证明信-推荐信】成绩单，录取通知书，Offer，在读证明，雅思托福成绩单，真实大使馆教育部认证，回国人员证明，留信网认证。网上存档永久可查！
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
DevOps Consulting Company | Hire DevOps Services
Spiral Mantra excels in providing comprehensive DevOps services, including Azure and AWS DevOps solutions. As a top DevOps consulting company, we offer controlled services, cloud DevOps, and expert consulting nationwide, including Houston and New York. Our skilled DevOps engineers ensure seamless integration and optimized operations for your business. Choose Spiral Mantra for superior DevOps services.
https://www.spiralmantra.com/devops/
42 Ways to Generate Real Estate Leads - Sellxpert
Generate hot real estate leads with these simple strategies. 42 innovative ways to attract clients in the real estate industry.
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Ensuring the optimal performance of your audio-visual (AV) equipment is crucial for delivering exceptional experiences. AV performance validation is a critical process that verifies the quality and functionality of your AV setup. Whether you're a content creator, a business conducting webinars, or a homeowner creating a home theater, validating your AV performance is essential.
Assure Contact Center Experiences for Your Customers With ThousandEyes
Assure Contact Center Experiences for Your Customers With ThousandEyes
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0
Recently uploaded (20)
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Boost Your Savings with These Money Management Apps
Boost Your Savings with These Money Management Apps
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...
The Power of Visual Regression Testing_ Why It Is Critical for Enterprise App...
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Enhanced Screen Flows UI/UX using SLDS with Tom Kitt
Manyata Tech Park Bangalore_ Infrastructure, Facilities and More
Manyata Tech Park Bangalore_ Infrastructure, Facilities and More
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Orca: Nocode Graphical Editor for Container Orchestration
Orca: Nocode Graphical Editor for Container Orchestration
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...
WMF 2024 - Unlocking the Future of Data Powering Next-Gen AI with Vector Data...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
The Comprehensive Guide to Validating Audio-Visual Performances.pdf
Assure Contact Center Experiences for Your Customers With ThousandEyes
Assure Contact Center Experiences for Your Customers With ThousandEyes
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Software provider
- 1. Choosing Your Software Provider Arthit Hongchintakul Managing Director Swiftlet Co., Ltd. contact@swiftlet.co.th
- 2. What is Software Development? https://twitter.com/daisyowl/status/841806379962646532?lang=en
- 3. Various Roles in Software Team Product Owner Project Manager Quality Assurance AnalystDevOps Developers
- 5. Talk to tech team for timeline, or set yourself up for failure.
- 7. Feature Priority > Must-have: We will lose without them. > Should-have: We will not win without them. > Nice-to-have: We will win more with them. – If it’s unnecessary, it’s unnecessary. – Don’t fix things that don’t break. – Keep it simple and stupid. – Elegance = Simple and Powerful – Master your skills of saying no. https://www.projectsmart.co.uk/moscow-method.php
- 8. Releasing Software • Staging environment • Test run everything • Capacity Planning • Data Migration Planning • Versioning Plan • Pre-deploy QA • Deploy • Migration • Post-deploy QA • Rollback Release • Analytics Information • Growth Projection • Production Issues • Continuous Integration • Continuous Delivery Repeat
- 9. Scaling > How does your software respond to increasing load? – Algorithmic analysis: Big O notation – Load Testing: Jmeter, flood.io > What is your expected load at launch? A month in? A year in? Three years in? > What kind of infrastructure you need to support such load? > Real-time load monitoring – preemptive scaling – New Relic, Zabbix, m/monit > Cloud Infrastructure vs Hosted Solutions vs Self-Hosting
- 10. Software Development Cost Analysis Qualification • ISO • CMMA • HIPAA • Security Equipment • Development Machines • Test Devices • Licensing • Various Environments Labor • Project Manager • Analyst • Developer • QA • DevOps • Support Infrastructure • Domain • DNS • SSL Certificates • Hosting • Analytics • Support Platorm Disaster • Bugs • Downtime • SLA • Opportunity Cost • Reputation
- 11. Development teams are people. We make mistakes. Our mistakes are spectacular. You are a part of the team too. Help out.
- 12. Just because you paid millions for crap sandwich, doesn’t mean you have to keep it. May be it’s cheaper to restart.
- 13. In-house vs Outsource In-house > You pay for the salary and all the tools required. Sometimes with food, other times with stock options. > There’s no lump sum fee you can fix. You will have to pay the price for letting your staff go after the project. > You have complete control over the project. It’s entirely up to you, good or bad, right or wrong, success or failure. You had better know what you’re up to. Outsource > You pay for the (greatly varying) service fee and huge margin. You have the power to choose a lump sum fee; or a man-hour rate. > You usually have to have a maintenance contract post-release. > You have less control. Sometimes it’s a good thing. Let the expert do their job. Or… you may be conned in the most terrible way. Ultimately, software development is a people business. It’s all about who you hire.