Ryan Ripley relates that during his last agile transformation project, a key stakeholder asked, “Why are we adopting agile?” Ryan talked about increasing quality, delivering software sooner, and fostering a more collaborative relationship with business partners. After a few moments, the stakeholder raised his hand and said, “I get all that. But how is all of this agile stuff any better, faster, or cheaper than what we do today?” Ryan says that leaders must answer the better, faster, cheaper question if they want their agile transformation and associated projects to move forward. To prepare for this critical question, Ryan explores how better, faster, cheaper translates in an agile organization. Take away experiments to use with your agile teams to define better in your organization, an understanding of how agile helps teams deliver value faster to their stakeholders, and how working in an agile way can make business costs cheaper by reducing team turnover, enhancing learning through pairing, and reducing overall costs of product ownership.
Vip Call Girls Noida ➡️ Delhi ➡️ 9999965857 No Advance 24HRS Live
The Business of Agile: Better, Faster, Cheaper
1. AW1
Agile Leadership
11/16/2016 11:30:00 AM
The Business of Agile: Better, Faster,
Cheaper
Presented by:
Ryan Ripley
Independent Consultant
Brought to you by:
350 Corporate Way, Suite 400, Orange Park, FL 32073
888--‐268--‐8770 ·∙ 904--‐278--‐0524 - info@techwell.com - http://www.stareast.techwell.com/
2. Ryan Ripley
Independent Consultant
For the past ten years Ryan Ripley has worked on agile teams in development,
ScrumMaster, and management roles. He’s worked at various Fortune 500
companies in the medical device, wholesale, and financial services industries.
Ryan is great at taking tests and holds the PMI-ACP, PSM I, PSM II, PSE, PSPO I,
PSD I, CSM, and CSPO agile certifications. He lives in Indiana with his wife Kristin
and three children. Ryan blogs at ryanripley.com, hosts the Agile for Humans
podcast available on iTunes, and is on Twitter @ryanripley.
21. SCRUM MANAGEMENT • Manage the boundaries
• Build Stable Teams
• Hire people – Grow skills
• Act transparently
• Examine systems &
correct faulty ones
• Give guidance when
asked/needed
• Reach across org charts
• Definition of Done
• Continuous improvement
• Expect working software
every sprint
Vision – Direction – Goals
“I finally have time to do my job.”
22. “I get all that…
BUT how is all
of this agile
stuff any better,
faster, or
cheaper than
what we do
today?”
@ryanripley #BSCADC
25. Stacey Diagram
• Simple: Everything is known
• Complicated: More is known
than unknown
• Complex: More is unknown
than know
• Chaotic: Very little is known
29. We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
30. “Three pillars uphold every
implementation of empirical process
control: transparency, inspection, and
adaptation.”
--The Scrum Guide
31. Scrum is not a problem solving
framework. It’s a problem finding
framework.
37. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
Creative Commons – Michael Nugent “Safety”
“The second you embarrass
someone with a metric, your
metric program is over.”
38. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
“Metrics are often
in contention with
one another.”
Creative Commons – Hans Splinter “balance”
39. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
“Your metrics have a half-
life of about 3 months…”
40. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
“People want to be treated
fairly and know when they
aren’t.”
41. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
“Trends, not individual data points.”
42. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
“Favor the cheapest metric.”
Creative Commons – 401k “Money”
43. EPISODE 35: Agile Driven Coaching with Troy Magennis
http://ryanripley.com/data-driven-agile-coaching-with-troy-magennis/
An in-depth discussion on using metrics to drive coaching insights
“Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
software.”
Creative Commons – klt “projection”
44. 5 Metrics to Help Get Started
1. Throughput
2. Defect Density
3. Customer Satisfaction
4. Team Satisfaction
5. Value Delivered Per Sprint
45. 5 Metrics to Help Get Started
1. Throughput
2. Defect Density
3. Customer Satisfaction
4. Team Satisfaction
5. Value Delivered Per Sprint
47. People do not fail, systems do
• Commitment to continuous improvement
• Trend more important than individual data points
• Investigate the bottlenecks
• Monitor cycle time
48. 5 Metrics to Help Get Started
1. Throughput
2. Defect Density
3. Customer Satisfaction
4. Team Satisfaction
5. Value Delivered Per Sprint
49. The number of bugs discovered
during a sprint
• Commitment to quality
• Trend more important than individual data points
• Increasing # of bugs could mean too much WIP
• Downward trends could point to improvements in
practices
50. 5 Metrics to Help Get Started
1. Throughput
2. Defect Density
3. Customer Satisfaction
4. Team Satisfaction
5. Value Delivered Per Sprint
51. How happy is your customer?
• Commitment to alignment
• Trend more important than individual data points
• Address negative feedback quickly
• Glad – Mad – Sad is low-res means to collect data
• Net-promoter scoring
54. 5 Metrics to Help Get Started
1. Throughput
2. Defect Density
3. Customer Satisfaction
4. Team Satisfaction
5. Value Delivered Per Sprint
55. How happy is your team?
• Commitment to safety
• Trend more important than individual data points
• Possible retrospective activity
• Is it safe to say you’re unhappy about something?
57. 5 Metrics to Help Get Started
1. Throughput
2. Defect Density
3. Customer Satisfaction
4. Team Satisfaction
5. Value Delivered Per Sprint
58. What is the value of the work?
• Commitment to delivery
• Trend more important than individual data points
• Higher numbers expected earlier in the project
• Downward trend could be an indicator to end the
project
89. No matter which methodology
your team uses, you will
spend the same amount to
employ them
90. Comparing cost of output doesn’t work either
If an agile team builds a better feature faster
than a waterfall team builds a similar feature,
are we satisfied if what we really needed was
a different feature?
94. Customer collaboration over contract negotiation
1. Transparency is essential
2. The team is upfront about their limitations
3. Stakeholders are open about their needs
96. EPISODE 37: Cost of Delay with Johanna Rothman
http://ryanripley.com/afh-037-cost-of-delay-with-johanna-rothman/
An in-depth discussion on how Cost of Delay impacts projects
97. EPISODE 37: Cost of Delay with Johanna Rothman
http://ryanripley.com/afh-037-cost-of-delay-with-johanna-rothman/
An in-depth discussion on how Cost of Delay impacts projects
Causes of Delays:
• Missed Dates
• Multitasking
• Experts
• Gold Plating
• Technical Debt
• Doing the Wrong Things
• Indecision
• Not Starting
• Dependencies