Managingincrementswi thvwstaging030

Managing Increments and Iterations with "V-W" Staging: 

Managing Increments and Iterations with "V-W" Staging Alistair Cockburn Human and Technology arc@acm.org http://Alistair.Cockburn.us

“Every team must deliver working function every 2-4 months.”: 

“Every team must deliver working function every 2-4 months.” The most important statement I know to make for a project.

How can we describe increments, iterations, and spirals using linear calendar time?: 

How can we describe increments, iterations, and spirals using linear calendar time? Givens: Developer time vs. Project Manager time The “Validation V” Techniques: V’s for increments & iterations V-W staging Managing by milestones and reviews

The Problem (1):  Developers do not live in linear time.: 

The Problem (1): Developers do not live in linear time. time artifacts Proj. Plan other classes Use Cases Domain UI (“Developer’s time”) Artifacts grow fast, slow, even backwards! Spiral is a good word.

The Problem (2):  Project Managers DO live in linear time.: 

The Problem (2): Project Managers DO live in linear time. The calendar does not show spirals. time moves inexorably forward... (“Project Manager’s time”) How do you schedule a Gestalt Round Trip?

The ‘Validation V’:  Not waterfall, but a fact of life.: 

The ‘Validation V’: Not waterfall, but a fact of life. Req'ts Design Validate syntax Validate req'ts Code Validate logic How can we use this 'fact of life'?

1 24-month V is “waterfall”. 6 4-month Vs are incremental, effective.: 

1 24-month V is “waterfall”. 6 4-month Vs are incremental, effective. ? Adjustment Points 1-10

Short Vs allow focus of attention, learning, better estimation, process & team changes.: 

Short Vs allow focus of attention, learning, better estimation, process & team changes. 6-16 weeks Aha ! Ah Staff changes Management changes Process changes Aha ! 1-10

Increments lets you fix Process: build / deliver / learn / build / deliver...: 

Increments lets you fix Process: build / deliver / learn / build / deliver... UI Function Infrastructure Database 1 2 2 2 3 3 3 Req’ts Design Test Ship Learn! Req’ts Design Test Ship

Iterations let you fix Ignorance:build / examine / learn / rebuild / ship...: 

Iterations let you fix Ignorance: build / examine / learn / rebuild / ship... Req’ts Design Examine Learn! Req'ts Redesign Test Ship! A version A Revision Ship Version

Vs fit within Vs for increments / iterations,and to manage visibility.: 

Vs fit within Vs for increments / iterations, and to manage visibility. Team-visible increments or iterations Exte rnally visible increments 10 months 4 months 3 months 3 months 2 1 1 1 1 1 1 1 1 S S S E E E E E E

Increments and iterations combine well ("mountain range" picture): 

Increments and iterations combine well ("mountain range" picture)

Every V is a major milestone  for the Project Manager's calendar: 

Every V is a major milestone for the Project Manager's calendar use case 22 class 9 use case 21 screen 11 use case 22 week 41 week 42 week 43 week 44 week 40 class 9 use case 21 screen 11

Multiple teams can be synchronized  using overlapping Vs.: 

Team:1 2 3 Multiple teams can be synchronized using overlapping Vs. 6 to 16 weeks Characterize the plan by Width, Offset, Overlap of Vs.

Refined view of Increments: Requirements & design evolve.: 

Refined view of Increments: Requirements & design evolve. Staff work by time showing ongoing requirements & design

Net : Managers can request and plan from V results instead of "phase" results!: 

Net : Managers can request and plan from V results instead of "phase" results! ? Analysis Document Design Document Final Requirements Document Prototype or Ship#1 Ship#2 Final

Experiences (3): The "V-W" model lets people negotiate the work plan: 

Experiences (3): The "V-W" model lets people negotiate the work plan Managers must and can write a 6-month plan. Developers must and can iterate. They negotiate number and duration: iterations to examine For usage / performance / correctness increments to ship or stack

The V-W model lets project managers put increments / iterations on the calendar. : 

The V-W model lets project managers put increments / iterations on the calendar. What this model does NOT do: Does not make project managers smarter Does not improve your first estimate Does not guarantee project delivered on time What this model DOES do: Gives a vocabulary to what we know is effective, but hard to describe. Lets project managers SCHEDULE iterations Let different people develop differently

Experiences (1): The "V-W" model lets developers explain what they are doing: 

Experiences (1): The "V-W" model lets developers explain what they are doing A: 150-person project Described the multi-team W (width /overlap /sync) B: Dumped waterfall process Because they could rationally explain new process They knew the waterfall was wrong, but they couldn't argue their feelings. Moved to increments within increments

Experiences (2): The "V-W" model lets different people work differently: 

Experiences (2): The "V-W" model lets different people work differently C: Released each 3 months, 3 iterations /release (A winning strategy) D: Released each 4 months, no iterations /release (Iterations are hidden. An OK strategy) E: 'V' per week, release whenever possible (A survival strategy on, e.g., Wall Street) F: Release each year, many iterations (A losing strategy)

"V-W" lets people negotiate work plan: 

"V-W" lets people negotiate work plan Managers must and can write a 6-month plan. Developers must and can iterate. They negotiate number and duration: iterations to examine For usage / performance / correctness increments to ship or stack

"V-W" lets people work differently: 

"V-W" lets people work differently A: Released each 3 months, 3 iterations /release (A winning strategy) B: Released each 4 months, no iterations /release (Iterations are hidden. An OK strategy) C: 'V' per week, release whenever possible (A survival strategy on, e.g., Wall Street) D: Release each year, many iterations (A losing strategy)