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

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 3

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 4

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 5

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 6

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 7

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 8

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 9

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 10

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

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 11

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

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 12

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 implementation

•  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

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 13

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 14

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

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 15

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 16

“He without bad habits has seven”

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 17

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

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 18

Failure Demand

Value Demand

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 19

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 20

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 21

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 22

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 23

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 24

“The Principle of Queuing Waste: Queues are the root cause of the majority of economic waste in product development”

(Reinertsen, 2009).

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 25

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.

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 26

Design

Done Accepted

Coding

(2)

Code Review

(2)

Test Analysis

(2)

Design Review

(1)

SCM Updates

(1)

Planned (10)

Ready (5)

In Progress

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 27

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)

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)

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 28

Planned Ready In Progress Done Accepted Requested 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

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 29

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 30

Feature A Feature B Feature C Feature D Feature E

© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 31

Business Unit

Product

Team Team

Product

Team Team Team

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)

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 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)

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)'

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)'

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)'

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)'

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)'

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)

Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. 32

Thank you.

©2013 Rally Software Development Corp "#RallyON13! www.rallydev.com/rallyon/europe!