Scrum gathering vegas agile program and portfolio management

Agile Program and Portfolio Management with Scrum

Wednesday, May 8, 13

Agile Program and Portfolio Management with ScrumWhere does well groomed prioritized backlog come from... at scale?

Wednesday, May 8, 13

Mike [email protected]

www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer

Wednesday, May 8, 13

Why Scrum?

Wednesday, May 8, 13

C-Suite Value Proposition • Predictability

• Quality

• Early ROI

• Cost Savings

Wednesday, May 8, 13

C-Suite Value Proposition • Predictability

• Quality

• Early ROI

• Cost Savings

Wednesday, May 8, 13

C-Suite Value Proposition • Predictability

•Quality

• Early ROI

• Cost Savings

Wednesday, May 8, 13

C-Suite Value Proposition • Predictability

• Quality

• Early ROI

• Cost Savings

Wednesday, May 8, 13

C-Suite Value Proposition • Predictability

• Quality

• Early ROI

• Cost Savings

Wednesday, May 8, 13

Competing Delivery Goals• Emergence

• Convergence

Wednesday, May 8, 13

Competing Delivery Goals• Emergence

• Convergence

Wednesday, May 8, 13

Competing Delivery Goals• Emergence

• Convergence

Wednesday, May 8, 13

Projects, Programs, Portfolios

Wednesday, May 8, 13

Agile Project Management

Scrum Team

ScrumTeam

ScrumTeam

ScrumTeam

Wednesday, May 8, 13

Agile Program Management

Scrum Team

ProductTeam

ScrumTeam

ScrumTeam

ScrumTeam

ProductTeam

Wednesday, May 8, 13

Agile Portfolio Management

Scrum Team

ProductTeam

ScrumTeam

ScrumTeam

ScrumTeam

ProductTeam

PortfolioTeam

Wednesday, May 8, 13

Enterprise Portfolio Management

Scrum Team

ProductTeam

ScrumTeam

ScrumTeam

ScrumTeam

ProductTeam

StrategyTeam

SupportTeam

PortfolioTeam

Wednesday, May 8, 13

Foundational Stuff...Anatomy of a Scrum Team

Wednesday, May 8, 13

ScrumTeam

DevelopersDevelopersWednesday, May 8, 13

ScrumTeam Developers

DevelopersDevelopersWednesday, May 8, 13

ScrumTeam Developers

Testers

DevelopersDevelopersWednesday, May 8, 13

ScrumTeam Developers

Testers

Analysts

DevelopersDevelopersWednesday, May 8, 13

ScrumTeam Developers

Testers

Analysts

DevelopersDevelopers

Lead

Wednesday, May 8, 13

ScrumTeam Developers

Testers

Analysts

DevelopersDevelopers

ScrumMaster

Lead

Wednesday, May 8, 13

ScrumTeam Developers

Testers

Analysts

DevelopersDevelopers

ScrumMaster

Product Owner

Lead

Wednesday, May 8, 13

Teams at Every Level

Scrum Team

ProductTeam

ScrumTeam

ScrumTeam

ScrumTeam

ProductTeam

StrategyTeam

SupportTeam

PortfolioTeam

Wednesday, May 8, 13

Scrum Teams• Clarity

• Accountability

• Measurable progress

Wednesday, May 8, 13

Scrum Teams• Clarity

• Accountability

• Measurable progress

Wednesday, May 8, 13

Scrum Teams• Clarity

• Accountability

• Measurable progress

Wednesday, May 8, 13

Scrum Teams• Clarity

• Accountability

• Measurable progress

Wednesday, May 8, 13

Foundational Stuff... Time, Cost, and Scope

Wednesday, May 8, 13

Scope

CostTime

Wednesday, May 8, 13

Scope

CostTime

Wednesday, May 8, 13

CostTime

Value

Scope

Wednesday, May 8, 13

Managing Variable ScopeHow to deal with making commitments when scope is

constantly changing

Wednesday, May 8, 13

Story Maps

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Epic

Story  Maps  start  with  the  iden*fica*on  of  larger,  more  strategic  organiza*onal  goals

Wednesday, May 8, 13

Epic

Feature

Epics  are  decomposed  into  Features  that  describe  the  value  

added  into  the  product

Wednesday, May 8, 13

Epic

Feature Feature

Epics  are  decomposed  into  Features  that  describe  the  value  

added  into  the  product

Wednesday, May 8, 13

Epic

Feature Feature Feature

Epics  are  decomposed  into  Features  that  describe  the  value  

added  into  the  product

Wednesday, May 8, 13

Epic

Feature Feature Feature Feature

Epics  are  decomposed  into  Features  that  describe  the  value  

added  into  the  product

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Minimally Marketable Features

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Essential View #1Velocity & Burndown

Wednesday, May 8, 13

Sprinting

Wednesday, May 8, 13

Story  Backlog Task  Backlog In  Process Task  Done Story  Done

Minimally  Marketable  Features  feed  the  priori*za*on  of  our  

Sprint  Planning

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Measuring Progress

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Essential View #2Roadmap Over Time

Wednesday, May 8, 13

Road-mapping

Wednesday, May 8, 13

Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Epic Epic Epic Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Arch Arch Arch Arch Arch Arch Arch Arch

Wednesday, May 8, 13

Arch Arch Arch Arch Arch Arch Arch ArchEpic Epic Epic Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 13

Progressive Elaboration

Wednesday, May 8, 13

Arch Arch Arch Arch Arch Arch Arch ArchEpic

Feature

Epic

Feature

Epic Epic Epic Epic Epic Epic

Q1 Q2 Q3 Q4

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Managing Risk

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Release Spikes

Wednesday, May 8, 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, May 8, 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, May 8, 13

Budgeting vs. Estimating

Wednesday, May 8, 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, May 8, 13

Essential View #3Flow

Wednesday, May 8, 13

Key Concepts• Flow

• Value Streams

• Small Batches

• WIP Limits

Wednesday, May 8, 13

Key Concepts• Flow

• Value Streams

• Small Batches

• WIP Limits

Wednesday, May 8, 13

Key Concepts• Flow

• Value Streams

• Small Batches

• WIP Limits

Wednesday, May 8, 13

Key Concepts• Flow

• Value Streams

• Small Batches

• WIP Limits

Wednesday, May 8, 13

Key Concepts• Flow

• Value Streams

• Small Batches

• WIP Limits

Wednesday, May 8, 13

n-Tier Model

Wednesday, May 8, 13

Scrum Team

ProductTeam

ScrumTeam

ScrumTeam

ScrumTeam

ProductTeam

StrategyTeam

SupportTeam

PortfolioTeam

n-Tier Model

Wednesday, May 8, 13

Story Backlog Task Backlog In Process Task Done Story Done

Tier 1 - Scrum

Wednesday, May 8, 13

Story Backlog Task Backlog In Process Task Done Story Done

Analysis Design Build Test Deploy

Tier 1 - Scrum

Tier 2 - Kanban

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Kanban creates a Pull System across the entire portfolio that is

limited by your Actual Capacity

Wednesday, May 8, 13

Story Backlog Task Backlog In Process Task Done Story Backlog

Analysis Design Build Test Deploy

Inception Elaboration Construction Transition

Epic

Epic

Wednesday, May 8, 13

Story Backlog Task Backlog In Process Task Done Story Backlog

Analysis Design Build Test Deploy

Inception Elaboration Construction Transition

Epic

Epic

Wednesday, May 8, 13

Story Backlog Task Backlog In Process Task Done Story Backlog

Analysis Design Build Test Deploy

Inception Elaboration Construction Transition

Epic

Epic

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Bottlenecks & Dependencies

Wednesday, May 8, 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, May 8, 13

Essential View #4Progress

Wednesday, May 8, 13

Assessing ProgressHow do we visualize progress to the rest of the organization

• Start

• End

• Budget

• SWAG

• Estimate

• Actual

• % Complete

Wednesday, May 8, 13

Planned Planned Progress Budget Estimate Detail Start End

TextWednesday, May 8, 13

Epic

Planned Planned Progress Budget Estimate Detail Start End

300 280

Text

325 Sprint 1 Sprint 5

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Pulling it all together

Wednesday, May 8, 13

Release  Burndown

38

Sprint  Burndown

96

Velocity  Trend

66

8

5

Wednesday, May 8, 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, May 8, 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, May 8, 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, May 8, 13

Done  Develop    and  Test  

Ready  To  Build  

Detailed  Planning  

Release  Targe6ng  

Feasibility  Study  

Market  Research  New  Concept  

Development Flow

Feature  Complete  

Integra6on  Tes6ng  

Develop  and  Test  

Story  Review  

Story    Mapping  

Feature  Breakdown  

Story    Done  

Task  Done  

Task  In  Process  

Task  Ready  

Story  Backlog  

KANBAN

 FEAT

URE

STORY

EPICS  

KANBAN

SCRUM  

The Epic Tier

•  Idea  list  genera<on  from  mul<ple  data  feeds  and  sources  

•  Market  Research  •  Customer  Research  •  Field  Feedback  •  Business  Case  &  ROI  •  Compe<<ve  Analysis  

•  High  Level  Es<ma<on  •  Solu<on  Cost  •  High  Level  Architecture    •  Risk  Analysis  •  Feasibility  

•  Detailed  Architecture  •  Feature  Mapping  •  Acceptance  Criteria  •  Es<ma<on  •  Backlog  

•  All  features  are  done  •  Regression  tests  are  completed    •  Release  Criteria  are  met  

•  Forced  Priority  •  Certainty    Curve  

Done  Develop    and  Test  

Ready  To  Build  

Detailed  Planning  

Release  Targe6ng  

Feasibility  Study  

Market  Research  New  Concept  

Epic Tier Ownership

R  A  C  I    

Product  Management  Product  Management  Customer  Advocate  PorLolio  Team    

R  A  C  I    

Product  Owner  Team  Product  Owner  Team  Engineering  PorLolio  Team    

R  A  C  I    

Product  Owner  Team  Product  Owner  Team  Engineering  PorLolio  Team    

R  A  C  I    

Engineering  Product  Owner  Team  Customer  Advocate  PorLolio  Team    

PorLolio  Team  

R  A  C  I    

Product  Management  Product  Management  Customer  Advocate  Product  Owner  Team  

R  A  C  I    

Product  Management  Product  Management  Customer  Advocate  Product  Owner  Team  

•  Responsible  -­‐  Those  who  do  the  work  to  achieve  the  task.  •  Accountable  -­‐  The  one  ul<mately  answerable  for  the  correct  and  thorough  comple<on  of  the  deliverable.  •  Consulted  -­‐  Those  whose  opinions  are  sought,  typically  subject  maRer  experts;  and  with  whom  there  is  two-­‐way  communica<on.  •  Informed  -­‐  Those  who  are  kept  up-­‐to-­‐date  on  progress,  oUen  only  on  comple<on  of  the  task  or  deliverable.  

GATE  RESPONSIBLITY  

Done  Develop    and  Test  

Ready  To  Build  

Detailed  Planning  

Release  Targe6ng  

Feasibility  Study  

Market  Research  New  Concept  

The Feature Tier

•  Feature  List  for  the  Parent  Epic  

•  Story  Wri<ng  •  MMF  •  Es<ma<ng  •  High  Level  Design  •  UX  Mockups  

•  Es<mate  Sanity  Check  •  Spike  Iden<fica<on  •  Review  for  Feasibility  •  Review  of  Acceptance  Criteria  •  Story  Spanning  •  Story  Tasking  

•  Feature  Tes<ng  Non-­‐Func<onal  •  Valida<on  of  Automated  Tests  

•  Detailed  Design  •  Code  •  Unit  Test  •  Code  Review  •  Func<onal  Test  •  User  Story    •  Product  Owner  Acceptance  

Feature  Complete  

Integra6on  Tes6ng  

Develop  and  Test  

Story  Review  

Story    Mapping  

Feature  Breakdown  

•  All  Stories  are  done  •  Feature  Level  tes<ng  is  completed  •  Defect  criteria  are  met  •  Feature  Check  list    from  RDS  template  •  Performance  and  Sizing  Complete  

* Stand alone features must have these acceptance criteria (x, x, x)

Feature Tier Ownership

•  Responsible  -­‐  Those  who  do  the  work  to  achieve  the  task.  •  Accountable  -­‐  The  one  ul<mately  answerable  for  the  correct  and  thorough  comple<on  of  the  deliverable.  •  Consulted  -­‐  Those  whose  opinions  are  sought,  typically  subject  maRer  experts;  and  with  whom  there  is  two-­‐way  communica<on.  •  Informed  -­‐  Those  who  are  kept  up-­‐to-­‐date  on  progress,  oUen  only  on  comple<on  of  the  task  or  deliverable.  

R  A  C  I    

Product  Owner  Team  Product  Owner  Team  Customer  Advocate  Engineering  

R  A  C  I    

Engineering    Product  Owner  Team  Product  Owner  Team  Product  Owner  Team    

R  A  C  I    

Engineering    Engineering    Product  Owner  Team  Product  Owner  Team  

R  A  C  I    

Engineering  Engineering    Product  Owner  Team  Product  Owner  Team    

R  A  C  I    

Product  Owner  Team  Product  Owner  Team  Engineering  Engineering  

R  A  C  I    

Product  Owner  Team  Product  Owner  Team  Engineering  PorLolio  

Product  Owner  Team  GATE  RESPONSIBLITY  

Engineering  Team  GATE  RESPONSIBLITY  

Engineering  Team  GATE  RESPONSIBLITY  

Product  Owner  Team  GATE  RESPONSIBLITY  

Feature  Complete  

Integra6on  Tes6ng  

Develop  and  Test  

Story  Review  

Story    Mapping  

Feature  Breakdown  

The Story Tier

Story    Done  

Task  Done  

Task  In  Process  

Task  Ready  

Story  Backlog  

•  Story  List  for  the  Parent  Feature  

•  Approved  task  of  8  hours  or  less  

•  SCRUM  team  completes  the  task  

•  Task  is  done  and  communicated  in  the  standup  

   Documented  • The  User  Story    • Acceptance  Criteria  • Conversa<ons    • Level  of  Value  • Level  of  Effort  • Design  Assump<ons  • Design  Documented  (op<onal)    • UI  Documented  (op<onal)          Coded  • Checked  Into  integrated  build  • Simple  Design    • Documented  with  Comments  • Automated  Tests  for  New  Features      Tested  • Tes<ng  is  complete    • Defect  Criteria  Met    • Automated  Tes<ng  Passed    Approved  • Feature  Complete  (Scrum  Master)  • Test  Complete  (QA  Lead)  • Accepted  (Product  Owner)    

* Stand alone stories must have these acceptance criteria (x, x, x)

Story Tier Ownership

•  Responsible  -­‐  Those  who  do  the  work  to  achieve  the  task.  •  Accountable  -­‐  The  one  ul<mately  answerable  for  the  correct  and  thorough  comple<on  of  the  deliverable.  •  Consulted  -­‐  Those  whose  opinions  are  sought,  typically  subject  maRer  experts;  and  with  whom  there  is  two-­‐way  communica<on.  •  Informed  -­‐  Those  who  are  kept  up-­‐to-­‐date  on  progress,  oUen  only  on  comple<on  of  the  task  or  deliverable.  

R  A  C  I    

Product  Owner  Product  Owner  Customer  Advocate  Engineering  

R  A  C  I    

Engineering  Engineering  Engineering  Engineering  

R  A  C  I    

Engineering    Engineering    Engineering  Engineering  

R  A  C  I    

Engineering  Product  Owner  Engineering    Engineering  

R  A  C  I    

Engineering  Engineering  Engineering  Engineering  

Story    Done  

Task  Done  

Task  In  Process  

Task  Ready  

Story  Backlog