Your SlideShare is downloading. ×
0
Blending Scrum and Kanban to Create an End-to-End Agile Enterprise<br />
Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLCmike@leadingagile.com	1.404.312.1471www.leadingagile.comtwitter.com...
Agenda<br />Why this talk?  Isn’t Scrum enough?<br />
Agenda<br />Why this talk?  Isn’t Scrum enough?<br />Discuss what end-to-end business agility looks like and how it is dif...
Agenda<br />Why this talk?  Isn’t Scrum enough?<br />Discuss what end-to-end business agility looks like and how it is dif...
Agenda<br />Why this talk?  Isn’t Scrum enough?<br />Discuss what end-to-end business agility looks like and how it is dif...
Agenda<br />Why this talk?  Isn’t Scrum enough?<br />Discuss what end-to-end business agility looks like and how it is dif...
Why Not Just Scrum?<br />
Scrum is a team based approach to product delivery.<br />
Team<br />
Developers<br />
Testers<br />Developers<br />
Analyst<br />Testers<br />Developers<br />
Analyst<br />ScrumMaster<br />Testers<br />Developers<br />
Product Owner<br />Analyst<br />ScrumMaster<br />Testers<br />Developers<br />
What if my team is more than 5-7 people?<br />
Scrum in the Enterprise<br />
Scrum in the Enterprise<br />
Enterprise Scrum<br />
Enterprise Scrum... it’s different!<br />
Enterprise Scrum<br />
Enterprise Scrum<br />
Enterprise Scrum<br />
Enterprise Scrum<br />
Enterprise Scrum<br />
Enterprise Scrum<br />
Enterprise Scrum<br />
What breaks Scrum?<br />
External Dependencies<br />
External Dependencies<br />
External Dependencies<br />
Why dependencies matter?<br />Velocity dependent on something outside the team<br />
Why dependencies matter?<br />Velocity dependent on something outside the team<br />External dependencies have to be manag...
Why dependencies matter?<br />Velocity dependent on something outside the team<br />External dependencies have to be manag...
Why dependencies matter?<br />Velocity dependent on something outside the team<br />External dependencies have to be manag...
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Many-to-Many Relationships<br />
Why many-to-many matters?<br />Team velocity is not a predictor of higher order deliverables<br />
Why many-to-many matters?<br />Team velocity is not a predictor of higher order deliverables<br />One or more teams can st...
Why many-to-many matters?<br />Team velocity is not a predictor of higher order deliverables<br />One or more teams can st...
Why many-to-many matters?<br />Team velocity is not a predictor of higher order deliverables<br />One or more teams can st...
What do we mean by end-to-end business agility?<br />
We want the benefits of team-level agility….<br />
We want the benefits of team-level agility…. but across the entire company<br />
We want a pattern that can accommodate Sales and Marketing…<br />
…several Scrum teams, service orientation, and shared services…<br />
…as well as technical support and ultimately sustaining engineering<br />
At some level of scale, Scrum breaks.  <br />
At some level of scale, Scrum breaks.  What are you going to do about it?<br />
Tools available to scale Scrum<br />Scrum and XP<br />
Tools available to scale Scrum<br />Scrum and XP<br />Kanban<br />
Tools available to scale Scrum<br />Scrum and XP<br />Kanban<br />Lean<br />
Tools available to scale Scrum<br />Scrum and XP<br />Kanban<br />Lean<br />RUP<br />
Tools available to scale Scrum<br />Scrum and XP<br />Kanban<br />Lean<br />RUP<br />Traditional SDLC<br />
Interesting idea… how to we get there?<br />
It always starts with teams...<br />
Ways to organize teams… <br />Products<br />
Ways to organize teams… <br />Products<br />Product features<br />
Ways to organize teams… <br />Products<br />Product features<br />Components<br />
Ways to organize teams… <br />Products<br />Product features<br />Components<br />Shared services<br />
Ways to organize teams… <br />Products<br />Product features<br />Components<br />Shared services<br />Business capabiliti...
Get the teams working…<br />Define the org structure<br />
Get the teams working…<br />Define the org structure<br />Form the teams<br />
Get the teams working…<br />Define the org structure<br />Form the teams<br />Get the teams delivering<br />
Get the teams working…<br />Define the org structure<br />Form the teams<br />Get the teams delivering<br />Focus on estab...
Get the teams working…<br />Define the org structure<br />Form the teams<br />Get the teams delivering<br />Focus on estab...
Incrementally roll-out Scrum across the organization…<br />
Incrementally roll-out Scrum across the organization……<br />
Incrementally roll-out Scrum across the organization………<br />
Establish Program Teams and/or Product Integration teams <br />
Establish Program Teams and/or Product Integration teams <br />
Establish a Portfolio Planning team<br />
Manage the flow of value at each level <br />
So… what does it look like when I am done?<br />
Focus is 100% on delivering end-to-end value across the organization<br />
“If all we do is find another way to measure activity, we will not be successful” – CTO<br />
Let’s start with a definition of value…<br />
Epics collections of features, typically 1-3 months in duration.  Epics span releases.  Epics can span more than one team....
Epics collections of features, typically 1-3 months in duration.  Epics span releases.  Epics can span more than one team....
Epics collections of features, typically 1-3 months in duration.  Epics span releases.  Epics can span more than one team....
Story Maps visually show the relationship between User Stories and Business Value<br />Epic<br />Feature<br />Feature<br /...
Story Maps start with the identification of larger, more strategic organizational goals<br />Epic<br />
Epicsare decomposed into Features that describe the value added into the product<br />Epic<br />Feature<br />
Epicsare decomposed into Features that describe the value added into the product<br />Epic<br />Feature<br />Feature<br />
Epicsare decomposed into Features that describe the value added into the product<br />Epic<br />Feature<br />Feature<br />...
Epicsare decomposed into Features that describe the value added into the product<br />Epic<br />Feature<br />Feature<br />...
Featuresare decomposed into User Stories that are thin slices of value added into the system<br />Epic<br />Feature<br />F...
Featuresare decomposed into User Stories that are thin slices of value added into the system<br />Epic<br />Feature<br />F...
Featuresare decomposed into User Stories that are thin slices of value added into the system<br />Epic<br />Feature<br />F...
Featuresare decomposed into User Stories that are thin slices of value added into the system<br />Epic<br />Feature<br />F...
User Stories are estimated in relative units of measure called Story Points<br />Epic<br />3<br />1<br />2<br />1<br />Fea...
Story Points can be added up to size Features<br />Epic<br />11<br />7<br />8<br />12<br />3<br />1<br />2<br />1<br />Fea...
Feature Points can be added up to size Epics<br />38<br />Epic<br />11<br />7<br />8<br />12<br />3<br />1<br />2<br />1<b...
Our Goal is to build the smallest system possible to deliver the value in the Epic<br />38<br />Epic<br />11<br />7<br />8...
We continuously evaluate the Story Map to determine the Minimally Marketable Feature<br />38<br />Epic<br />11<br />7<br /...
We continuously evaluate the Story Map to determine the Minimally Marketable Feature<br />38<br />Epic<br />11<br />7<br /...
When we focus on Minimally Marketable Features, we deliver Business Value early<br />26<br />Epic<br />10<br />4<br />7<br...
Minimally Marketable Featuresfeed the prioritization of our Sprint Planning<br />Story Backlog<br />In Process<br />Task D...
Identify the User Story most likely to contribute to the MMF and build that one first<br />Story Backlog<br />In Process<b...
Identify the User Story most likely to contribute to the MMF and build that one first<br />Story Backlog<br />In Process<b...
Pull User Stories in priority order focusing on delivering complete MMFs<br />Story Backlog<br />In Process<br />Task Done...
Pull User Stories in priority order focusing on delivering complete MMFs<br />Story Backlog<br />In Process<br />Task Done...
It’s okay to work User Stories across MMFs if that is what the Product Owner needs<br />Story Backlog<br />In Process<br /...
It’s okay to work User Stories across MMFs if that is what the Product Owner needs<br />Story Backlog<br />In Process<br /...
The team uses its past velocity to determine how many stories go in the Sprint<br />Planned Team Velocity = 6 points<br />...
The Team breaks each User Story down into Tasks<br />Planned Team Velocity = 6 points<br />Story Backlog<br />In Process<b...
The Team breaks each User Story down into Tasks<br />Planned Team Velocity = 6 points<br />Story Backlog<br />In Process<b...
The Team breaks each User Story down into Tasks<br />Planned Team Velocity = 6 points<br />Story Backlog<br />In Process<b...
And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver<br />Planned Team ...
And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver<br />Planned Team ...
And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver<br />Planned Team ...
And estimates each Task in Real Hours so they can assess if they can make a solid Commitment to Deliver<br />Planned Team ...
At the beginning of the Sprint, The Team pulls Tasks from the top of the Task Backlog<br />Planned Team Velocity = 6 point...
Tasks move across the Story Board until there is a completed User Story.  <br />Planned Team Velocity = 6 points<br />Plan...
Tasks move across the Story Board until there is a completed User Story.  <br />Planned Team Velocity = 6 points<br />Plan...
Tasks move across the Story Board until there is a completed User Story.  <br />Planned Team Velocity = 6 points<br />Plan...
The Team works from the top of the Story Board, Swarming to get  User Stories across the board as fast as possible .  <br ...
The Team works from the top of the Story Board, Swarming to get  User Stories across the board as fast as possible .  <br ...
The Team works from the top of the Story Board, Swarming to get  User Stories across the board as fast as possible .  <br ...
Until the entire Sprint has been delivered to the Product Owner.  <br />Planned Team Velocity = 6 points<br />Planned Esti...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down hours to make sure the sprint is on track<br />38<br />96<br />6<br />Release Bur...
From a Metrics perspective, we Burn Down points to make sure the Release is on track<br />38<br />96<br />6<br />6<br />Re...
From a Metrics perspective, we Burn Down points to make sure the Release is on track<br />38<br />96<br />8<br />6<br />6<...
We track Velocity Trend to make sure the team is delivering in a Predictable manner<br />38<br />96<br />8<br />6<br />6<b...
When the Release is ready to deliver, The Team has completed the highest priority User Stories, against the highest priori...
When the Release is ready to deliver, The Team has completed the highest priority User Stories, against the highest priori...
Team<br />
Team<br />Team<br />
Team<br />Team<br />Team<br />
Team<br />Team<br />Team<br />Team<br />
Team<br />Team<br />Team<br />Team<br />Team<br />
How do we establish the relationship between team level velocity and enterprise level flow of value?<br />
Team predictability is one thing, but organizations need to be able to track value at the Epic level<br />Epic<br />
Team predictability is one thing, but organizations need to be able to track value at the Epic level<br />Epic<br />We nee...
Team predictability is one thing, but organizations need to be able to track value at the Epic level<br />Epic<br />We nee...
Story Backlog<br />In Process<br />Task Done<br />Task Backlog<br />Story Backlog<br />Tier 1 - Scrum<br />
Deploy<br />Build	<br />Test	<br />Design<br />Analysis<br />Tier 2 - Kanban<br />Story Backlog<br />In Process<br />Task ...
Construction<br />Transition<br />Elaboration<br />Inception<br />Tier 3 - Kanban<br />Deploy<br />Build	<br />Test	<br />...
Kanban creates a pull system across the entire portfolio that is limited by your actual capacity<br />
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Deploy<br />Build	<br />Test	<br />D...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Deploy<br />Build	<br />Te...
Construction<br />Transition<br />Elaboration<br />Inception<br />Epic<br />Epic<br />Epic<br />Epic<br />Deploy<br />Buil...
At the team level, velocity metrics drive predictability<br />38<br />96<br />8<br />6<br />6<br />5<br />Release Burndown...
At the program/product level, lean metrics are more meaningful<br />At the team level, velocity metrics drive predictabili...
At the enterprise level, lean metrics are also the more interesting metric<br />At the program/product level, lean metrics...
Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLCmike@leadingagile.com	1.404.312.1471www.leadingagile.comtwitter.com...
Upcoming SlideShare
Loading in...5
×

Scrum and kanban in the enterprise webinar

4,320

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.

Published in: Lifestyle, Technology
2 Comments
21 Likes
Statistics
Notes
No Downloads
Views
Total Views
4,320
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
381
Comments
2
Likes
21
Embeds 0
No embeds

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 of "Scrum and kanban in the enterprise webinar"

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

      Clipping is a handy way to collect important slides you want to go back to later.

    ×