agile techniques as business acceleration tools
DESCRIPTION
Agile Techniques as Business Acceleration Tools by Ralph JochamTRANSCRIPT
effective agile. Ralph Jocham [email protected]
Ralph Jocham • Started as programmer; discovered process as a problem early on • First Unified Process with UML • Agile since 2000 with XP • Scrum in 2003 • Oracle, LinkedIn, Roche, Google, The Gap, Swisscom, Texas Instruments, ThoughtWorks,
Siemens Medical, JPMorgan • Did come around, different cultures and domains • Founder of effective agile. • Trainer with Scrum.org
31-‐May-‐2012 effective agile. 3
Business = Opportunities
31-‐May-‐2012 effective agile. 4
Opportunity = Products
31-‐May-‐2012 effective agile. 5
Product = Features
31-‐May-‐2012 effective agile. 6
Feature = Risks
Risk Mitigation
31-‐May-‐2012 effective agile. 7
Feedback Validation
Quick Often
Scientific Method
31-‐May-‐2012 effective agile. 8
Ask Ques0on
Do Background Research
Construct Hypothesis
Test with an Experiment
Analyze Results
Publish Results
Retest
Deming Cycle
31-‐May-‐2012 effective agile. 9
Ask Ques0on
Do Background Research
Construct Hypothesis
Test with an Experiment
Analyze Results
Publish Results
Retest
Plan
Do Check
Act
Agile Continuous Delivery
31-‐May-‐2012 effective agile. 10
New Product Idea
Gather Data / Define Acceptance Criteria
Write User Story
Implement Test Driven
Validate & Verify
Deploy
UAT
Plan
Do Check
Act
31-‐May-‐2012 effective agile. 11
Speed is of essence
31-‐May-‐2012 effective agile. 12
Plan
Analyze
Design
Code
Test
Release
How does this approach work?
Scrum
31-‐May-‐2012 effective agile. 13
Scrum (Empirical)"
Waterfall (Defined)"Plan for the entire project up-front
Plan a little for the entire project and then a little for each Sprint"
(source: ADM)
intern
extern
intern
extern
intern
extern
Plan Analyze Design Code Test Release
Plan
Plan
Plan Design Code Test
Release
Plan
Plan Design Code Test
Release
Plan
Plan Design Code Test
Release
Plan
Plan Design Code Test
Release
31-‐May-‐2012 effective agile. 14
MVP – Minimum Viable Product
A minimum viable product (MVP) is a development technique in which a new product or website is developed with sufficient features to satisfy early adopters. The final, complete set of features is only designed and developed after considering feedback from the product's initial users.
1. It has enough value that people are willing to use it or buy it ini0ally
2. It demonstrates enough future benefit to retain early adopters
3. It provides a feedback loop to guide future development
(source: techopedia.com)
How long is your runway?
31-‐May-‐2012 effective agile. 15
35% of Requirements Change
31-‐May-‐2012 effective agile. 16
>60% of features are rarely or never used
(source: Standish Group)
31-‐May-‐2012 effective agile. 17
How long is your runway?
31-‐May-‐2012 effective agile. 18
Scrum in a Nutshell
31-‐May-‐2012 effective agile. 19
Roles Product Owner Development Team Scrum Master
Ar0facts Product Backlog Sprint Backlog Increment
Events Sprint Planning Sprint Daily Scrum Sprint Review Retrospec0ve
Product Backlog
Sprint Planning Mee0ng
Sprint Backlog Sprint
Increment
Review
Retrospec0ve
Daily Scrum
ScrumMaster
(source: ADM)
Poten0ally Releasable
Agile vs Waterfall
31-‐May-‐2012 effective agile. 20
(source: ADM)
Visibility Ability to Change
Business Value Risk
Waterfall Scrum
31-‐May-‐2012 effective agile. 21
Practices - Metrics
A/B or Split Testing
Trying different solutions on the same customer base. Depending on feed-back
the better option is chosen.
How Agile Helps:
• Continuous Delivery based on Continuous Integration
• Continuous customer feedback through Sprint Reviews
• Flexible tested and instrumented code base (Branching by Abstraction)
31-‐May-‐2012 effective agile. 22
Practices - Metrics
Cohort Analysis
Look at data in the context of the ‘experiment’ not cumulative totals or gross-
numbers.
How Agile Helps:
• Continuous Delivery based on Continuous Integration
• Continuous customer feedback through Sprint Reviews
• Flexible tested and instrumented code base (Branching by Abstraction)
31-‐May-‐2012 effective agile. 23
Practices – Root Cause Analysis
Root Cause Analysis
Fix the root cause not the symptom. Ask ‘Why’ five times, the fifth answer is you
root cause.
How Agile Helps:
• Review
• Retrospective
• Continuous Improvement (Kaizen) thinking
31-‐May-‐2012 effective agile. 24
Practices – Small Batches
Small Batches
Think in features not in activities. Deliver working, tested, releasable software
every sprint.
How Agile Helps:
• Continuous Delivery based on Continuous Integration
• Cross-Functional Development Teams
• Product Backlog
• Definition of Done
Dev
Release Planning Design Release Analysis Dev Tes0ng
Planning Design Release Analysis Tes0ng
Design Dev Tes0ng Release
100%
50% 40%
Planning Design Release Analysis Dev Tes0ng
Planning Design Release Analysis Dev Tes0ng
100%
Major Release
Major Release
Major Release
Point Release V1
Point Release V4
Point Release V1.5
Point Release V4.2
Major Release
FR
Func0onal Release FR FR
FR
FR
FR
FR
FR
Dev
FR V1 © 2012 Ralph Jocham effective agile. www.effectiveagile.com
Stop
31-‐May-‐2012 effective agile. 25
31-‐May-‐2012 effective agile. 26
The Lean Startup and Scrum Agile Lean Startup
Product Roadmap Business Model Canvas
Product Vision Product Market Fit
Release Plan Minimum Viable Product
On-‐Site Customer ‘Get out of the Building’
Sprint / Itera0on Build-‐Measure-‐Learn Loop
Itera0on / Sprint Review Persevere or Pivot
User Story Hypothesis
Acceptance Test A/B or Split Test
Defini0on of Done Validated Learning
Con0nuous Integra0on Con0nuous Deployment
Customer Feedback Cohort-‐based Metrics
Product Owner Entrepreneur
Scrum Master Customer Success Manager (source: Mary Poppendieck)
Questions?
31-‐May-‐2012 effective agile. 27
Ralph Jocham effective agile.
31-‐May-‐2012 effective agile. 28
www.effec6veagile.com [email protected]
@rjocham