Post on 09-May-2015
description
transcript
Agile Program and Portfolio ManagementMike Cottmeyer, President & Agile CoachLeadingAgile, LLC
Wednesday, February 6, 13
Mike Cottmeyermike@leadingagile.com404.312.1471
www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer
Wednesday, February 6, 13
Before We Start...
Wednesday, February 6, 13
Before We Start...
This is not a process overlay for your existing organization...
Wednesday, February 6, 13
Before We Start... Organiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Wednesday, February 6, 13
Before We Start... Organiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Wednesday, February 6, 13
Before We Start... Organiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Continuous
Strategic
Release
Iteration
Daily
Wednesday, February 6, 13
Before We Start... Organiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Continuous
Strategic
Release
Iteration
Daily
Wednesday, February 6, 13
Projects, Programs, Portfolios
Wednesday, February 6, 13
Agile Project Management
Scrum Team
ScrumTeam
ScrumTeam
ScrumTeam
Wednesday, February 6, 13
Agile Program Management
Scrum Team
ProgramTeam
ScrumTeam
ScrumTeam
ScrumTeam
ProgramTeam
Wednesday, February 6, 13
Agile Portfolio Management
Scrum Team
ProgramTeam
ScrumTeam
ScrumTeam
ScrumTeam
ProgramTeam
PortfolioTeam
Wednesday, February 6, 13
Enterprise Portfolio Management
Scrum Team
ProgramTeam
ScrumTeam
ScrumTeam
ScrumTeam
ProgramTeam
StrategyTeam
SupportPortfolioTeam
Wednesday, February 6, 13
How is Agile PPM Different?Business Agility at the Portfolio Level
• Want our investment portfolio to respond to the needs of changing market conditions
• We need the ability as an organization to respond to changing market conditions
Wednesday, February 6, 13
How is Agile PPM Different?Business Agility at the Portfolio Level
• Want our investment portfolio to respond to the needs of changing market conditions
• We need the ability as an organization to respond to changing market conditions
• It’s less about team level agility, although that is an essential component
Wednesday, February 6, 13
Foundational Stuff...The Anatomy of Agile Teams
Wednesday, February 6, 13
Agile Teams• Who’s involved?
• Dependencies
• Backlog
• Velocity
• Accountability
Wednesday, February 6, 13
ScrumTeam
DevelopersDevelopersWednesday, February 6, 13
ScrumTeam Developers
DevelopersDevelopersWednesday, February 6, 13
ScrumTeam Developers
Testers
DevelopersDevelopersWednesday, February 6, 13
ScrumTeam Developers
Testers
Analysts
DevelopersDevelopersWednesday, February 6, 13
ScrumTeam Developers
Testers
Analysts
DevelopersDevelopers
Lead
Wednesday, February 6, 13
ScrumTeam Developers
Testers
Analysts
DevelopersDevelopers
ScrumMaster
Lead
Wednesday, February 6, 13
ScrumTeam Developers
Testers
Analysts
DevelopersDevelopers
ScrumMaster
Product Owner
Lead
Wednesday, February 6, 13
Foundational Stuff... Time, Cost, and Scope
Wednesday, February 6, 13
Scope
CostTime
Wednesday, February 6, 13
Scope
CostTime
Wednesday, February 6, 13
CostTime
$$$
Scope
Wednesday, February 6, 13
Managing Variable ScopeHow to deal with making commitments when scope is
constantly changing
Wednesday, February 6, 13
Story Maps
Wednesday, February 6, 13
EpicEpics collec*ons of features, typically 1-‐3 months in dura*on. Epics span releases. Epics can span more than one team. These are the things senior leadership cares about.
Wednesday, February 6, 13
Epic
Feature
Epics collec*ons of features, typically 1-‐3 months in dura*on. 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 dura*on. Features are contained within releases. Features are contained within a team. These are what the Product Owner Cares about.
Wednesday, February 6, 13
Epic
Feature
User Story
Epics collec*ons of features, typically 1-‐3 months in dura*on. 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 dura*on. 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.
Wednesday, February 6, 13
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 rela*onship between User Stories
and Business Value
Wednesday, February 6, 13
Epic
Story Maps start with the iden*fica*on of larger, more strategic organiza*onal goals
Wednesday, February 6, 13
Epic
Feature
Epics are decomposed into Features that describe the value
added into the product
Wednesday, February 6, 13
Epic
Feature Feature
Epics are decomposed into Features that describe the value
added into the product
Wednesday, February 6, 13
Epic
Feature Feature Feature
Epics are decomposed into Features that describe the value
added into the product
Wednesday, February 6, 13
Epic
Feature Feature Feature Feature
Epics are decomposed into Features that describe the value
added into the product
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
Minimally Marketable Features
Wednesday, February 6, 13
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 es*mated in rela*ve units of measure called
Story Points
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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 con*nuously evaluate the Story Map to determine the Minimally Marketable Feature
Wednesday, February 6, 13
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 con*nuously evaluate the Story Map to determine the Minimally Marketable Feature
Wednesday, February 6, 13
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
Wednesday, February 6, 13
Essential View #1Velocity & Burndown
Wednesday, February 6, 13
Sprinting
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Minimally Marketable Features feed the priori*za*on of our
Sprint Planning
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Iden*fy the User Story most likely to contribute to the MMF and
build that one first
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
User Story3
Iden*fy the User Story most likely to contribute to the MMF and
build that one first
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
User Story3
Pull User Stories in priority order focusing on delivering complete
MMFs
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
User Story
User Story
3
2
Pull User Stories in priority order focusing on delivering complete
MMFs
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
User Story
User Story
3
2
It’s okay to work User Stories across MMFs if that is what the
Product Owner needs
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 es*mates each Task in Real Hours so they can assess if they can make a solid Commitment to
Deliver
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 es*mates each Task in Real Hours so they can assess if they can make a solid Commitment to
Deliver
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
And es*mates each Task in Real Hours so they can assess if they can make a solid Commitment to
Deliver
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16
At the beginning of the Sprint, The Team pulls Tasks from the top of
the Task Backlog
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16
Tasks move across the Story Board un*l there is a completed User
Story.
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16User Story
3
Tasks move across the Story Board un*l there is a completed User
Story.
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16
Tasks move across the Story Board un*l there is a completed User
Story.
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16
User Story2
The Team works from the top of the Story Board, Swarming to get User Stories across the board as
fast as possible .
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated 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 .
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16
User Story1
The Team works from the top of the Story Board, Swarming to get User Stories across the board as
fast as possible .
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
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 Es*mated Hours = 98 hours
Task 8
Task 16
Un*l the en*re Sprint has been delivered to the Product Owner.
Wednesday, February 6, 13
Measuring Progress
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
6
From a Metrics perspec*ve, we Burn Down hours to make sure
the sprint is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
From a Metrics perspec*ve, we Burn Down points to make sure
the Release is on track
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
From a Metrics perspec*ve, we Burn Down points to make sure
the Release is on track
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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.
Wednesday, February 6, 13
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 o\en!
Wednesday, February 6, 13
Essential View #2Roadmap Over Time
Wednesday, February 6, 13
Planning Horizons
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Epic Epic Epic Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch Arch
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic Epic Epic Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Progressive Elaboration
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
Epic
Feature
Epic Epic Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
Epic
Feature
Epic
Feature
Epic
Feature
Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
Epic
Feature
Epic
Feature
Epic
Feature
Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Feature Feature
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
Epic
Feature
Epic
Feature
Epic
Feature
Epic Epic Epic Epic
Q1 Q2 Q3 Q4
Feature Feature Feature
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
Epic
Feature
Epic
Feature
Epic
Feature
Epic Epic
Q1 Q2 Q3 Q4
Feature
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
Epic
Feature
Epic Epic
Q1 Q2 Q3 Q4
Feature
Wednesday, February 6, 13
Dealing with Risk
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
Epic
Feature
Epic Epic
Q1 Q2 Q3 Q4
Feature
Risk Risk
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
Epic
Feature
Epic Epic
Q1 Q2 Q3 Q4
Feature
Risk Risk
User Story User Story
Wednesday, February 6, 13
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic Epic
Risk Risk Risk Risk
Q1 Q2 Q3 Q4
Feature
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
Epic Epic
Risk Risk Risk Risk
Feature
User StoryUser Story
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
Epic Epic
Risk Risk Risk Risk
Feature
User Story
Risk
User Story
Wednesday, February 6, 13
Release Spikes
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
Epic Epic
Risk Risk Risk Risk
Feature
User Story
Risk
Spike Spike
User Story
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
Epic Epic
Risk Risk Risk Risk
Feature
User Story
Risk
Spike SpikeSpike
User Story
Wednesday, February 6, 13
Budgeting vs. Estimating
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
Epic Epic
Risk Risk Risk Risk
Feature
User Story
Risk
Spike SpikeSpike
User Story
Wednesday, February 6, 13
Essential View #3Flow
Wednesday, February 6, 13
Key Concepts• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13
Key Concepts• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13
Key Concepts• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13
Key Concepts• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13
Key Concepts• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13
Key Concepts• Flow
• Kanban
• Value Streams
• Small Batches
• WIP Limits
Wednesday, February 6, 13
n-Tier Model
Wednesday, February 6, 13
Enterprise Portfolio Model
Scrum Team
ProgramTeam
ScrumTeam
ScrumTeam
ScrumTeam
ProgramTeam
StrategyTeam
SupportPortfolioTeam
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Tier 1 - Scrum
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Analysis Design Build Test Deploy
Tier 1 - Scrum
Tier 2 - Kanban
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Tier 1 - Scrum
Tier 2 - Kanban
Tier 3 - Kanban
Wednesday, February 6, 13
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
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Tier 1 - Scrum
Tier 2 - Kanban
Tier 3 - Kanban
User Story
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Tier 1 - Scrum
Tier 2 - Kanban
Tier 3 - Kanban
Feature
User Story
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Tier 1 - Scrum
Tier 2 - Kanban
Tier 3 - KanbanEpic
Feature
User Story
Wednesday, February 6, 13
Kanban creates a Pull System across the entire portfolio that is
limited by your Actual Capacity
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
Spike
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
User Story
User Story
Spike
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
User Story
User Story
Spike
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Epic
Epic
Feature
User Story
User Story
SpikeTaskTask
Task
8 16
8
Feature
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Feature
User Story
User Story
SpikeTaskTask
Task
8 16
8
Feature
Epic
Epic
Wednesday, February 6, 13
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
SpikeTaskTask
Task
8 16
8
Feature
Epic
Wednesday, February 6, 13
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
SpikeTaskTask
Task
8 16
8
Feature
Epic
Epic
Wednesday, February 6, 13
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
SpikeTaskTask
Task
8 16
8
Feature
Epic
Epic
Feature
Wednesday, February 6, 13
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
SpikeTaskTask
Task
8 16
8
Feature
EpicEpic
Feature
Wednesday, February 6, 13
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
SpikeTaskTask
Task
8 16
8
Feature
EpicEpic
Feature
Wednesday, February 6, 13
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
816
8
Epic
Spike
Feature
Feature
Wednesday, February 6, 13
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
SpikeTaskTask
Task
816
8
Epic
Feature
Feature
Wednesday, February 6, 13
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
816
8
Spike
Epic
Feature
Feature
Wednesday, February 6, 13
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
Feature
Feature
Wednesday, February 6, 13
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
Feature
Feature
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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 Story
User Story
Spike
EpicEpic
Feature Feature
Wednesday, February 6, 13
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 Story
User Story
Spike
EpicEpic
FeatureFeature
Wednesday, February 6, 13
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 Story
User Story
Spike
EpicEpic
FeatureFeature
Wednesday, February 6, 13
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 Story
User Story
Spike
EpicEpic
FeatureFeature
Wednesday, February 6, 13
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 StoryUser Story
Spike
EpicEpic
FeatureFeature
Wednesday, February 6, 13
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 StoryUser Story
Spike
EpicEpic
FeatureFeature
Wednesday, February 6, 13
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 Story
User Story
SpikeTask
Task
Task
8
8
Wednesday, February 6, 13
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
Feature
User Story
User Story
Spike
FeatureFeature
Wednesday, February 6, 13
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
Task
8
8
FeatureFeatureFeature
8
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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 StoryTask
Task
8
8
FeatureFeatureFeature
Task 8
User Story
Spike
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
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
Wednesday, February 6, 13
Bottlenecks & Dependencies
Wednesday, February 6, 13
Enterprise Portfolio Model
Scrum Team
ProgramTeam
ScrumTeam
ScrumTeam
ScrumTeam
ProgramTeam
StrategyTeam
SupportPortfolioTeam
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Backlog
Analysis (2) Design (2) Build (3) Test (2) Deploy (1)
Inception (3) Elaboration (4) Construction (5) Transition (2)
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
Wednesday, February 6, 13
Essential View #4Progress
Wednesday, February 6, 13
Assessing ProgressHow do we visualize progress to the rest of the organization
• Start
• End
• Budget
• SWAG
• Estimate
• Actual
• % Complete
Wednesday, February 6, 13
Planned Planned Progress Budget Estimate Detail Start End
TextWednesday, February 6, 13
Epic
Planned Planned Progress Budget Estimate Detail Start End
300 280
Text
325 Sprint 1 Sprint 5
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
300
16
280
19
Text
325
21
Sprint 1
Sprint 2
Sprint 5
Sprint 4
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
300
16
5
280
19
8
Text
325
21
8
Sprint 1
Sprint 2
Sprint 2
Sprint 5
Sprint 4
Sprint 2
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
300
16
5
3
280
19
8
Text
3
325
21
8
5
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13
Pulling it all together
Wednesday, February 6, 13
Transforming the OrganizationOrganiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Wednesday, February 6, 13
Transforming the OrganizationOrganiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Wednesday, February 6, 13
Transforming the OrganizationOrganiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Continuous
Strategic
Release
Iteration
Daily
Wednesday, February 6, 13
Transforming the OrganizationOrganiza(onal+Transforma(on+
Adopt++Prac(ces+
Personal+Transforma(on+
Continuous
Strategic
Release
Iteration
Daily
Wednesday, February 6, 13
Release Burndown
38
Sprint Burndown
96
Velocity Trend
66
8
5
Everyone is focused on delivering value early and o\en!
Wednesday, February 6, 13
Q1 Q2 Q3 Q4
Arch Arch Arch Arch Arch Arch Arch ArchEpic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
User Story
Epic
Feature
User Story
Epic
Feature
User Story
Epic
Feature
Epic Epic
Risk Risk Risk Risk
Feature
User Story
Risk
Spike SpikeSpike
User Story
Wednesday, February 6, 13
Story Backlog Task Backlog In Process Task Done Story Done
Analysis Design Build Test Deploy
Inception Elaboration Construction Transition
Tier 1 - Scrum
Tier 2 - Kanban
Tier 3 - KanbanEpic
Feature
User Story
Wednesday, February 6, 13
Epic
Feature
Planned Planned Progress Budget Estimate Detail Start End
User Story
User Story
User Story
300
16
5
3
8
280
19
8
8
Text
3
325
21
8
5
8
Sprint 1
Sprint 2
Sprint 2
Sprint 3
Sprint 4
Sprint 5
Sprint 4
Sprint 2
Sprint 3
Sprint 4
Wednesday, February 6, 13