Agile Program and Portfolio Management

12,034 views

Published on

Agile2012 Edition

Published in: Technology, Business
0 Comments
24 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
12,034
On SlideShare
0
From Embeds
0
Number of Embeds
5,644
Actions
Shares
0
Downloads
731
Comments
0
Likes
24
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Explaining the hierarchy of value\n
  • Explaining the hierarchy of value\n
  • Explaining the hierarchy of value\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • \n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • Story Mapping\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Story Mapping\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Agile Program and Portfolio Management

    1. 1. Agile Program and PortfolioManagementMike Cottmeyer, Enterprise Agile CoachLeadingAgile, LLC
    2. 2. Mike Cottmeyermike@leadingagile.com404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer
    3. 3. Before We Start...
    4. 4. Before We Start...This is not a process overlay foryour existing organization...
    5. 5. Before We Start... Organiza(onal+ Transforma(on+ Personal+ Adopt++Transforma(on+ Prac(ces+
    6. 6. Before We Start... Organiza(onal+ Transforma(on+ Personal+ Adopt++Transforma(on+ Prac(ces+
    7. 7. Before We Start... Organiza(onal+ Transforma(on+ Strategic Personal+ Adopt++Transforma(on+ Prac(ces+ Release Iteration Daily Continuous
    8. 8. Before We Start... Organiza(onal+ Transforma(on+ Strategic Personal+ Adopt++Transforma(on+ Prac(ces+ Release Iteration Daily Continuous
    9. 9. Agile Competencies• Product Definition• Planning & Coordination• Delivery Practices• Continuous Improvement• Organizational Enablement
    10. 10. Agile Competencies• Product Definition• Planning & Coordination• Delivery Practices• Continuous Improvement• Organizational Enablement
    11. 11. Agile Competencies• Product Definition• Planning & Coordination• Delivery Practices• Continuous Improvement• Organizational Enablement
    12. 12. Agile Competencies• Product Definition• Planning & Coordination• Delivery Practices• Continuous Improvement• Organizational Enablement
    13. 13. Agile Competencies• Product Definition• Planning & Coordination• Delivery Practices• Continuous Improvement• Organizational Enablement
    14. 14. Agile Competencies• Product Definition• Planning & Coordination• Delivery Practices• Continuous Improvement• Organizational Enablement
    15. 15. Competencies at Scale• Team• Multi-Team• Program• Portfolio• Enterprise
    16. 16. Team Agility Scrum Team
    17. 17. Multi-Team Agility Scrum Scrum Team Team
    18. 18. Multi-Team Agility Scrum Scrum Scrum Team Team Team
    19. 19. Multi-Team Agility Scrum Scrum Scrum Scrum Team Team Team Team
    20. 20. Program Agility Product Team Scrum Scrum Scrum Scrum Team Team Team Team
    21. 21. Program Agility Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    22. 22. Portfolio Agility Portfolio Team Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    23. 23. Enterprise Agility Strategy Portfolio Support Team Team Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    24. 24. Competencies in Time• Continuous• Daily• Strategic Iteration• Release Release• Strategic Iteration Daily Continuous
    25. 25. Competencies in Time• Continuous• Daily• Iteration Strategic• Release Release• Strategic Iteration Daily Continuous
    26. 26. Competencies in Time• Continuous• Daily• Iteration Strategic• Release Release• Strategic Iteration Daily Continuous
    27. 27. Competencies in Time• Continuous• Daily• Iteration Strategic• Release Release• Strategic Iteration Daily Continuous
    28. 28. Competencies in Time• Continuous• Daily• Iteration Strategic• Release Release• Strategic Iteration Daily Continuous
    29. 29. Competencies in Time• Continuous• Daily• Iteration Strategic• Release Release• Strategic Iteration Daily Continuous
    30. 30. Incremental vs. Iterative Courtesy of Jeff Patton
    31. 31. Incremental vs. Iterative Incremental Courtesy of Jeff Patton
    32. 32. Incremental vs. Iterative Incremental Iterative Courtesy of Jeff Patton
    33. 33. Transformation Life-Cycle Incrementing and Iterating the Agile Enterprise • Organiza(onal+ Change physical Transforma(on+ structures and introduce teams • Teach people new Personal+ Adopt++ practices and ways Transforma(on+ Prac(ces+ of working • Help people internalize the value system
    34. 34. Adoption/Transformation Cycle Organizational Transformation • Establish top to Organiza(onal+ bottom structure Transforma(on+ and roadmap • Incrementally make changes and Personal+ Adopt++ establish teams Transforma(on+ Prac(ces+ • Define policies and working agreements between teams
    35. 35. Adoption/Transformation Cycle Adopting Practices •Sprint planning, daily stand-ups, Organiza(onal+ product reviews, Transforma(on+ and retrospectives •Identify and train a Product Owner Personal+ Adopt++ and ScrumMaster Transforma(on+ Prac(ces+ •Teach TDD, CI, Story Maps, and MMF
    36. 36. Adoption/Transformation Cycle Personal Transformation • Develop an ability Organiza(onal+ to deal with Transforma(on+ uncertainty and adaptation • Help people work Personal+ Adopt++ toward common Transforma(on+ Prac(ces+ organizational goals • Help foster empathy, trust, and teamwork
    37. 37. Projects, Programs, Portfolios
    38. 38. Agile Project Management Scrum Scrum Scrum Scrum Team Team Team Team
    39. 39. Agile Program Management Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    40. 40. Agile Portfolio Management Portfolio Team Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    41. 41. Enterprise Portfolio Management Strategy Portfolio Support Team Team Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    42. 42. How is Agile Different? Business Agility at the Portfolio Level • Want our investment portfolio to respond to the needs of changing market conditions • We need the ability as an organization to respond to changing market conditions
    43. 43. Foundational Stuff...The Anatomy of Agile Teams
    44. 44. Agile Teams• Who’s involved?• Dependencies• Backlog• Velocity• Accountability
    45. 45. ScrumTeam
    46. 46. ScrumTeam Developers
    47. 47. ScrumTeam Developers Testers
    48. 48. AnalystsScrumTeam Developers Testers
    49. 49. AnalystsUX Scrum Team Developers Testers
    50. 50. AnalystsLead Scrum Team Developers Testers
    51. 51. Analysts Lead Scrum Team DevelopersScrumMaster Testers
    52. 52. Product Owner Analysts Lead Scrum Team DevelopersScrumMaster Testers
    53. 53. Foundational Stuff...Time, Cost, and Scope
    54. 54. ScopeTime Cost
    55. 55. Time Cost Scope
    56. 56. Time Cost Risk Scope
    57. 57. Time Cost Value Scope
    58. 58. Managing Variable ScopeHow to deal with making commitments when scope is constantly changing
    59. 59. Story Maps
    60. 60. Epics collections of features, typically 1-3 months inEpic duration. Epics span releases. Epics can span more than one team. These are the things senior leadership cares about.
    61. 61. Epics collections of features, typically 1-3 months in Epic duration. 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 inFeature duration. Features are contained within releases. Features are contained within a team. These are what the Product Owner Cares about.
    62. 62. Epics collections of features, typically 1-3 months in Epic duration. 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 inFeature duration. 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, typicallyUser less than a week. User Stories are contained within sprint.Story These are the things Engineering Management Cares about.
    63. 63. Story Maps visually show the Epic relationship between User Stories and Business ValueFeature Feature Feature FeatureUser User User UserStory Story Story StoryUser User User UserStory Story Story StoryUser User User UserStory Story Story StoryUser User User UserStory Story Story Story
    64. 64. Story Maps start with theEpic identification of larger, more strategic organizational goals
    65. 65. Epics are decomposed into Epic Features that describe the value added into the productFeature
    66. 66. Epics are decomposed into Epic Features that describe the value added into the productFeature Feature
    67. 67. Epics are decomposed into Epic Features that describe the value added into the productFeature Feature Feature
    68. 68. Epics are decomposed into Epic Features that describe the value added into the productFeature Feature Feature Feature
    69. 69. Features are decomposed Epic into User Stories that are thin slices of value added into the systemFeature Feature Feature FeatureUserStoryUserStoryUserStoryUserStory
    70. 70. Features are decomposed Epic into User Stories that are thin slices of value added into the systemFeature Feature Feature FeatureUser UserStory StoryUser UserStory StoryUser UserStory StoryUser UserStory Story
    71. 71. Features are decomposed Epic into User Stories that are thin slices of value added into the systemFeature Feature Feature FeatureUser User UserStory Story StoryUser User UserStory Story StoryUser User UserStory Story StoryUser User UserStory Story Story
    72. 72. Features are decomposed Epic into User Stories that are thin slices of value added into the systemFeature Feature Feature FeatureUser User User UserStory Story Story StoryUser User User UserStory Story Story StoryUser User User UserStory Story Story StoryUser User User UserStory Story Story Story
    73. 73. Minimally Marketable Features
    74. 74. User Stories are estimated in Epic relative units of measure called Story PointsFeature Feature Feature FeatureUser 3 User 1 User 2 User 1Story Story Story StoryUser 2 User 3 User 5 User 3Story Story Story StoryUser 5 User 2 User 3 User 2Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    75. 75. Story Points can be added Epic up to size Features 11 7 12 8Feature Feature Feature FeatureUser 3 User 1 User 2 User 1Story Story Story StoryUser 2 User 3 User 5 User 3Story Story Story StoryUser 5 User 2 User 3 User 2Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    76. 76. 38 Feature Points can be added Epic up to size Epics 11 7 12 8Feature Feature Feature FeatureUser 3 User 1 User 2 User 1Story Story Story StoryUser 2 User 3 User 5 User 3Story Story Story StoryUser 5 User 2 User 3 User 2Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    77. 77. 38 Our Goal is to build the Epic smallest system possible to deliver the value in the Epic 11 7 12 8Feature Feature Feature FeatureUser 3 User 1 User 2 User 1Story Story Story StoryUser 2 User 3 User 5 User 3Story Story Story StoryUser 5 User 2 User 3 User 2Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    78. 78. 38 We continuously evaluate Epic the Story Map to determine the Minimally Marketable Feature 11 7 12 8Feature Feature Feature FeatureUser 3 User 1 User 2 User 1Story Story Story StoryUser 2 User 3 User 5 User 3Story Story Story StoryUser 5 User 2 User 3 User 2Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    79. 79. 38 We continuously evaluate Epic the Story Map to determine the Minimally Marketable Feature 11 7 12 8Feature Feature Feature Feature User 3 User 1 User 2 User 1 Story Story Story Story User 2 User 3 User 5 User 3 Story Story Story Story User 5 User 2 User 3 User 2 Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    80. 80. 26 When we focus on Minimally Epic Marketable Features, we deliver Business Value early 10 4 5 7Feature Feature Feature Feature User 3 User 1 User 2 User 1 Story Story Story Story User 2 User 3 User 5 User 3 Story Story Story Story User 5 User 2 User 3 User 2 Story Story Story StoryUser 1 User 1 User 2 User 2Story Story Story Story
    81. 81. Essential View #1 Velocity & Burndown
    82. 82. Sprinting
    83. 83. Minimally Marketable Features feed the prioritization of our Sprint PlanningStory Backlog Task Backlog In Process Task Done Story Done
    84. 84. Identify the User Story most likely to contribute to the MMF and build that one firstStory Backlog Task Backlog In Process Task Done Story Done
    85. 85. Identify the User Story most likely to contribute to the MMF and build that one firstStory Backlog Task Backlog In Process Task Done Story Done 3UserStory
    86. 86. Pull User Stories in priority order focusing on delivering complete MMFsStory Backlog Task Backlog In Process Task Done Story Done 3UserStory
    87. 87. Pull User Stories in priority order focusing on delivering complete MMFsStory Backlog Task Backlog In Process Task Done Story Done 3UserStory 2 User Story
    88. 88. It’s okay to work User Stories across MMFs if that is what the Product Owner needsStory Backlog Task Backlog In Process Task Done Story Done 3UserStory 2 User Story
    89. 89. It’s okay to work User Stories across MMFs if that is what the Product Owner needsStory Backlog Task Backlog In Process Task Done Story Done 3UserStory 2 User Story 1UserStory
    90. 90. The team uses its past velocity to determine how many stories go in the Sprint Planned Team Velocity = 6 pointsStory Backlog Task Backlog In Process Task Done Story Done 3UserStory 2 User Story 1UserStory
    91. 91. The Team breaks each User Story down into Tasks Planned Team Velocity = 6 pointsStory Backlog Task Backlog In Process Task Done Story Done 3 Task TaskUserStory Task 2 User Story 1UserStory
    92. 92. The Team breaks each User Story down into Tasks Planned Team Velocity = 6 pointsStory Backlog Task Backlog In Process Task Done Story Done 3 Task TaskUserStory Task 2 Task Task User Story Task Task 1UserStory
    93. 93. The Team breaks each User Story down into Tasks Planned Team Velocity = 6 pointsStory Backlog Task Backlog In Process Task Done Story Done 3 Task TaskUserStory Task 2 Task Task User Story Task Task Task Task 1UserStory Task Task
    94. 94. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver Planned Team Velocity = 6 pointsStory Backlog Task Backlog In Process Task Done Story Done 3 Task 8 16 TaskUserStory Task 8 2 Task Task User Story Task Task Task Task 1UserStory Task Task
    95. 95. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver Planned Team Velocity = 6 pointsStory Backlog Task Backlog In Process Task Done Story Done 3 Task 8 16 TaskUserStory Task 8 2 Task16 Task 2 User 8 Story 4 Task Task Task Task 1UserStory Task Task
    96. 96. And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done 3 Task 8 Task 16UserStory Task 8 2 Task16 Task 2 User 8 Story 4 Task Task 8 Task Task 4 1User 16 8Story Task Task
    97. 97. At the beginning of the Sprint, The Team pulls Tasks from the top of the Task Backlog Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done 3 Task 8UserStory 8 Task16 Task 2 Task16 Task 2 User 8 Story 4 Task Task 8 Task Task 4 1User 16 8Story Task Task
    98. 98. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done 3 Task 8UserStory 8 Task16 Task 2 Task16 Task 2 User 8 Story 4 Task Task 8 Task Task 4 1User 16 8Story Task Task
    99. 99. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done 3 Task 8UserStory Task16 Task 8 2 Task16 Task 2 User 8 Story 4 Task Task 8 Task Task 4 1User 8 16 TaskStory Task
    100. 100. Tasks move across the Story Board until there is a completed User Story. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done Task 8 3 User Task16 Story Task 8 2 Task16 Task 2 User 8 Story 4 Task Task 8 Task Task 4 1User 8 16 TaskStory Task
    101. 101. The Team works from the top of the Story Board, Swarming to get User Stories across the board as fast as possible . Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done Task 8 3 User Task16 Story Task 8 2 Task16 Task 2 User 8 Story 4 Task Task 8 Task Task 4 1User 8 16 TaskStory Task
    102. 102. The Team works from the top of the Story Board, Swarming to get User Stories across the board as fast as possible . Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done Task 8 3 User Task16 Story Task 8 2 Task16 Task 2 8 User 4 Task Story Task 8 Task Task 4 1User 8 16 TaskStory Task
    103. 103. The Team works from the top of the Story Board, Swarming to get User Stories across the board as fast as possible . Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done Task 8 3 User Task16 Story Task 8 2 Task16 Task 2 8 User 4 Task Story Task 8 Task Task 4 1User 16 Task 8Story Task
    104. 104. Until the entire Sprint has been delivered to the Product Owner. Planned Team Velocity = 6 points Planned Estimated Hours = 98 hoursStory Backlog Task Backlog In Process Task Done Story Done Task 8 3 User Task16 Story Task 8 2 Task16 Task 2 8 User 4 Task Story Task Task 8 Task 4 1 User 8 Story 16 Task Task
    105. 105. Measuring Progress
    106. 106. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    107. 107. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    108. 108. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    109. 109. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    110. 110. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    111. 111. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    112. 112. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    113. 113. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    114. 114. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track38 96 6 Release Burndown Sprint Burndown Velocity Trend
    115. 115. From a Metrics perspective, we Burn Down points to make sure the Release is on track38 96 6 6 Release Burndown Sprint Burndown Velocity Trend
    116. 116. From a Metrics perspective, we Burn Down points to make sure the Release is on track38 96 8 6 6 Release Burndown Sprint Burndown Velocity Trend
    117. 117. We track Velocity Trend to make sure the team is delivering in a Predictable manner38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend
    118. 118. 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.38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend
    119. 119. 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 often!38 96 8 6 6 5 Release Burndown Sprint Burndown Velocity Trend
    120. 120. Essential View #2 Roadmap Over Time
    121. 121. Planning Horizons
    122. 122. Q1 Q2 Q3 Q4
    123. 123. Road-mapping
    124. 124. Q1 Q2 Q3 Q4Epic
    125. 125. Q1 Q2 Q3 Q4Epic Epic
    126. 126. Q1 Q2 Q3 Q4Epic Epic Epic
    127. 127. Q1 Q2 Q3 Q4Epic Epic Epic Epic
    128. 128. Q1 Q2 Q3 Q4Epic Epic Epic Epic Epic
    129. 129. Q1 Q2 Q3 Q4Epic Epic Epic Epic Epic Epic
    130. 130. Q1 Q2 Q3 Q4Epic Epic Epic Epic Epic Epic Epic
    131. 131. Q1 Q2 Q3 Q4Epic Epic Epic Epic Epic Epic Epic Epic
    132. 132. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch ArchEpic Epic Epic Epic Epic Epic Epic Epic
    133. 133. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch ArchEpic Epic Epic Epic Epic Epic Epic Epic
    134. 134. Progressive Elaboration
    135. 135. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature
    136. 136. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature
    137. 137. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature
    138. 138. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature
    139. 139. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User Story Story User User Story Story
    140. 140. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User Story Story Story Story User User User Story Story Story
    141. 141. Dealing with Risk
    142. 142. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User Story Story Story Story User User User Story Story Story Risk Risk
    143. 143. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User Story Story Story Story Story Story User User User Story Story Story Risk Risk
    144. 144. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User Story Story Story Story Story Story User User User Story Story Story Risk Risk Risk Risk
    145. 145. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User User Story Story Story Story Story Story Story User User User Story Story Story Risk Risk Risk Risk
    146. 146. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User User Story Story Story Story Story Story Story User User User Story Story Story Risk Risk Risk Risk Risk
    147. 147. Release Spikes
    148. 148. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User User Story Story Story Story Story Story Story User User User Story Story StorySpike Spike Risk Risk Risk Risk Risk
    149. 149. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User User Story Story Story Story Story Story Story User User User Story Story Story SpikeSpike Spike Risk Risk Risk Risk Risk
    150. 150. Budgeting vs. Estimating
    151. 151. Q1 Q2 Q3 Q4 Arch Arch Arch Arch Arch Arch Arch Arch Epic Epic Epic Epic Epic Epic Epic EpicFeature Feature Feature Feature Feature Feature Feature User User User User User User User Story Story Story Story Story Story Story User User User Story Story Story SpikeSpike Spike Risk Risk Risk Risk Risk
    152. 152. Essential View #3 Flow
    153. 153. Key Concepts• Flow• Kanban• Value Streams• Small Batches• WIP Limits
    154. 154. Key Concepts• Flow• Kanban• Value Streams• Small Batches• WIP Limits
    155. 155. Key Concepts• Flow• Kanban• Value Streams• Small Batches• WIP Limits
    156. 156. Key Concepts• Flow• Kanban• Value Streams• Small Batches• WIP Limits
    157. 157. Key Concepts• Flow• Kanban• Value Streams• Small Batches• WIP Limits
    158. 158. Key Concepts• Flow• Kanban• Value Streams• Small Batches• WIP Limits
    159. 159. n-Tier Model
    160. 160. Enterprise Portfolio Model Strategy Portfolio Support Team Team Product Product Team Team Scrum Scrum Scrum Scrum Team Team Team Team
    161. 161. Story Backlog Task Backlog In Process Task Done Story Done Tier 1 - Scrum
    162. 162. Analysis Design Build Test Deploy Tier 2 - KanbanStory Backlog Task Backlog In Process Task Done Story Done Tier 1 - Scrum
    163. 163. Inception Elaboration Construction Transition Tier 3 - Kanban Analysis Design Build Test Deploy Tier 2 - KanbanStory Backlog Task Backlog In Process Task Done Story Done Tier 1 - Scrum
    164. 164. Features are decomposed Epic into User Stories that are thin slices of value added into the systemFeature Feature Feature FeatureUser User User UserStory Story Story StoryUser User User UserStory Story Story StoryUser User User UserStory Story Story StoryUser User User UserStory Story Story Story
    165. 165. Inception Elaboration Construction Transition Tier 3 - Kanban Analysis Design Build Test Deploy Tier 2 - KanbanStory Backlog Task Backlog In Process Task Done Story DoneUser Story Tier 1 - Scrum
    166. 166. Inception Elaboration Construction Transition Tier 3 - Kanban Analysis Design Build Test Deploy Feature Tier 2 - KanbanStory Backlog Task Backlog In Process Task Done Story DoneUser Story Tier 1 - Scrum
    167. 167. Inception Elaboration Construction Transition Epic Tier 3 - Kanban Analysis Design Build Test Deploy Feature Tier 2 - KanbanStory Backlog Task Backlog In Process Task Done Story DoneUser Story Tier 1 - Scrum
    168. 168. Kanban creates a Pull System across the entire portfolio that islimited by your Actual Capacity
    169. 169. Inception Elaboration Construction TransitionEpic Epic Analysis Design Build Test DeployStory Backlog Task Backlog In Process Task Done Story Backlog
    170. 170. Inception Elaboration Construction TransitionEpic Epic Analysis Design Build Test DeployStory Backlog Task Backlog In Process Task Done Story Backlog
    171. 171. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test DeployStory Backlog Task Backlog In Process Task Done Story Backlog
    172. 172. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test DeployFeature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog
    173. 173. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test DeployFeature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog
    174. 174. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog
    175. 175. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog Spike
    176. 176. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog Spike User StoryUser Story
    177. 177. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog Spike User StoryUser Story
    178. 178. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 16 Task Task Spike User Story 8User Story Task
    179. 179. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 16 Task Task Spike User Story 8User Story Task
    180. 180. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 16 Task Task Spike User Story 8User Story Task
    181. 181. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 16 Task Task Spike User Story 8User Story Task
    182. 182. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 16 Task Task Spike User Story 8User Story Task
    183. 183. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 8 Task Task Spike User Story 8User Story Task
    184. 184. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 8 Task Task Spike User Story 8User Story Task
    185. 185. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 8 Task Task Spike User Story 8User Story Task
    186. 186. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 8 Task Task User Story Spike 8User Story Task
    187. 187. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 8 Task Task SpikeUser Story 8 User Story Task
    188. 188. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog 16 Task Task 8 Spike User Story 8 User Story Task
    189. 189. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog 16 Task Task 8 Spike User Story 8 User Story Task
    190. 190. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog 16 Task Task 8 Spike User Story 8 User Story Task
    191. 191. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature Feature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog 16 Task Task 8 Spike User Story 8 User Story Task
    192. 192. Inception Elaboration Construction Transition Epic Epic Analysis Design Build Test Deploy Feature FeatureFeature FeatureStory Backlog Task Backlog In Process Task Done Story Backlog 16 Task Task 8 Spike User Story 8 User Story Task
    193. 193. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task Spike User Story Task 8User Story 8 Task
    194. 194. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task Spike User Story Task 8User Story 8 Task
    195. 195. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task Spike User Story Task 8User Story 8 Task
    196. 196. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 8 Task Task Spike User StoryUser Story 8 Task
    197. 197. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task SpikeUser Story Task 8 User Story 8 Task
    198. 198. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task SpikeUser Story Task 8 User Story 8 Task
    199. 199. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task Task Spike Spike User Story Task 8User Story Task 8 User Story User Story 8 8 Task Task
    200. 200. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 16 Task Spike Spike User StoryUser Story Task 8 User Story User Story 8 Task
    201. 201. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 Task Spike User Story Task 8User Story 8 Task
    202. 202. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 Task Spike User Story Task 8User Story 8 Task
    203. 203. Inception Elaboration Construction Transition Epic Epic Epic Analysis Design Build Test Deploy Feature Feature Feature Feature Feature Story Backlog Task Backlog In Process Task Done Story Backlog 8 Task 8 Spike TaskUser Story 8 User Story Task

    ×