Your SlideShare is downloading. ×
Scrum and kanban in the enterprise   webinar
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum and kanban in the enterprise webinar

4,168
views

Published on

This was the one delivered at the VersionOne AgileLIVE webinar on 6/29/2011. Talk will be reprised at the 2011 PMI North American Global Congress.

This was the one delivered at the VersionOne AgileLIVE webinar on 6/29/2011. Talk will be reprised at the 2011 PMI North American Global Congress.

Published in: Lifestyle, Technology

2 Comments
20 Likes
Statistics
Notes
No Downloads
Views
Total Views
4,168
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
370
Comments
2
Likes
20
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
  • So here is our small agile team.
  • I
  • Scrum is a team based methodology…Ideal team size is 5 to 9 peopleTeam has everything it needs to deliver an increment of working productVery clear role and responsibility delineation: ScrumMaster, Product Owner, TeamProduct Owner brings the whatTeam decides the howWIP is limited by the velocity of the teamScrumMaster’s job is to get rid of the stuff slowing the team down The idea is to deliver in short sprints…… use empirical process control, inspect and adaptTotally designed to be a lightweight framework for delivering products in the face of uncertaintyI
  • Explaining the hierarchy of value
  • Explaining the hierarchy of value
  • Explaining the hierarchy of value
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Story Mapping
  • Explaining the hierarchy of value
  • Explaining the hierarchy of value
  • Explaining the hierarchy of value
  • So, before we get started, a little about me. My name is Mike Cottmeyer, I am an agile transformation coach with Pillar technology. Before I joined Pillar I was a trainer and consultant with VersionOne. Before that I ran a pretty large agile portfolio of projects for CheckFree (now Fiserv). Pillar Technology has been around for about 13 years and is just about 100 people strong. Pillar specializes in agile transformation and project delivery. We can bring in agile coaches on the leadership and project management side. We can bring in coaches to help you with TDD. We can spin up teams and help you deliver projects.
  • Transcript

    • 1. Blending Scrum and Kanban to Create an End-to-End Agile Enterprise
    • 2. Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLCmike@leadingagile.com 1.404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer
    • 3. Agenda
      Why this talk? Isn’t Scrum enough?
    • 4. Agenda
      Why this talk? Isn’t Scrum enough?
      Discuss what end-to-end business agility looks like and how it is different from team agility
    • 5. Agenda
      Why this talk? Isn’t Scrum enough?
      Discuss what end-to-end business agility looks like and how it is different from team agility, and why team agility is not enough
    • 6. Agenda
      Why this talk? Isn’t Scrum enough?
      Discuss what end-to-end business agility looks like and how it is different from team agility, and why team agility is not enough
      Explore one adoption and transformation strategy… and maybe a few alternatives
    • 7. Agenda
      Why this talk? Isn’t Scrum enough?
      Discuss what end-to-end business agility looks like and how it is different from team agility, and why team agility is not enough
      Explore one adoption and transformation strategy… and maybe a few alternatives
      Show how to manage the flow of value across the enterprise, using Scrum at the team level, and Kanban at the Program and Portfolio level
    • 8. Why Not Just Scrum?
    • 9. Scrum is a team based approach to product delivery.
    • 10. Team
    • 11. Developers
    • 12. Testers
      Developers
    • 13. Analyst
      Testers
      Developers
    • 14. Analyst
      ScrumMaster
      Testers
      Developers
    • 15. Product Owner
      Analyst
      ScrumMaster
      Testers
      Developers
    • 16. What if my team is more than 5-7 people?
    • 17. Scrum in the Enterprise
    • 18. Scrum in the Enterprise
    • 19. Enterprise Scrum
    • 20. Enterprise Scrum... it’s different!
    • 21. Enterprise Scrum
    • 22. Enterprise Scrum
    • 23. Enterprise Scrum
    • 24. Enterprise Scrum
    • 25. Enterprise Scrum
    • 26. Enterprise Scrum
    • 27. Enterprise Scrum
    • 28. What breaks Scrum?
    • 29. External Dependencies
    • 30. External Dependencies
    • 31. External Dependencies
    • 32. Why dependencies matter?
      Velocity dependent on something outside the team
    • 33. Why dependencies matter?
      Velocity dependent on something outside the team
      External dependencies have to be managed and planned for in advance
    • 34. Why dependencies matter?
      Velocity dependent on something outside the team
      External dependencies have to be managed and planned for in advance
      Excessive forward planning can reduce our ability to change as we learn new things
    • 35. Why dependencies matter?
      Velocity dependent on something outside the team
      External dependencies have to be managed and planned for in advance
      Excessive forward planning can reduce our ability to change as we learn new things
      Lack of full ownership can result in lack of commitment and unreliable results
    • 36. Many-to-Many Relationships
    • 37. Many-to-Many Relationships
    • 38. Many-to-Many Relationships
    • 39. Many-to-Many Relationships
    • 40. Many-to-Many Relationships
    • 41. Many-to-Many Relationships
    • 42. Many-to-Many Relationships
    • 43. Many-to-Many Relationships
    • 44. Many-to-Many Relationships
    • 45. Why many-to-many matters?
      Team velocity is not a predictor of higher order deliverables
    • 46. Why many-to-many matters?
      Team velocity is not a predictor of higher order deliverables
      One or more teams can starve the value creation process
    • 47. Why many-to-many matters?
      Team velocity is not a predictor of higher order deliverables
      One or more teams can starve the value creation process
      Backlogs have to be sequenced and dependencies managed
    • 48. Why many-to-many matters?
      Team velocity is not a predictor of higher order deliverables
      One or more teams can starve the value creation process
      Backlogs have to be sequenced and dependencies managed
      Teams focus on their backlog to the exclusion of the rest of the organization
    • 49. What do we mean by end-to-end business agility?
    • 50.
    • 51. We want the benefits of team-level agility….
    • 52. We want the benefits of team-level agility…. but across the entire company
    • 53. We want a pattern that can accommodate Sales and Marketing…
    • 54. …several Scrum teams, service orientation, and shared services…
    • 55. …as well as technical support and ultimately sustaining engineering
    • 56. At some level of scale, Scrum breaks.
    • 57. At some level of scale, Scrum breaks. What are you going to do about it?
    • 58. Tools available to scale Scrum
      Scrum and XP
    • 59. Tools available to scale Scrum
      Scrum and XP
      Kanban
    • 60. Tools available to scale Scrum
      Scrum and XP
      Kanban
      Lean
    • 61. Tools available to scale Scrum
      Scrum and XP
      Kanban
      Lean
      RUP
    • 62. Tools available to scale Scrum
      Scrum and XP
      Kanban
      Lean
      RUP
      Traditional SDLC
    • 63. Interesting idea… how to we get there?
    • 64. It always starts with teams...
    • 65. Ways to organize teams…
      Products
    • 66. Ways to organize teams…
      Products
      Product features
    • 67. Ways to organize teams…
      Products
      Product features
      Components
    • 68. Ways to organize teams…
      Products
      Product features
      Components
      Shared services
    • 69. Ways to organize teams…
      Products
      Product features
      Components
      Shared services
      Business capabilities
    • 70. Get the teams working…
      Define the org structure
    • 71. Get the teams working…
      Define the org structure
      Form the teams
    • 72. Get the teams working…
      Define the org structure
      Form the teams
      Get the teams delivering
    • 73. Get the teams working…
      Define the org structure
      Form the teams
      Get the teams delivering
      Focus on establishing a stable velocity
    • 74. Get the teams working…
      Define the org structure
      Form the teams
      Get the teams delivering
      Focus on establishing a stable velocity
      Learn what works
    • 75. Incrementally roll-out Scrum across the organization…
    • 76. Incrementally roll-out Scrum across the organization……
    • 77. Incrementally roll-out Scrum across the organization………
    • 78. Establish Program Teams and/or Product Integration teams
    • 79. Establish Program Teams and/or Product Integration teams
    • 80. Establish a Portfolio Planning team
    • 81. Manage the flow of value at each level
    • 82. So… what does it look like when I am done?
    • 83. Focus is 100% on delivering end-to-end value across the organization
    • 84. “If all we do is find another way to measure activity, we will not be successful” – CTO
    • 85. Let’s start with a definition of value…
    • 86. Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about.
      Epic
    • 87. Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about.
      Epic
      Features are smaller than epics, typically 2-4 weeks in duration. Features are contained within releases. Ideally, features are contained within a team. These are what the Product Owner Cares about.
      Feature
    • 88. Epics collections of features, typically 1-3 months in duration. Epics span releases. Epics can span more than one team. These are the things the market cares about.
      Epic
      Features are smaller than epics, typically 2-4 weeks in duration. Features are contained within releases. Ideally, features are contained within a team. These are what the Product Owner Cares about.
      Feature
      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.
      User
      Story
    • 89. Story Maps visually show the relationship between User Stories and Business Value
      Epic
      Feature
      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
      User Story
    • 90. Story Maps start with the identification of larger, more strategic organizational goals
      Epic
    • 91. Epicsare decomposed into Features that describe the value added into the product
      Epic
      Feature
    • 92. Epicsare decomposed into Features that describe the value added into the product
      Epic
      Feature
      Feature
    • 93. Epicsare decomposed into Features that describe the value added into the product
      Epic
      Feature
      Feature
      Feature
    • 94. Epicsare decomposed into Features that describe the value added into the product
      Epic
      Feature
      Feature
      Feature
      Feature
    • 95. Featuresare decomposed into User Stories that are thin slices of value added into the system
      Epic
      Feature
      Feature
      Feature
      Feature
      User Story
      User Story
      User Story
      User Story
    • 96. Featuresare decomposed into User Stories that are thin slices of value added into the system
      Epic
      Feature
      Feature
      Feature
      Feature
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
    • 97. Featuresare decomposed into User Stories that are thin slices of value added into the system
      Epic
      Feature
      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
    • 98. Featuresare decomposed into User Stories that are thin slices of value added into the system
      Epic
      Feature
      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
      User Story
    • 99. User Stories are estimated in relative units of measure called Story Points
      Epic
      3
      1
      2
      1
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      5
      2
      3
      2
      1
      1
      2
      2
      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
      User Story
    • 100. Story Points can be added up to size Features
      Epic
      11
      7
      8
      12
      3
      1
      2
      1
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      5
      2
      3
      2
      1
      1
      2
      2
      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
      User Story
    • 101. Feature Points can be added up to size Epics
      38
      Epic
      11
      7
      8
      12
      3
      1
      2
      1
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      5
      2
      3
      2
      1
      1
      2
      2
      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
      User Story
    • 102. Our Goal is to build the smallest system possible to deliver the value in the Epic
      38
      Epic
      11
      7
      8
      12
      3
      1
      2
      1
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      5
      2
      3
      2
      1
      1
      2
      2
      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
      User Story
    • 103. We continuously evaluate the Story Map to determine the Minimally Marketable Feature
      38
      Epic
      11
      7
      8
      12
      3
      1
      2
      1
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      5
      2
      3
      2
      1
      1
      2
      2
      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
      User Story
    • 104. We continuously evaluate the Story Map to determine the Minimally Marketable Feature
      38
      Epic
      11
      7
      8
      12
      3
      1
      2
      1
      User Story
      User Story
      User Story
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      User Story
      User Story
      User Story
      5
      2
      3
      2
      User Story
      User Story
      User Story
      1
      1
      2
      2
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
    • 105. When we focus on Minimally Marketable Features, we deliver Business Value early
      26
      Epic
      10
      4
      7
      5
      3
      1
      2
      1
      User Story
      User Story
      User Story
      Feature
      Feature
      Feature
      Feature
      3
      2
      3
      5
      User Story
      User Story
      User Story
      5
      2
      3
      2
      User Story
      User Story
      User Story
      1
      1
      2
      2
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
      User Story
    • 106. Minimally Marketable Featuresfeed the prioritization of our Sprint Planning
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
    • 107. Identify the User Story most likely to contribute to the MMF and build that one first
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
    • 108. Identify the User Story most likely to contribute to the MMF and build that one first
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      User Story
    • 109. Pull User Stories in priority order focusing on delivering complete MMFs
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      User Story
    • 110. Pull User Stories in priority order focusing on delivering complete MMFs
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      User Story
      2
      User Story
    • 111. It’s okay to work User Stories across MMFs if that is what the Product Owner needs
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      User Story
      2
      User Story
    • 112. It’s okay to work User Stories across MMFs if that is what the Product Owner needs
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      User Story
      2
      User Story
      1
      User Story
    • 113. The team uses its past velocity to determine how many stories go in the Sprint
      Planned Team Velocity = 6 points
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      User Story
      2
      User Story
      1
      User Story
    • 114. The Team breaks each User Story down into Tasks
      Planned Team Velocity = 6 points
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      Task
      Task
      User Story
      Task
      2
      User Story
      1
      User Story
    • 115. The Team breaks each User Story down into Tasks
      Planned Team Velocity = 6 points
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      Task
      Task
      User Story
      Task
      2
      Task
      Task
      User Story
      Task
      Task
      1
      User Story
    • 116. The Team breaks each User Story down into Tasks
      Planned Team Velocity = 6 points
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      Task
      Task
      User Story
      Task
      2
      Task
      Task
      User Story
      Task
      Task
      Task
      Task
      1
      User Story
      Task
      Task
    • 117. 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
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      16
      8
      Task
      Task
      User Story
      8
      Task
      2
      Task
      Task
      User Story
      Task
      Task
      Task
      Task
      1
      User Story
      Task
      Task
    • 118. 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
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      16
      8
      Task
      Task
      User Story
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      Task
      Task
      1
      User Story
      Task
      Task
    • 119. 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 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      16
      8
      Task
      Task
      User Story
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      16
      8
      Task
      Task
    • 120. 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 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      16
      8
      Task
      Task
      User Story
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      16
      8
      Task
      Task
    • 121. 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 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      16
      8
      Task
      Task
    • 122. Tasks move across the Story Board until there is a completed User Story.
      Planned Team Velocity = 6 points
      Planned Estimated Hours = 98 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      16
      8
      Task
      Task
    • 123. Tasks move across the Story Board until there is a completed User Story.
      Planned Team Velocity = 6 points
      Planned Estimated Hours = 98 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      8
      Task
      16
      Task
    • 124. Tasks move across the Story Board until there is a completed User Story.
      Planned Team Velocity = 6 points
      Planned Estimated Hours = 98 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      8
      Task
      16
      Task
    • 125. 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 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      8
      Task
      16
      Task
    • 126. 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 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      8
      Task
      16
      Task
    • 127. 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 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      8
      4
      Task
      Task
      1
      User Story
      8
      Task
      16
      Task
    • 128. Until the entire Sprint has been delivered to the Product Owner.
      Planned Team Velocity = 6 points
      Planned Estimated Hours = 98 hours
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      3
      8
      Task
      User Story
      16
      Task
      8
      Task
      2
      2
      16
      Task
      Task
      User Story
      8
      Task
      4
      Task
      1
      8
      4
      Task
      User Story
      Task
      8
      Task
      16
      Task
    • 129. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 130. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 131. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 132. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 133. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 134. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 135. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 136. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 137. From a Metrics perspective, we Burn Down hours to make sure the sprint is on track
      38
      96
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 138. From a Metrics perspective, we Burn Down points to make sure the Release is on track
      38
      96
      6
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 139. From a Metrics perspective, we Burn Down points to make sure the Release is on track
      38
      96
      8
      6
      6
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 140. We track Velocity Trend to make sure the team is delivering in a Predictable manner
      38
      96
      8
      6
      6
      5
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 141. 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
    • 142. 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
    • 143. Team
    • 144. Team
      Team
    • 145. Team
      Team
      Team
    • 146. Team
      Team
      Team
      Team
    • 147. Team
      Team
      Team
      Team
      Team
    • 148. How do we establish the relationship between team level velocity and enterprise level flow of value?
    • 149. Team predictability is one thing, but organizations need to be able to track value at the Epic level
      Epic
    • 150. Team predictability is one thing, but organizations need to be able to track value at the Epic level
      Epic
      We need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features.
      Feature
    • 151. Team predictability is one thing, but organizations need to be able to track value at the Epic level
      Epic
      We need a mechanism to make sure features that span multiple Scrum teams are treated with the same sense of awareness as single-product features.
      Feature
      All of our day-to-day activities need to clearly map to enterprise objectives. We need to build product as one organization
      User
      Story
    • 152. Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      Tier 1 - Scrum
    • 153. Deploy
      Build
      Test
      Design
      Analysis
      Tier 2 - Kanban
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      Tier 1 - Scrum
    • 154. Construction
      Transition
      Elaboration
      Inception
      Tier 3 - Kanban
      Deploy
      Build
      Test
      Design
      Analysis
      Tier 2 - Kanban
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      Tier 1 - Scrum
    • 155. Kanban creates a pull system across the entire portfolio that is limited by your actual capacity
    • 156. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
    • 157. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
    • 158. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
    • 159. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
    • 160. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      Spike
    • 161. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      User Story
      User Story
      Spike
    • 162. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 163. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 164. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 165. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 166. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 167. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 168. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 169. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 170. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 171. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      8
      Task
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 172. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 173. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 174. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 175. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 176. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 177. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 178. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 179. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 180. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      8
      Task
      User Story
      User Story
      Spike
      8
      Task
    • 181. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      User Story
      User Story
      Spike
      8
      Task
      8
      Task
    • 182. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      User Story
      User Story
      Spike
      8
      Task
      8
      Task
    • 183. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      Task
      User Story
      User Story
      User Story
      User Story
      8
      Task
      Spike
      Spike
      8
      Task
      8
      8
      Task
      Task
    • 184. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      16
      Task
      User Story
      User Story
      User Story
      User Story
      Spike
      Spike
      8
      Task
      8
      Task
    • 185. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 186. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 187. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 188. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      User Story
      User Story
      8
      Task
      Spike
      8
      Task
    • 189. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 190. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 191. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 192. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      Task
      8
      User Story
      User Story
      Task
      Spike
      8
      Task
    • 193. Construction
      Transition
      Elaboration
      Inception
      Epic
      Epic
      Epic
      Epic
      Deploy
      Build
      Test
      Design
      Analysis
      Feature
      Feature
      Feature
      Feature
      Feature
      Feature
      Story Backlog
      In Process
      Task Done
      Task Backlog
      Story Backlog
      8
      8
      Task
      Task
      Task
      8
      User Story
      User Story
      User Story
      User Story
      8
      Task
      Task
      Spike
      Spike
      8
      8
      8
      Task
      Task
      Task
    • 194. At the team level, velocity metrics drive predictability
      38
      96
      8
      6
      6
      5
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 195. At the program/product level, lean metrics are more meaningful
      At the team level, velocity metrics drive predictability
      38
      96
      8
      6
      6
      5
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 196. At the enterprise level, lean metrics are also the more interesting metric
      At the program/product level, lean metrics are more meaningful
      At the team level, velocity metrics drive predictability
      38
      96
      8
      6
      6
      5
      Release Burndown
      Sprint Burndown
      Velocity Trend
    • 197. Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLCmike@leadingagile.com 1.404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer