scrum and kanban in the enterprise webinar
TRANSCRIPT
Blending Scrum and Kanban to Create an End-to-End Agile Enterprise
Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLC
www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer
Agenda
• Why this talk? Isn’t Scrum enough?
Agenda
• Why this talk? Isn’t Scrum enough?• Discuss what end-to-end business agility looks
like and how it is different from team agility
Agenda
• Why this talk? Isn’t Scrum enough?• Discuss what end-to-end business agility looks
like and how it is different from team agility, and why team agility is not enough
Agenda
• Why this talk? Isn’t Scrum enough?• Discuss what end-to-end business agility looks
like and how it is different from team agility, and why team agility is not enough
• Explore one adoption and transformation strategy… and maybe a few alternatives
Agenda
• Why this talk? Isn’t Scrum enough?• Discuss what end-to-end business agility looks
like and how it is different from team agility, and why team agility is not enough
• Explore one adoption and transformation strategy… and maybe a few alternatives
• Show how to manage the flow of value across the enterprise, using Scrum at the team level, and Kanban at the Program and Portfolio level
Why Not Just Scrum?
Scrum is a team based approach to product delivery.
Team
Developers
DevelopersTesters
Developers
Analyst
Testers
Developers
ScrumMasterAnalyst
Testers
Product Owner
Analyst
TestersDevelopers
ScrumMaster
What if my team is more than 5-7 people?
Scrum in the Enterprise
Scrum in the Enterprise
Enterprise Scrum
Enterprise Scrum... it’s different!
Enterprise Scrum
Enterprise Scrum
Enterprise Scrum
Enterprise Scrum
Enterprise Scrum
Enterprise Scrum
Enterprise Scrum
What breaks Scrum?
External Dependencies
External Dependencies
External Dependencies
Why dependencies matter?
• Velocity dependent on something outside the team
Why dependencies matter?
• Velocity dependent on something outside the team
• External dependencies have to be managed and planned for in advance
Why dependencies matter?
• Velocity dependent on something outside the team
• External dependencies have to be managed and planned for in advance
• Excessive forward planning can reduce our ability to change as we learn new things
Why dependencies matter?
• Velocity dependent on something outside the team
• External dependencies have to be managed and planned for in advance
• Excessive forward planning can reduce our ability to change as we learn new things
• Lack of full ownership can result in lack of commitment and unreliable results
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Many-to-Many Relationships
Why many-to-many matters?
• Team velocity is not a predictor of higher order deliverables
Why many-to-many matters?
• Team velocity is not a predictor of higher order deliverables
• One or more teams can starve the value creation process
Why many-to-many matters?
• Team velocity is not a predictor of higher order deliverables
• One or more teams can starve the value creation process
• Backlogs have to be sequenced and dependencies managed
Why many-to-many matters?
• Team velocity is not a predictor of higher order deliverables
• One or more teams can starve the value creation process
• Backlogs have to be sequenced and dependencies managed
• Teams focus on their backlog to the exclusion of the rest of the organization
What do we mean by end-to-end business agility?
We want the benefits of team-level agility….
We want the benefits of team-level agility…. but across the entire company
We want a pattern that can accommodate Sales and Marketing…
…several Scrum teams, service orientation, and shared services…
…as well as technical support and ultimately sustaining engineering
At some level of scale, Scrum breaks.
At some level of scale, Scrum breaks. What are you going to do about it?
Tools available to scale Scrum
• Scrum and XP
Tools available to scale Scrum
• Scrum and XP• Kanban
Tools available to scale Scrum
• Scrum and XP• Kanban• Lean
Tools available to scale Scrum
• Scrum and XP• Kanban• Lean• RUP
Tools available to scale Scrum
• Scrum and XP• Kanban• Lean• RUP• Traditional SDLC
Interesting idea… how to we get there?
It always starts with teams...
Ways to organize teams…
• Products
Ways to organize teams…
• Products• Product features
Ways to organize teams…
• Products• Product features• Components
Ways to organize teams…
• Products• Product features• Components• Shared services
Ways to organize teams…
• Products• Product features• Components• Shared services• Business capabilities
Get the teams working…
• Define the org structure
Get the teams working…
• Define the org structure• Form the teams
Get the teams working…
• Define the org structure• Form the teams• Get the teams delivering
Get the teams working…
• Define the org structure• Form the teams• Get the teams delivering• Focus on establishing a
stable velocity
Get the teams working…
• Define the org structure• Form the teams• Get the teams delivering• Focus on establishing a
stable velocity• Learn what works
Incrementally roll-out Scrum across the organization…
Incrementally roll-out Scrum across the organization……
Incrementally roll-out Scrum across the organization………
Establish Program Teams and/or Product Integration teams
Establish Program Teams and/or Product Integration teams
Establish a Portfolio Planning team
Manage the flow of value at each level
So… what does it look like when I am done?
Focus is 100% on delivering end-to-end value across the organization
“If all we do is find another way to measure activity, we will not be successful” – CTO
Let’s start with a definition of value…
EpicEpics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about.
Epic
Feature
Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about.
Features are smaller than epics, typically 2-4 weeks in duration. Features are contained within releases. Ideally, features are contained within a team. These are what the Product Owner Cares about.
Epic
Feature
User Story
Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about.
Features are smaller than epics, typically 2-4 weeks in duration. Features are contained within releases. Ideally, 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.
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Story Maps visually show the relationship between User Stories and Business Value
Epic
Story Maps start with the identification of larger, more strategic organizational goals
Epic
Feature
Epics are decomposed into Features that describe the
value added into the product
Epic
Feature Feature
Epics are decomposed into Features that describe the
value added into the product
Epic
Feature Feature Feature
Epics are decomposed into Features that describe the
value added into the product
Epic
Feature Feature Feature Feature
Epics are decomposed into Features that describe the
value added into the product
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
Features are decomposed into User Stories that are thin slices of value added into the system
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Features are decomposed into User Stories that are thin slices of value added into the system
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Features are decomposed into User Stories that are thin slices of value added into the system
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Features are decomposed into User Stories that are thin slices of value added into the system
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
User Stories are estimated in relative units of measure
called Story Points
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
11 7 12 8
Story Points can be added up to size Features
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
11 7 12 8
38 Feature Points can be added up to size Epics
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
11 7 12 8
38 Our Goal is to build the smallest system possible to deliver the value in the Epic
Epic
Feature
User Story
Feature Feature Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
11 7 12 8
38 We continuously evaluate the Story Map to determine the
Minimally Marketable Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Epic
Feature Feature Feature Feature
User Story
User Story
User Story
11 7 12 8
38
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
We continuously evaluate the Story Map to determine the
Minimally Marketable Feature
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
User Story
Epic
Feature Feature Feature Feature
User Story
User Story
User Story
10 4 5 7
26
3
2
5
1
1
3
2
1
2
5
3
2
1
3
2
2
When we focus on Minimally Marketable Features, we
deliver Business Value early
Story Backlog Task Backlog In Process Task Done Story Backlog
Minimally Marketable Features feed the prioritization of our
Sprint Planning
Story Backlog Task Backlog In Process Task Done Story Backlog
Identify the User Story most likely to contribute to the
MMF and build that one first
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
3
Identify the User Story most likely to contribute to the
MMF and build that one first
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
3
Pull User Stories in priority order focusing on delivering
complete MMFs
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
3
2
Pull User Stories in priority order focusing on delivering
complete MMFs
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
3
2
It’s okay to work User Stories across MMFs if that is what the Product Owner needs
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
3
2
1
It’s okay to work User Stories across MMFs if that is what the Product Owner needs
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
3
2
1
Planned Team Velocity = 6 points
The team uses its past velocity to determine how many stories go in the Sprint
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
3
2
1
Planned Team Velocity = 6 points
The Team breaks each User Story down into Tasks
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
3
2
1
Task Task
TaskTask
Planned Team Velocity = 6 points
The Team breaks each User Story down into Tasks
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
Planned Team Velocity = 6 points
The Team breaks each User Story down into Tasks
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8 16
8
Planned Team Velocity = 6 points
And estimates each Task in Real Hours so they can assess
if they can make a solid Commitment to Deliver
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8 16
8
16 2
48
Planned Team Velocity = 6 points
And estimates each Task in Real Hours so they can assess
if they can make a solid Commitment to Deliver
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8 16
8
16 2
48
8 4
16 8
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
And estimates each Task in Real Hours so they can assess
if they can make a solid Commitment to Deliver
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
TaskTask
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8 16
8
16 2
48
8 4
16 8
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
And estimates each Task in Real Hours so they can assess
if they can make a solid Commitment to Deliver
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8
16 2
48
8 4
16 8
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
At the beginning of the Sprint, The Team pulls Tasks from the
top of the Task Backlog
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8
16 2
48
8 4
16 8
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
Tasks move across the Story Board until there is a
completed User Story.
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
Task
Task Task
Task
Task Task
Task Task
2
1
Task
8
16 2
48
8 4
168
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16User Story
3
Tasks move across the Story Board until there is a
completed User Story.
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8
16 2
48
8 4
168
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
Tasks move across the Story Board until there is a
completed User Story.
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
Task
Task Task
Task
Task Task
TaskTask
3
1
Task
8
16 2
48
8 4
168
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
User Story
2
The Team works from the top of the Story Board, Swarming to get User Stories across the
board as fast as possible .
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
Task
Task Task
Task
Task Task
TaskTask
3
2
1
Task
8
16 2
48
8 4
168
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
The Team works from the top of the Story Board, Swarming to get User Stories across the
board as fast as possible .
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
Task
Task Task
Task
Task Task
Task Task
3
2Task
8
16 2
48
8 4
168
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
User Story
1
The Team works from the top of the Story Board, Swarming to get User Stories across the
board as fast as possible .
Story Backlog Task Backlog In Process Task Done Story Backlog
User Story
User Story
User Story
Task
Task Task
Task
Task Task
Task Task
3
2
1
Task
8
16 2
48
8 4
168
Planned Team Velocity = 6 pointsPlanned Estimated Hours = 98 hours
Task 8
Task 16
Until the entire Sprint has been delivered to the Product
Owner.
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspective, we Burn Down hours to make
sure the sprint is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
From a Metrics perspective, we Burn Down points to make
sure the Release is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
From a Metrics perspective, we Burn Down points to make
sure the Release is on track
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
We track Velocity Trend to make sure the team is
delivering in a Predictable manner
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
When the Release is ready to deliver, The Team has
completed the highest priority User Stories, against the
highest priority Features ,against the highest
priority Epics.
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
When the Release is ready to deliver, The Team has
completed the highest priority User Stories, against the
highest priority Features ,against the highest
priority Epics.
Everyone is focused on delivering value early and often!
Team
Team
Team
Team
Team
Team
Team
Team
Team
Team
Team
Team
Team
Team
Team
How do we establish the relationship between team level velocity and enterprise level flow of value?
EpicTeam predictability is one thing, but organizations need to be able to track value at the Epic level
Epic
Feature
Team predictability is one thing, but organizations need to be able to track value at the Epic level
We need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features.
Epic
Feature
User Story
Team predictability is one thing, but organizations need to be able to track value at the Epic level
We need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features.
All of our day-to-day activities need to clearly map to enterprise objectives. We need to build product as one organization
Story Backlog Task Backlog In Process Task Done Story Backlog
Tier 1 - Scrum
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Tier 1 - Scrum
Tier 2 - Kanban
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Tier 1 - Scrum
Tier 2 - Kanban
Tier 3 - Kanban
Kanban creates a pull system across the entire portfolio that is limited by your actual capacity
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Spike
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
User StoryUser
Story
Spike
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
User StoryUser
Story
Spike TaskTask
Task
8 16
8
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Feature
User StoryUser
Story
Spike TaskTask
Task
8 16
8
Feature
Epic
Epic
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
Spike TaskTask
Task
8 16
8
Feature
Epic
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
Spike TaskTask
Task
8 16
8
Feature
Epic
Epic
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
Spike TaskTask
Task
8 16
8
Feature
Epic
Epic
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
SpikeTaskTask
Task
8 16
8
Feature
EpicEpic
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
SpikeTaskTask
Task
8 16
8
Feature
EpicEpic
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
TaskTask
Task
8 16
8
Epic
Spike
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User StoryUser
Story
SpikeTaskTask
Task
8 16
8
Epic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
User Story
User Story
TaskTask
Task
8 16
8
Spike
Epic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Task
Task
Task
8
16
8 User Story
Spike User Story
Epic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Task
Task
Task
8
16
8 User Story
Spike User Story
Epic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
FeatureFeature
Task
Task
Task
8
16
8 User Story
Spike User Story
Epic
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
FeatureFeature
Task
Task
Task
8
16
8 User Story
Spike User Story
Epic
Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
FeatureFeature
Task
Task
Task
8
16
8 User Story
Spike User Story
Epic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature Feature
Task
Task
Task
8
16
8
User StoryUser
Story
Spike
EpicEpic
Feature Feature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature Feature
Task
Task
Task
8
16
8
User StoryUser
Story
Spike
EpicEpic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature Feature
Task
Task
Task
8
16
8
User StoryUser
Story
Spike
EpicEpic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature Feature
TaskTask
Task
816
8
User StoryUser
Story
Spike
EpicEpic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature Feature
Task
TaskTask
8
16
8User Story
User Story
Spike
EpicEpic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature Feature
Task
TaskTask
8
16
8User Story
User Story
Spike
EpicEpic
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Feature
Task
TaskTask
8
16
8User Story
Spike
User Story
Epic
FeatureFeatureFeature
User StoryUser
Story
SpikeTask
Task
Task
8
8
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
EpicEpic
Feature
Feature
Task
TaskTask
8
16
8User Story
Spike
User Story
Epic
Feature
User StoryUser
Story
Spike
FeatureFeature
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User StoryUser
Story
SpikeTask
Task
Task
8
8
FeatureFeatureFeature
8
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User StoryUser
Story
SpikeTask
Task
8
8
FeatureFeatureFeature
Task 8
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
User Story
SpikeTask
Task
8
8
FeatureFeatureFeature
Task 8
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
Task
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
Task
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
Task
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
Task
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
Task
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Feature
Feature
Epic Epic
User Story
Task
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Epic
Feature
User Story
User Story
SpikeTask
Task
Task
8
8 Task 8
Task 8
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
At the team level, velocity metrics drive predictability
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
At the team level, velocity metrics drive predictability
At the program/product level, lean metrics are more meaningful
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
At the team level, velocity metrics drive predictability
At the program/product level, lean metrics are more meaningful
At the enterprise level, lean metrics are also the more interesting metric
Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLC
www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer