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

Scrum and kanban in the enterprise webinar

on

  • 4,486 views

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.

Statistics

Views

Total Views
4,486
Views on SlideShare
4,480
Embed Views
6

Actions

Likes
20
Downloads
346
Comments
2

4 Embeds 6

http://paper.li 2
https://twitter.com 2
http://www.slideshare.net 1
http://tweetedtimes.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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.

Scrum and kanban in the enterprise   webinar Scrum and kanban in the enterprise webinar Presentation Transcript

  • Blending Scrum and Kanban to Create an End-to-End Agile Enterprise
  • Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLCmike@leadingagile.com 1.404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer
  • Agenda
    Why this talk? Isn’t Scrum enough?
  • 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
  • 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
  • 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
  • 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
  • Why Not Just Scrum?
  • Scrum is a team based approach to product delivery.
  • Team
  • Developers
  • Testers
    Developers
  • Analyst
    Testers
    Developers
  • Analyst
    ScrumMaster
    Testers
    Developers
  • Product Owner
    Analyst
    ScrumMaster
    Testers
    Developers
  • What if my team is more than 5-7 people?
  • Scrum in the Enterprise
  • Scrum in the Enterprise
  • Enterprise Scrum
  • Enterprise Scrum... it’s different!
  • Enterprise Scrum
  • Enterprise Scrum
  • Enterprise Scrum
  • Enterprise Scrum
  • Enterprise Scrum
  • Enterprise Scrum
  • Enterprise Scrum
  • What breaks Scrum?
  • External Dependencies
  • External Dependencies
  • External Dependencies
  • Why dependencies matter?
    Velocity dependent on something outside the team
  • Why dependencies matter?
    Velocity dependent on something outside the team
    External dependencies have to be managed and planned for in advance
  • 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
  • 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
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Many-to-Many Relationships
  • Why many-to-many matters?
    Team velocity is not a predictor of higher order deliverables
  • 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
  • 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
  • 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
  • What do we mean by end-to-end business agility?
  • We want the benefits of team-level agility….
  • We want the benefits of team-level agility…. but across the entire company
  • We want a pattern that can accommodate Sales and Marketing…
  • …several Scrum teams, service orientation, and shared services…
  • …as well as technical support and ultimately sustaining engineering
  • At some level of scale, Scrum breaks.
  • At some level of scale, Scrum breaks. What are you going to do about it?
  • Tools available to scale Scrum
    Scrum and XP
  • Tools available to scale Scrum
    Scrum and XP
    Kanban
  • Tools available to scale Scrum
    Scrum and XP
    Kanban
    Lean
  • Tools available to scale Scrum
    Scrum and XP
    Kanban
    Lean
    RUP
  • Tools available to scale Scrum
    Scrum and XP
    Kanban
    Lean
    RUP
    Traditional SDLC
  • Interesting idea… how to we get there?
  • It always starts with teams...
  • Ways to organize teams…
    Products
  • Ways to organize teams…
    Products
    Product features
  • Ways to organize teams…
    Products
    Product features
    Components
  • Ways to organize teams…
    Products
    Product features
    Components
    Shared services
  • Ways to organize teams…
    Products
    Product features
    Components
    Shared services
    Business capabilities
  • Get the teams working…
    Define the org structure
  • Get the teams working…
    Define the org structure
    Form the teams
  • Get the teams working…
    Define the org structure
    Form the teams
    Get the teams delivering
  • Get the teams working…
    Define the org structure
    Form the teams
    Get the teams delivering
    Focus on establishing a stable velocity
  • Get the teams working…
    Define the org structure
    Form the teams
    Get the teams delivering
    Focus on establishing a stable velocity
    Learn what works
  • Incrementally roll-out Scrum across the organization…
  • Incrementally roll-out Scrum across the organization……
  • Incrementally roll-out Scrum across the organization………
  • Establish Program Teams and/or Product Integration teams
  • Establish Program Teams and/or Product Integration teams
  • Establish a Portfolio Planning team
  • Manage the flow of value at each level
  • So… what does it look like when I am done?
  • Focus is 100% on delivering end-to-end value across the organization
  • “If all we do is find another way to measure activity, we will not be successful” – CTO
  • Let’s start with a definition of value…
  • 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
  • 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
  • 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
  • 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
  • Story Maps start with the identification of larger, more strategic organizational goals
    Epic
  • Epicsare decomposed into Features that describe the value added into the product
    Epic
    Feature
  • Epicsare decomposed into Features that describe the value added into the product
    Epic
    Feature
    Feature
  • Epicsare decomposed into Features that describe the value added into the product
    Epic
    Feature
    Feature
    Feature
  • Epicsare decomposed into Features that describe the value added into the product
    Epic
    Feature
    Feature
    Feature
    Feature
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • Minimally Marketable Featuresfeed the prioritization of our Sprint Planning
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
  • 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
  • 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
  • Pull User Stories in priority order focusing on delivering complete MMFs
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
    3
    User Story
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • Team
  • Team
    Team
  • Team
    Team
    Team
  • Team
    Team
    Team
    Team
  • Team
    Team
    Team
    Team
    Team
  • How do we establish the relationship between team level velocity and enterprise level flow of value?
  • Team predictability is one thing, but organizations need to be able to track value at the Epic level
    Epic
  • 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
  • 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
  • Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
    Tier 1 - Scrum
  • Deploy
    Build
    Test
    Design
    Analysis
    Tier 2 - Kanban
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
    Tier 1 - Scrum
  • 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
  • Kanban creates a pull system across the entire portfolio that is limited by your actual capacity
  • Construction
    Transition
    Elaboration
    Inception
    Epic
    Epic
    Deploy
    Build
    Test
    Design
    Analysis
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
  • Construction
    Transition
    Elaboration
    Inception
    Epic
    Epic
    Deploy
    Build
    Test
    Design
    Analysis
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
  • Construction
    Transition
    Elaboration
    Inception
    Epic
    Epic
    Deploy
    Build
    Test
    Design
    Analysis
    Feature
    Feature
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
  • Construction
    Transition
    Elaboration
    Inception
    Epic
    Epic
    Deploy
    Build
    Test
    Design
    Analysis
    Feature
    Feature
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
  • Construction
    Transition
    Elaboration
    Inception
    Epic
    Epic
    Deploy
    Build
    Test
    Design
    Analysis
    Feature
    Feature
    Story Backlog
    In Process
    Task Done
    Task Backlog
    Story Backlog
    Spike
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • At the team level, velocity metrics drive predictability
    38
    96
    8
    6
    6
    5
    Release Burndown
    Sprint Burndown
    Velocity Trend
  • 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
  • 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
  • Mike CottmeyerEnterprise Agile Coach, LeadingAgile, LLCmike@leadingagile.com 1.404.312.1471www.leadingagile.comtwitter.com/mcottmeyerfacebook.com/leadingagilelinkedin.com/in/cottmeyer