Embed Size (px)
Citation preview
100 People > 10 Teams > 1 Product Large Scale Agile Release Planning
Opening Activity
Introduce yourself and discuss at your table : Why do we do release planning ?
What are the benefits?
About us: Brad Swanson
@bradswanson
!
Manny G Segarra III
Facilitate
Framework
Plan
Framework
Case Study: Acme Cable TV Co.
6
Set top box (STB/DVR)
soIware
STB server
Server comp Server comp Server comp
7
A1
A B C D
A2 A3
B1 B2
Architecture Roadmap E2 E3 E1 E4
E1 E2
Portfolio Project Roadmap Project C Project A D
Project B
H
H
H R
elea
se
…
Sto
ry b
ackl
og
MM
F/E
pic
bac
klog
s
System Team
Agile feature &
component teams
Sto
ry b
ackl
og
Product Council P
roje
ct b
ackl
og
Epic Roadmap
Epic C1 A1 Epic B3 D MMF B1
A3 MMF A2 C2 C3
back
log
Release Planning
H
H
H
Rel
ease
C E3 B
MMF B2 Epic B4
…
Sto
ry /
task
ba
cklo
g
Sprint / iteration
Har
deni
ng
Spr
int
Based on The Scaled Agile Framework™ From the Dean Leffingwell book Agile Software Requirements
PO PO A
B3 B4
E3 E4
A E1 B
test
nfr
Release 1 Release 2 R3
8
Set top box (STB) soIware
STB server
Server comp Server comp Server comp New server component team
Feature team
1
Feature team
2
Feature team
3
Server plaSorm team
STB plaSorm team
System Test Team
Feature team
4
System Architecture Team
Feature team
5
Cross-‐team component integrity
FT Organized by requirement area. Stable. Cross-‐component
Develop new component unZl mature, then FTs take over.
Arch components == pre-‐Agile teams
9
ACTIVITY #2
Reflect individually on this framework.
How could you apply all or part to your organization?
Discuss insights and questions at your tables.
Plan
11
A1
A B C D
A2 A3
B1 B2
E1 E2
Epi
c b
ackl
ogs
Product Council P
roje
ct b
ackl
og
Release Planning
PO PO A
B3 B4
E3 E4
4-‐6 weeks 2-‐3 weeks Planning Day
Release planning event
Next Release
1. PorSolio planning
2. Team story mapping 3. Teams idenZfy dependencies, pair-‐wise collab
4. Team esZmates release scope
2. Story mapping 3. IdenZfy dependencies 4. EsZmate release scope 5. Prepare epic Zmeline for planning day
Current Release
PreparaZon Timeline
walking skeleton
Product planning with story maps
Source: Jeff Patton. “An Introduction to User Story Mapping”
Order of usage or logical epic grouping
Story A
Epic Epic Epic
Story B
Story Story
Story
Story Story
Story
Story
prio
rity
Story
Story
Story Story
Release boundary
12
EsZmaZon Scale
13
Mike Cohn, Mountain Goat Software
Epic-‐level planning: each team
14
Epic A Epic B
Epic C Epic D
Epic E
SEPT OCT NOV DEC
Dependency FROM other
team
Dependency ON another
team
Epic F
15
16
ACTIVITY #3
Reflect on the planning process.
What would you do differently?
Discuss ideas at your tables.
17 Facilitate
18
1. One big room with wall space for each team
19
2. Release vision Team intros Key features
20
3. Inter-‐team discovery,
collaboraZon negoZaZon
21
Discovery CollaboraZon NegoZaZon
22 Team board after the inter-team discovery
Request from other team
New story New dependency
23
4. Integrate the team plans
5. Agree on preliminary
plan
25
6. RetrospecZve
Release planning outcome
Alignment
Teamwork
Visible Release Map
1. Keep map visible & update weekly
2. Honest Progress == Transparency
3. Ask for Help when you need it
4. Courage !
27
Once dev is underway
28
30
Thanks to our team…
• Ken McCorkell • Deanna Evans • Don McKenzie • John Henry • Sherri Green
30
32
