Portfolio Management and Organization Flow

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1
Ken Power, Tom Lambert
Cisco Systems
17 September 2013

Request Planned Ready
Analysis
Done Accepted
System
Testing
Design Coding
Code
Review
Code
Updates
Testing
Test
Complete
System
Test Done
Deployed
to Staging
Verification
Deployed
to Live
In Progress
Deployed

Ideas List
Portfolio
Backlog
Discovery
Period
Portfolio
Release
Backlog
Team
Release
Planning
Portfolio
Release
Planning
PSI
Commit
Checkpoint
(Ready)
•  Wish list
items, incl.
MVO list,
stretch list
•  Release
Strategy
•  Feature
descriptions
•  Portfolio sizes
•  UX deliverables
•  Architecture
deliverables
•  Spikes /
Research
•  Analysis
•  Use Cases
•  Epics
•  Prioritized
portfolio
backlog for
the 10.0
release •  Commit
event for
next PSI
Release
•  Prioritized backlog per
team
•  User Stories
•  Roadmap for next 3
PSIs with appropriate
degrees of confidence
•  Sprint goals
Primary
Deliverables

Request
Portfolio
Review
POs
Manage
Backlogs
Delivery
Team(s)
Architecture
Evaluation
Identify
Feature
Prime
“I have an
idea or a
problem to
solve”
•  Priioritize
this request
•  Align with
Portfolio
•  Technical
evaluation
•  Decide the
appropriate
place for
implementati
on
•  Architecture
consistency
•  Detailed
Technical
evaluation
•  End-to-end
consistency
•  Work across
entire VS
•  Prioritize
work within
a Product or
Component
•  Consider all
sources of
input
•  Design, develop,
deliver
Release
Products
Low-Level Story
Acceptance Criteria
Acceptance Criteria
Low-Level Story
Acceptance Criteria
Acceptance Criteria
Low-Level Story
Acceptance Criteria
Acceptance Criteria
User Story
Acceptance Criteria
Acceptance Criteria
User Story
Acceptance Criteria
Acceptance Criteria
User Story
Acceptance Criteria
Acceptance Criteria
User Story
Acceptance Criteria
Acceptance Criteria
Low-Level Story
Acceptance Criteria
Acceptance Criteria
Low-Level Story
Acceptance Criteria
Acceptance Criteria
Low-Level Story
Acceptance Criteria
Acceptance Criteria

Lead Time
Planned Ready In Progress Done Accepted
Exit Policy:
Meets
Definition of
Ready
(5)
Requested Deployed
Exit Policy:
Meets
Definition of
Done
Exit Policy:
Item meets
Acceptance
Criteria
Exit Policy:
Ready to be
deployed
Exit Policy:
Prioritized for
grooming
(3)
Exit Policy:
Targeted for a
specific
release
Exit Policy:
Feature is in
active use
(10)
Cycle Times
Flow

“He without
bad habits
has seven”

Extra Features
• Features that are not wanted
• Do not have an economically justified
need
Handovers
• Includes tacit knowledge lost when work
is handed off between people or groups
• Causes delays.
Failure Demand
• Demand created on our system because
of something we did wrong, or failed to
do.
• Includes Defects, Technical Debt, Work
caused by poor docs or service
Work In Progress
• Work that does not yet meet its Definition
of Done
• Hides problems
Task Switching
• Waste caused by working on multiple
tasks at the same time and the time lost
in switching between them.
• Decreases productivity.
Unnecessary Motion
• Difficult to see in software development.
Often caused by inattention to team
environment and workspace layout, e.g.,
teams not co-located
Unmet Human Potential
• Underutilization of people and in
particular their ideas and creative input to
make improvements
Extra Processes
• Aspects of the process used by the team,
or mandated by the organization, that do
not add value.
• Process that cause knowledge to be lost,
forcing relearning to occur.
Delays
• Slow down or inhibit movement
• Slow down feedback and hinder learning
• The fastest learner wins (Ries)
• Can occur anywhere along Value Stream

Failure Demand
Value Demand

“The Principle of Queuing Waste:
Queues are the root cause of the
majority of economic waste in
product development”
(Reinertsen, 2009).

A single “In Progress” queue is not always
sufficient to see what is happening
Planned
(10)
Ready
(5)
In Progress
(7)
Done Accepted
This is our Ready
policy. Thanks for
reading.
This is our Ready
policy. Thanks for
reading.

Design
Done Accepted
Coding
(2)
Code
Review
(2)
TestAnalysis
(2)
Design
Review
(1)
SCM
Updates
(1)
Planned
(10)
Ready
(5)
In Progress

Exit Policy:
Meets
Definition of
Ready
(5)
Requested Deployed
Exit Policy:
Meets
Definition of
Done
Exit Policy:
Item meets
Acceptance
Criteria
Exit Policy:
Ready to be
deployed
Exit Policy:
Prioritized for
grooming
(3)
Queue In
Process
Queue In
Process
Queue In
Process
Queue In
Process
Queue In
Process
Queue In
Process
Exit Policy:
Targeted for a
specific release
Exit Policy:
Feature is in
active use
(10)

Planned Ready In Progress Done AcceptedRequested Deployed
Lead Time
Delivery
Cycle Time
Acceptance
Cycle Time
Deployment
Cycle Time
Work Wait
Time
Portfolio
Planning
Time
Portfolio
Team
Product
Owners
Delivery
Teams
Product
Owners
Release
Management
Discovery
Time
Product
Owners
Total Reaction Cycle Time Total Delivery Cycle Time

Feature A
Feature B
Feature C
Feature D
Feature E

Business
Unit
Product
Team Team
Product
Team Team Team
Exit Policy:
Meets
Definition of
Ready
(5)
Requested Deployed
Exit Policy:
Meets
Definition of
Done
Exit Policy:
Item meets
Acceptance
Criteria
Exit Policy:
Ready to be
deployed
Exit Policy:
Prioritized for
grooming
(3)
Queue In
Process
Queue In
Process
Queue In
Process
Queue In
Process
Queue In
Process
Queue In
Process
Exit Policy:
Targeted for a
specific release
Exit Policy:
Feature is in
active use
(10)
Exit Policy:
Meets
Definition of
Ready
(5)
Requested Deployed
Exit Policy:
Meets
Definition of
Done
Exit Policy:
Item meets
Acceptance
Criteria
Exit Policy:
Ready to be
deployed
Exit Policy:
Prioritized for
grooming
(3)
Exit Policy:
Targeted for a
specific
release
Exit Policy:
Feature is in
active use
(10)
Planned' Ready' In'Progress' Done' Accepted'
Exit'Policy:'
Meets'Defini:on'
of'Ready'
(5)'
Exit'Policy:'
Meets'Defini:on'
of'Done'
Exit'Policy:'Item'
meets'
Acceptance'
Criteria'
Exit'Policy:'
Ready'to'be'
deployed'
Exit'Policy:'
Priori:zed'for'
grooming'
(3)'(10)'
Exit'Policy:'
Meets'Defini:on'
of'Ready'
(5)'
Exit'Policy:'
Meets'Defini:on'
of'Done'
Exit'Policy:'Item'
meets'
Acceptance'
Criteria'
Exit'Policy:'
Ready'to'be'
deployed'
Exit'Policy:'
Priori:zed'for'
grooming'
(3)'(10)'
Exit'Policy:'
Meets'Defini:on'
of'Ready'
(5)'
Exit'Policy:'
Meets'Defini:on'
of'Done'
Exit'Policy:'Item'
meets'
Acceptance'
Criteria'
Exit'Policy:'
Ready'to'be'
deployed'
Exit'Policy:'
Priori:zed'for'
grooming'
(3)'(10)'
Exit'Policy:'
Meets'Defini:on'
of'Ready'
(5)'
Exit'Policy:'
Meets'Defini:on'
of'Done'
Exit'Policy:'Item'
meets'
Acceptance'
Criteria'
Exit'Policy:'
Ready'to'be'
deployed'
Exit'Policy:'
Priori:zed'for'
grooming'
(3)'(10)'
Exit'Policy:'
Meets'Defini:on'
of'Ready'
(5)'
Exit'Policy:'
Meets'Defini:on'
of'Done'
Exit'Policy:'Item'
meets'
Acceptance'
Criteria'
Exit'Policy:'
Ready'to'be'
deployed'
Exit'Policy:'
Priori:zed'for'
grooming'
(3)'(10)'
Exit Policy:
Meets
Definition of
Ready
(5)
Requested Deployed
Exit Policy:
Meets
Definition of
Done
Exit Policy:
Item meets
Acceptance
Criteria
Exit Policy:
Ready to be
deployed
Exit Policy:
Prioritized for
grooming
(3)
Exit Policy:
Targeted for a
specific
release
Exit Policy:
Feature is in
active use
(10)

Portfolio Management and Organization Flow

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Portfolio Management and Organization Flow (20)

More from Ken Power (8)

Recently uploaded (20)

Portfolio Management and Organization Flow