Upload
agilesparks
View
1.855
Download
1
Embed Size (px)
DESCRIPTION
Achieving Predictability with Agile - Doing Scrum in a complex multi-disciplinary environment - Elbit Case studyBy Gil Ari @ AgileIL12http://agilesparks.com/ElbitCaseStudy-GilAri
Citation preview
Think A Head
Achieving Predictability with Agile
a case study
Agile Israel 2012
27-June-2012
Think A Head
What made us start?
Projects milestones are not meet
Budget overrun
Integration Hell
Product quality
Management awareness
Think A Head
The Project – A/C Upgrade
Think A Head
Before…
Think A Head
…and after
Think A Head
The Project - Complexity
System of Systems
Lots of interfaces
Multidisciplinary:
Pilots
System
Software
Think A Head
SCRUM Team - Concepts
Working Software
Predictability
Definition Of Done (DoD) for each US
Done is Done – no bugs
Team Commitment – as many US per PO priority
Early Feedback
Measure the team, not the individual developer
Think A Head
SCRUM Team Measurements
1 2 3 4 5 60
5
10
15
20
25
30
35
40
45
50
26 26
23
35
43
37
10
4
13
16
36
30
Comitted Done
Think A Head
End to End Flow
Discovery Team
Manages the end-to-end flow (using Kanban)
Scrum Team
Manages the development per iteration
Think A Head
Kanban – managing the end to end flow
Visualize the workflow
Limit WIP (work in progress)
Measure & optimize flow
Explicit policies (definition of Done, WIP limits, etc)
Backlog Dev Done
orem ipsum dolor sit
amet, co nse ctetur
orem ipsum dolor sit
amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse cteturorem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
UAT Deploy5 3 2 3
FLOW Avg lead time: days 12
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit
amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
orem ipsum dolor sit amet, co nse ctetur
Pioneered byDavid Andersonin 2004
Think A Head
End to End Flow – The States
Backlog New
Analysis Selected Discovery Elaborating
Scrum Elaborating Ready Story
Development (SCRUM) In Process Done
Acceptance Free Run Mini FQT Formal FQT Closed
Think A Head
Discovery Team – Practical Notes
Who is in the team
Technical Manager
Operational
System
Software
Discovery Forum
Once a week
Review WIP
Visibility tools
SCRUM Team – board & notes – Tasks
Discovery – TFS – User Stories
Think A Head
Discovery Team – Continuous Flow
Analysis Acceptance
Think A Head
Discovery Team - Tools
Think A Head
Discovery Team – Story Points
Rough estimate (range)
Estimates may be wrong
Team Velocity is per Backlog estimates
Team estimates (Scrum planning) are not related to Backlog estimates (Backlog preparation)
Velocity : Done is Done
Min [days]
Max [days]
Story Point
TshirtSize
1 2 1 XS3 5 2 S6 10 4 M11 20 8 L21 40 16 XL41 80 25 XXL81 160 35 XXXL
Think A Head
Commitment
Think A Head
Team Velocity & Predictability
Remaining Future Iterations: 2
Remaining Story Points: 115.00
Calculated Values Normal Worst Case
Current Velocity: 26.00 20.80
Estimates
Remaining Capacity: 52.00 41.60
Outstanding Story Points: 63.00 73.40
Think A Head
Cumulative Flow Diagram
Think A Head
Our Conclusions
Manage the entire processManage the flow
Before Iteration – Planning preparations
During Iteration – Early feedback; Free run tests
After Iteration –
Fix bugs ASAP
Mini FQTs (avoid Integration hell)
Multi disciplinary discovery team
Work as a team
Focus on ready stories
Think A Head
Our Conclusions
PredictabilityTeam Velocity as a parameter
Data Analysis
How to increase Team Velocity
Always Retrospect
Ready Story
Remove impediments
Team size – Diminishing Marginal Utility
Trust the Team
Think A Head
Questions?
Think A Head
The End