11. Teams.
Teams.
Teams.
“Build project teams around motivated
individuals. Give them the environment and
support they need, and trust them to get the
job done.”
- agilemanifesto.org
12. User
Story
User
Story
Screen
User
Story
User
Story
Repor
t
Team
User
Story
User
Story
Database
User
Story
Clarity
Accountability
Measureable
Progress
15. Process: Execute Agile Team
Inputs
Tools/
Techniques
• Fully Allocated
• Skillsets
• Small increments
Outputs
16. Process: Execute Agile Team
Inputs
Tools/
Techniques
Outputs
• Usable output
• High Quality
17. Less
Compressed
• Longer
Milestones
• Big Scope
• Skillset Silos
• Pieces built
in isolation
More
Compressed
• Shorter
Milestone
• Small Scope
• Tiger teams
• Pieces built
together
34. Moving Teams to Work
v2.0
Alpha
Gamma
Beta
???
v5.0
v3.0
v4.0
Project 1
v6.0
Project 6
Project 2
Project 5
Project 3
Project 4
Jun
Jul
Aug
Sep
! Sporadic Delivery
ü Discrete SOWs
! Delayed Business Value
ü Commodity Oriented
! Strain on resources
! Overhead of staffing up or down
35. Moving Work to Teams
v2.0
v3.0
Alpha
Project 1a
Project 1b
Gamma
Project 2
Project 4a
Beta
Project 3a
Jun
v5.0
v4.0
Project 4b
Project 5
Project 3b
Project 3c
Project 6
Jul
Aug
Sep
ü Deliver earlier and more often
! Slicing scope to fit
ü Predictable schedule
! Choosing reliability over
ü Predictable burn rate
ü Sustainable Pace
efficiency
49. Programs & PPM
Inception
Epic
Projects
Grooming
Feature
Teams
Story Backlog
User
Story
Construction
Elaboration
Transition
Tier 3 - Kanban
Architecture Spikes
Build
IVV / C&A
Deploy
Tier 2 - Kanban
Task Backlog
In Process
Task Done
Tier 1 - Scrum
Story Done
3-Tiered
Model
50. Epic
Feature
User
Story
Epics
collecDons
of
features,
typically
1-‐3
months
in
duraDon.
Epics
span
releases.
Epics
can
span
more
than
one
team.
These
are
the
things
senior
leadership
cares
about.
Features
are
smaller
than
epics,
typically
2-‐4
weeks
in
duraDon.
Features
are
contained
within
releases.
Features
are
contained
within
a
team.
These
are
what
the
Product
Owner
Cares
about.
User
Stories
are
the
smallest
increment
of
value,
typically
less
than
a
week.
User
Stories
are
contained
within
sprint.
These
are
the
things
Engineering
Management
Cares
about.
93. Inception
Elaboration
Epic
Analysis
Feature
Story Backlog
Spike
User Story User Story
Construction
Build
Feature
Feature
8
Task
8
Task
Task
8
Task
8
Story Backlog
Task Done
Task
8
Feature
Feature
In Process
Task
Task
Deploy
Test
Feature
Task Backlog
Epic
Epic
Epic
Design
Transition
Task
8
8
Spike
User Story User Story
99. World’s largest
online grocery
£2.47bn in 2011
UK, India
Conclusions
Context
Case Study: Dotcom IT
Balance technical
risk and change
Dramatic mind
shift on business
side
Leverage your
unique assets
100. 2009 Merger
with Symbian
2000+ staff
UK, India,
Finland, China
Conclusions
Context
Case Study: Telecom
Stakeholder
management is
key
Structured rollout
across years
rather than
months
Benefits real but
not measurable
106. Structure
Metrics
Governance
Assessment
OperaDonalize
Form
Teams
Targeted
Coaching
Guide
Culture
Teach
PracDces
107. AgileManifesto.org
We are uncovering better ways of developing products by doing it
and helping others do it. Through this work we have come to value:
Over
Processes & tools
Working product
Over
Comprehensive
documentation
Customer collaboration
Over
Contract negotiation
Responding to change
Over
Following a plan
Individuals & interactions
That is, while there is value in the items on the right,
we value the items on the left more.
108. (Big) AgileManifesto.org
We are uncovering better ways of developing products by doing it
and helping others do it. Through this work we have come to value:
Individuals & interactions Supported by
Processes & tools
Working product
Supported by
Comprehensive
documentation
Customer collaboration
Supported by
Contract negotiation
Responding to change
Supported by
Following a plan
That is, while there is value in the items on the right,
we value the items on the left more.