Successfully reported this slideshow.

More Related Content

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Scrum gathering vegas agile program and portfolio management

  1. 1. Agile Program and Portfolio Management with Scrum Wednesday, May 8, 13
  2. 2. Agile Program and Portfolio Management with Scrum Where does well groomed prioritized backlog come from... at scale? Wednesday, May 8, 13
  3. 3. Mike Cottmeyer mike@leadingagile.com 404.312.1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile linkedin.com/in/cottmeyer Wednesday, May 8, 13
  4. 4. Why Scrum? Wednesday, May 8, 13
  5. 5. C-SuiteValue Proposition • Predictability • Quality • Early ROI • Cost Savings Wednesday, May 8, 13
  6. 6. C-SuiteValue Proposition •Predictability • Quality • Early ROI • Cost Savings Wednesday, May 8, 13
  7. 7. C-SuiteValue Proposition • Predictability •Quality • Early ROI • Cost Savings Wednesday, May 8, 13
  8. 8. C-SuiteValue Proposition • Predictability • Quality •Early ROI • Cost Savings Wednesday, May 8, 13
  9. 9. C-SuiteValue Proposition • Predictability • Quality • Early ROI •Cost Savings Wednesday, May 8, 13
  10. 10. Competing Delivery Goals • Emergence • Convergence Wednesday, May 8, 13
  11. 11. Competing Delivery Goals •Emergence • Convergence Wednesday, May 8, 13
  12. 12. Competing Delivery Goals • Emergence •Convergence Wednesday, May 8, 13
  13. 13. Projects, Programs, Portfolios Wednesday, May 8, 13
  14. 14. Agile Project Management Scrum Team Scrum Team Scrum Team Scrum Team Wednesday, May 8, 13
  15. 15. Agile Program Management Scrum Team Product Team Scrum Team Scrum Team Scrum Team Product Team Wednesday, May 8, 13
  16. 16. Agile Portfolio Management Scrum Team Product Team Scrum Team Scrum Team Scrum Team Product Team Portfolio Team Wednesday, May 8, 13
  17. 17. Enterprise Portfolio Management Scrum Team Product Team Scrum Team Scrum Team Scrum Team Product Team Strategy Team Support Team Portfolio Team Wednesday, May 8, 13
  18. 18. Foundational Stuff... Anatomy of a Scrum Team Wednesday, May 8, 13
  19. 19. Scrum Team Wednesday, May 8, 13
  20. 20. Scrum Team Developers Wednesday, May 8, 13
  21. 21. Scrum Team Developers Testers Wednesday, May 8, 13
  22. 22. Scrum Team Developers Testers Analysts Wednesday, May 8, 13
  23. 23. Scrum Team Developers Testers Analysts Lead Wednesday, May 8, 13
  24. 24. Scrum Team Developers Testers Analysts ScrumMaster Lead Wednesday, May 8, 13
  25. 25. Scrum Team Developers Testers Analysts ScrumMaster Product Owner Lead Wednesday, May 8, 13
  26. 26. Teams at Every Level Scrum Team Product Team Scrum Team Scrum Team Scrum Team Product Team Strategy Team Support Team Portfolio Team Wednesday, May 8, 13
  27. 27. Scrum Teams • Clarity • Accountability • Measurable progress Wednesday, May 8, 13
  28. 28. Scrum Teams • Clarity • Accountability • Measurable progress Wednesday, May 8, 13
  29. 29. Scrum Teams • Clarity • Accountability • Measurable progress Wednesday, May 8, 13
  30. 30. Scrum Teams • Clarity • Accountability • Measurable progress Wednesday, May 8, 13
  31. 31. Foundational Stuff... Time, Cost, and Scope Wednesday, May 8, 13
  32. 32. Scope CostTime Wednesday, May 8, 13
  33. 33. Scope CostTime Wednesday, May 8, 13
  34. 34. CostTime Value Scope Wednesday, May 8, 13
  35. 35. ManagingVariable Scope How to deal with making commitments when scope is constantly changing Wednesday, May 8, 13
  36. 36. Story Maps Wednesday, May 8, 13
  37. 37. Epic 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.   Wednesday, May 8, 13
  38. 38. 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
  39. 39. 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
  40. 40. 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
  41. 41. Epic Story  Maps  start  with  the   iden*fica*on  of  larger,  more   strategic  organiza*onal  goals Wednesday, May 8, 13
  42. 42. Epic Feature Epics  are  decomposed  into   Features  that  describe  the  value   added  into  the  product Wednesday, May 8, 13
  43. 43. Epic Feature Feature Epics  are  decomposed  into   Features  that  describe  the  value   added  into  the  product Wednesday, May 8, 13
  44. 44. Epic Feature Feature Feature Epics  are  decomposed  into   Features  that  describe  the  value   added  into  the  product Wednesday, May 8, 13
  45. 45. Epic Feature Feature Feature Feature Epics  are  decomposed  into   Features  that  describe  the  value   added  into  the  product Wednesday, May 8, 13
  46. 46. 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
  47. 47. 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
  48. 48. 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
  49. 49. 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
  50. 50. Minimally Marketable Features Wednesday, May 8, 13
  51. 51. 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
  52. 52. 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
  53. 53. 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
  54. 54. 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
  55. 55. 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
  56. 56. 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
  57. 57. 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
  58. 58. EssentialView #1 Velocity & Burndown Wednesday, May 8, 13
  59. 59. Sprinting Wednesday, May 8, 13
  60. 60. 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
  61. 61. 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
  62. 62. Story  Backlog Task  Backlog In  Process Task  Done Story  Done User  Story 3 Iden*fy  the  User  Story  most  likely   to  contribute  to  the  MMF  and   build  that  one  first Wednesday, May 8, 13
  63. 63. Story  Backlog Task  Backlog In  Process Task  Done Story  Done User  Story 3 Pull  User  Stories  in  priority  order   focusing  on  delivering  complete   MMFs Wednesday, May 8, 13
  64. 64. 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
  65. 65. 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
  66. 66. 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
  67. 67. 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
  68. 68. 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
  69. 69. Story  Backlog Task  Backlog In  Process Task  Done Story  Done User  Story User  Story User  Story TaskTask Task 3 2 1 Task Task Task Task Planned  Team  Velocity  =  6  points The  Team  breaks  each  User  Story   down  into  Tasks Wednesday, May 8, 13
  70. 70. 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
  71. 71. 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
  72. 72. 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 4 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
  73. 73. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  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
  74. 74. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  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
  75. 75. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  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
  76. 76. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  Es*mated  Hours  =  98  hours Task 8 Task 16 User  Story 3 Tasks  move  across  the  Story  Board   un*l  there  is  a  completed  User   Story.     Wednesday, May 8, 13
  77. 77. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  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
  78. 78. Story  Backlog Task  Backlog In  Process Task  Done Story  Done User  Story User  Story Task Task Task Task Task Task Task Task 3 1 Task 8 16 2 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  Es*mated  Hours  =  98  hours Task 8 Task 16 User  Story 2 The  Team  works  from  the  top  of   the  Story  Board,  Swarming  to  get     User  Stories  across  the  board  as   fast  as  possible  .     Wednesday, May 8, 13
  79. 79. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  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
  80. 80. Story  Backlog Task  Backlog In  Process Task  Done Story  Done User  Story User  Story Task Task Task Task Task Task Task Task 3 2 Task 8 16 2 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  Es*mated  Hours  =  98  hours Task 8 Task 16 User  Story 1 The  Team  works  from  the  top  of   the  Story  Board,  Swarming  to  get     User  Stories  across  the  board  as   fast  as  possible  .     Wednesday, May 8, 13
  81. 81. 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 4 8 8 4 16 8 Planned  Team  Velocity  =  6  points Planned  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
  82. 82. Measuring Progress Wednesday, May 8, 13
  83. 83. 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
  84. 84. 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
  85. 85. 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
  86. 86. 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
  87. 87. 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
  88. 88. 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
  89. 89. 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
  90. 90. 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
  91. 91. 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
  92. 92. Release  Burndown 38 Sprint  Burndown 96 Velocity  Trend 6 6 From  a  Metrics  perspec*ve,  we   Burn  Down  points  to  make  sure   the  Release  is  on  track Wednesday, May 8, 13
  93. 93. Release  Burndown 38 Sprint  Burndown 96 Velocity  Trend 6 6 8 From  a  Metrics  perspec*ve,  we   Burn  Down  points  to  make  sure   the  Release  is  on  track Wednesday, May 8, 13
  94. 94. Release  Burndown 38 Sprint  Burndown 96 Velocity  Trend 6 6 8 5 We  track  Velocity  Trend  to  make   sure  the  team  is  delivering  in  a   Predictable  manner Wednesday, May 8, 13
  95. 95. Release  Burndown 38 Sprint  Burndown 96 Velocity  Trend 6 6 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
  96. 96. Release  Burndown 38 Sprint  Burndown 96 Velocity  Trend 6 6 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  oen! Wednesday, May 8, 13
  97. 97. EssentialView #2 Roadmap Over Time Wednesday, May 8, 13
  98. 98. Road-mapping Wednesday, May 8, 13
  99. 99. Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  100. 100. Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  101. 101. Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  102. 102. Epic Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  103. 103. Epic Epic Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  104. 104. Epic Epic Epic Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  105. 105. Epic Epic Epic Epic Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  106. 106. Epic Epic Epic Epic Epic Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  107. 107. Epic Epic Epic Epic Epic Epic Epic Epic Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Wednesday, May 8, 13
  108. 108. Arch Arch Arch Arch Arch Arch Arch ArchEpic Epic Epic Epic Epic Epic Epic Epic Q1 Q2 Q3 Q4 Wednesday, May 8, 13
  109. 109. Progressive Elaboration Wednesday, May 8, 13
  110. 110. 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
  111. 111. 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
  112. 112. 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
  113. 113. 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
  114. 114. 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
  115. 115. 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
  116. 116. Managing Risk Wednesday, May 8, 13
  117. 117. 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
  118. 118. 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
  119. 119. 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
  120. 120. 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
  121. 121. 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
  122. 122. Release Spikes Wednesday, May 8, 13
  123. 123. 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
  124. 124. 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 Spike User  Story Wednesday, May 8, 13
  125. 125. Budgeting vs. Estimating Wednesday, May 8, 13
  126. 126. 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 Spike User  Story Wednesday, May 8, 13
  127. 127. EssentialView #3 Flow Wednesday, May 8, 13
  128. 128. Key Concepts • Flow • Value Streams • Small Batches • WIP Limits Wednesday, May 8, 13
  129. 129. Key Concepts • Flow • Value Streams • Small Batches • WIP Limits Wednesday, May 8, 13
  130. 130. Key Concepts • Flow • Value Streams • Small Batches • WIP Limits Wednesday, May 8, 13
  131. 131. Key Concepts • Flow • Value Streams • Small Batches • WIP Limits Wednesday, May 8, 13
  132. 132. Key Concepts • Flow • Value Streams • Small Batches • WIP Limits Wednesday, May 8, 13
  133. 133. n-Tier Model Wednesday, May 8, 13
  134. 134. Scrum Team Product Team Scrum Team Scrum Team Scrum Team Product Team Strategy Team Support Team Portfolio Team n-Tier Model Wednesday, May 8, 13
  135. 135. Story Backlog Task Backlog In Process Task Done Story Done Tier 1 - Scrum Wednesday, May 8, 13
  136. 136. 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
  137. 137. 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
  138. 138. 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
  139. 139. 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
  140. 140. 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
  141. 141. 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
  142. 142. Kanban creates a Pull System across the entire portfolio that is limited by your Actual Capacity Wednesday, May 8, 13
  143. 143. 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
  144. 144. 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
  145. 145. 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
  146. 146. 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
  147. 147. 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
  148. 148. 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
  149. 149. 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
  150. 150. 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
  151. 151. 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
  152. 152. 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 TaskTask Task 8 16 8 Feature Wednesday, May 8, 13
  153. 153. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Feature User Story User Story Spike TaskTask Task 8 16 8 Feature Epic Epic Wednesday, May 8, 13
  154. 154. 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 Spike TaskTask Task 8 16 8 Feature Epic Wednesday, May 8, 13
  155. 155. 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 Spike TaskTask Task 8 16 8 Feature Epic Epic Wednesday, May 8, 13
  156. 156. 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 Spike TaskTask Task 8 16 8 Feature Epic Epic Feature Wednesday, May 8, 13
  157. 157. 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 Spike TaskTask Task 8 16 8 Feature EpicEpic Feature Wednesday, May 8, 13
  158. 158. 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 Spike TaskTask Task 8 16 8 Feature EpicEpic Feature Wednesday, May 8, 13
  159. 159. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Epic Feature User Story User Story TaskTask Task 8 16 8 Epic Spike Feature Feature Wednesday, May 8, 13
  160. 160. 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 Spike TaskTask Task 8 16 8 Epic Feature Feature Wednesday, May 8, 13
  161. 161. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Epic Feature User StoryUser Story TaskTask Task 8 16 8 Spike Epic Feature Feature Wednesday, May 8, 13
  162. 162. 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
  163. 163. 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
  164. 164. 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 Spike User Story Epic Feature Wednesday, May 8, 13
  165. 165. 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 Spike User Story Epic Feature Wednesday, May 8, 13
  166. 166. 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 Spike User Story Epic FeatureFeature Wednesday, May 8, 13
  167. 167. 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 Epic Epic Feature Feature Wednesday, May 8, 13
  168. 168. 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 Epic Epic FeatureFeature Wednesday, May 8, 13
  169. 169. 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 Epic Epic FeatureFeature Wednesday, May 8, 13
  170. 170. 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 Epic Epic FeatureFeature Wednesday, May 8, 13
  171. 171. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Epic Feature Feature Task Task Task 8 16 8 User StoryUser Story Spike Epic Epic FeatureFeature Wednesday, May 8, 13
  172. 172. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Epic Feature Feature Task Task Task 8 16 8 User StoryUser Story Spike Epic Epic FeatureFeature Wednesday, May 8, 13
  173. 173. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Epic Epic Feature Feature Task Task Task 8 16 8 User Story Spike User Story Epic Feature FeatureFeature User Story User Story Spike Task Task Task 8 8 Wednesday, May 8, 13
  174. 174. Story Backlog Task Backlog In Process Task Done Story Backlog Analysis Design Build Test Deploy Inception Elaboration Construction Transition Epic Epic Feature Feature Task Task Task 8 16 8 User Story Spike User Story Epic Feature User Story User Story Spike Feature Feature Wednesday, May 8, 13
  175. 175. 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 Spike Task Task Task 8 8 Feature FeatureFeature 8 Wednesday, May 8, 13
  176. 176. 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 Spike Task Task 8 8 Feature FeatureFeature Task 8 Wednesday, May 8, 13
  177. 177. 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 Spike Task Task 8 8 Feature FeatureFeature Task 8 Wednesday, May 8, 13
  178. 178. 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 Feature FeatureFeature Task 8 User Story Spike Wednesday, May 8, 13
  179. 179. 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 Feature FeatureFeature Task 8 User Story Spike Wednesday, May 8, 13
  180. 180. 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 Feature FeatureFeature Task 8 User Story Spike Wednesday, May 8, 13
  181. 181. 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
  182. 182. 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
  183. 183. 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 FeatureFeature Feature Task 8 User Story Spike Epic Feature User Story User Story Spike Task Task Task 8 8 Task 8 Task 8 Wednesday, May 8, 13
  184. 184. Bottlenecks & Dependencies Wednesday, May 8, 13
  185. 185. 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 FeatureFeature Feature Task 8 User Story Spike Epic Feature User Story User Story Spike Task Task Task 8 8 Task 8 Task 8 Wednesday, May 8, 13
  186. 186. EssentialView #4 Progress Wednesday, May 8, 13
  187. 187. Assessing Progress How do we visualize progress to the rest of the organization • Start • End • Budget • SWAG • Estimate • Actual • % Complete Wednesday, May 8, 13
  188. 188. Planned Planned Progress Budget Estimate Detail Start End Wednesday, May 8, 13
  189. 189. Epic Planned Planned Progress Budget Estimate Detail Start End 300 280 325 Sprint 1 Sprint 5 Wednesday, May 8, 13
  190. 190. Epic Feature Planned Planned Progress Budget Estimate Detail Start End 300 16 280 19 325 21 Sprint 1 Sprint 2 Sprint 5 Sprint 4 Wednesday, May 8, 13
  191. 191. Epic Feature Planned Planned Progress Budget Estimate Detail Start End User  Story 300 16 5 280 19 8 325 21 8 Sprint 1 Sprint 2 Sprint 2 Sprint 5 Sprint 4 Sprint 2 Wednesday, May 8, 13
  192. 192. Epic Feature Planned Planned Progress Budget Estimate Detail Start End User  Story User  Story 300 16 5 3 280 19 8 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
  193. 193. 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 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
  194. 194. 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 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
  195. 195. 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 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
  196. 196. 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 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
  197. 197. 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 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
  198. 198. 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 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
  199. 199. Pulling it all together Wednesday, May 8, 13
  200. 200. Release  Burndown 38 Sprint  Burndown 96 Velocity  Trend 6 6 8 5 Wednesday, May 8, 13
  201. 201. 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 Spike User  Story Wednesday, May 8, 13
  202. 202. 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
  203. 203. 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 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
  204. 204. 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   FEATURE   STORY   EPICS   KANBAN   SCRUM  
  205. 205. 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  
  206. 206. 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  
  207. 207. 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)
  208. 208. 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  
  209. 209. 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)
  210. 210. 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  

×