View
176
Download
3
Category
Tags:
Preview:
Citation preview
Minimum Viable Agile
Troy TuttleLean Agile CoachKanFlow.comtroy@kanflow.com@troytuttle
KCDC 2015
Titanium Sponsors
Platinum Sponsors
Gold Sponsors
Minimum Viable AgileWhat is it?
Agile Is…?
Burn Down Charts
Sticky Notes
Card Walls
Kanban BoardsStandup Meetings
Retrospectives
Pair Programming
TDD
Sprint Planning
Planning PokerVelocityStory Points
User Stories
Release Planning
Estimation
Team Room
Definition of Done
WIP Limits
Agile Is…
(Actual Google Search, BTW)
The Agile Dysfunction Spiral
Detailed sprint planning
Formal sprintcommitment
Work the sprintUnfinished work
We need to get better at
planning sprints
Coaching to helpimprove sprint planning
Sprint planningtakes longer
ManagementApplies pressure
Culture of Blame creeps back in…
Team works overtime
Are we really just after better sprints?
Cargo Cult (Agile)
Many early Agile attempts simply installed practices (recipes).
Warning!Following recipes leads to Cargo Cult Agile
Mob Programming
Mob Programming: The original MVA?
Reduces or Eliminates: 1. Standup meetings2. Detailed planning sessions3. The need for estimates4. Team alignment activities5. Context Switching6. Individual status updates7. Burn-down charts for performance tracking8. Code Reviews
All the Brilliant People Working on the
same problem At the same timeOn the
same computer- mobprogramming.org
status updates?
Story Points: The sacred cow of Agile
Sometimes this causes unnecessary
confusion and drama!
Story points are designed to be abstract.
Velocity is an attempt to plan work based on an abstraction, based on an estimate.
Story point myopia
-- Jim Benson, moduscooperandi.com
16 72 21 19 37
Velocity in Story Points
7 9 9 9 7
Throughput in Card Count
Velocity is not Minimal Viable Agile
Velocity (based on story points) has become a social and business currency.
What about Story Point predictability?
Courtesy of Bennet Vallet
Director of Development
Siemens Health Services
Expected Distribution Actual Distribution
Story Point Predictability?
A product team from Microsoft shared their story point estimates. They performed three release forecasts:
1. Story Points 1,2,3 for small medium and large2. Story Points 1, 3, 5 for small medium and large3. All stories are 1 point (just count # of stories)
Story Point Predictability?
All dates within 3 weeks of each other in a 38 to 42 week project!
Data used with permission from Bill Hanlon at Microsoft
”At that point, I stopped thinking that estimating
was important.”
Bill Hanlon: http://bit.ly/BHanlon
Data Visualizations courtesy of Vasco Duartehttp://bit.ly/vasco_blog
@duarte_vasco
Planning in the world of MVA
Option #1Hours-long traditional sprint planning meetings spent playing planningpoker and a team arguing about the difference between 2’s and 3’s.
Option #2Short story slicing meeting where the focus is on understanding and slicing large stories.
“Do we understand this story? If not, let’s keep slicing.”
1 2 3 5 8 13 20 40 100
Right-sizing the work
Planning in the world of MVA
Input Q Design Develop Test Done1 2 1
3
12
9
7
8
64
5
Lead Time
Throughput
10
14 days from this point
5 stories per week
MVP
Upstream Planning
1. Prioritize
2. Analyze
SS
SS
SSS
SS
S
MVP
Planning in the world of MVAProbabilistic Forecasting
<= 4 days (50th percentile)<= 9 days (85th percentile)<= 13 days (95th percentile)
22333445689101316
Lead times in daysfor 14 User stories:
Find the 50th, 85th, and 95th percentiles…(Rank = Percentage * Count)
50th
85th
95th
The Essence of Agile
Focus
Learning
Simplicity (The art of the work not done.)
(Collaboration is an outcome.)
(Feedback loops enable improvements)
Insist your practices and ceremonies support the “Why” behind Agile!
Customer Value (We wouldn’t be here otherwise.)
Coaching Minimum Viable Agile
I Don’t:
Coaching Minimum Viable Agile
I Do:
Where does Agile go from here?
“What are all the practices we need to adopt to be successful?”
Minimum Viable Agile prompts us to ask:
“Now, what practices do we change ordiscard to be successful?”
Minimum Viable Agile
Troy TuttleLean Agile CoachKanFlow.comtroy@kanflow.com@troytuttle
KCDC 2015
Recommended