SlideShare a Scribd company logo

Kanban with scrum or is it scrum with kanban.001

•Download as PPTX, PDF•
•
T
Tom Reynolds

The document discusses how Kanban and Scrum can be used together rather than as mutually exclusive frameworks. It describes key aspects of Kanban such as limiting work-in-progress, visualizing workflow, and continuous flow. It also outlines Scrum practices like sprints, product backlogs, and retrospectives. The document then shows how Kanban techniques like pull systems and WIP limits can be applied within a Scrum framework to manage flow across the entire value stream from concept to cash. It argues this combined approach allows for scaling agile across multiple teams.

1 of 19
Kanban with Scrum or is it Scrum with Kanban © 2018 BeLiminal LLP
@tomjreynolds uk.linkedin.com/in/tomjreynolds  Agile Coach & Trainer  Organisational & Relationship Systems Coach  International Conference Speaker  25+ years in software development  Multi Certified Trainer  Agile since 2007 Tom Reynolds
 Change management method  Controls work with WIP limits  Visualise work  Flow based  Pull system  Process policies are explicit  Feedback mechanisms  Collaborative work  Evolutionary improvement What is Kanban? Visualise Limit WIP Manage Flow Make Process Policies Explicit Develop Feedback Mechanisms at workflow, inter- workflow & Organisational Levels Improve Collaboratively Using “Safe to Fail” Experiments
 Cadence based  Empirical  Time boxed  Reduces batch size  Collaborative work  ‘Done’ policies explicit  Feedback mechanisms  Evolutionary Improvement What is Scrum? Adapted from Mike Cohn – Mountain Goat Software Product Backlog Refinement Rule of thumb: 10% of overall Sprint time spent on meetings 1 month or less The Sprint
Are these methods mutually exclusive or can they be used in conjunction with one another and if so how might that be possible?
Tasks (Sprint Backlog - including at least 1 improvement item) Product Backlog Selected Product Backlog Development Team Forecast Product Owner Discuss and clarify the selected backlog Sprint Goal Product Owner and Team agree a Sprint Goal and the Team forecast the work of the Sprint Sprint Day 1 of The Sprint 8 Hours Maximum Scrum Master Let’s start with Scrum – Sprint Planning
As a I want so that... As a I want so that... As a I want so that... User Stories To Do WIP (Work In Progress) Done Task Cards Task Board
Product Backlog Refinement Development Team Product Backlog Additionally Refined Product Backlog Product Owner Discuss, refine and elaborate. Add acceptance criteria and size Initially before development, then iteratively every sprint No more than 10% of development team capacity
Managing refinement Product Backlog Refinement Sprint Committed User Stories (Sprint Backlog) In Progress Ready for Sprint Review WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work
Apply WIP limits Product Backlog <∞> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity
Pull system present with WIP limits Product Backlog <∞> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity Pull
Moving downstream Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity
Moving downstream Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity Pull
Commitment and Measurement Options Refinement Sprint Committed In Progress Ready for Sprint Review Sprint Review Ready to Deploy Analysis and RFC Deploying Done Customer Lead Time Commitment is Deferred Abandon prior to commitment Commitment Point Can consider this to be discovery
Kanban system or Scrum system? Options <∞> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done WI P Done
Moving further upstream Project ideas <∞> Initiate <1-2> Story Mapping <1> Options <1 project> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done WIP Done WIP Done WIP Done Discovery Delivery
Scaling across teams Project ideas <∞> Initiate <1-2> Story Mapping <1> Options <1 project > Refinement <16 per team> Sprint Committed User Stories (Sprint Backlog) <Velocity per team> In Progress <3 User Stories per team> Ready for Sprint Review <Velocity per team> Sprint Review <Velocity per team> Ready to Deploy <16> Analysi s and RFC <8> Deploying <16> Done WIP Done WIP Done TeamA WIP Done WIP Done TeamB
Managing across a value stream? © 2013 The Agile Mindset Ltd Concept Cash
The question was “Kanban with Scrum or is it Scrum with Kanban” What do you think? © 2018 BeLiminal LLP

More Related Content

Kanban with scrum or is it scrum with kanban.001

  • 1. Kanban with Scrum or is it Scrum with Kanban © 2018 BeLiminal LLP
  • 2. @tomjreynolds uk.linkedin.com/in/tomjreynolds  Agile Coach & Trainer  Organisational & Relationship Systems Coach  International Conference Speaker  25+ years in software development  Multi Certified Trainer  Agile since 2007 Tom Reynolds
  • 3.  Change management method  Controls work with WIP limits  Visualise work  Flow based  Pull system  Process policies are explicit  Feedback mechanisms  Collaborative work  Evolutionary improvement What is Kanban? Visualise Limit WIP Manage Flow Make Process Policies Explicit Develop Feedback Mechanisms at workflow, inter- workflow & Organisational Levels Improve Collaboratively Using “Safe to Fail” Experiments
  • 4.  Cadence based  Empirical  Time boxed  Reduces batch size  Collaborative work  ‘Done’ policies explicit  Feedback mechanisms  Evolutionary Improvement What is Scrum? Adapted from Mike Cohn – Mountain Goat Software Product Backlog Refinement Rule of thumb: 10% of overall Sprint time spent on meetings 1 month or less The Sprint
  • 5. Are these methods mutually exclusive or can they be used in conjunction with one another and if so how might that be possible?
  • 6. Tasks (Sprint Backlog - including at least 1 improvement item) Product Backlog Selected Product Backlog Development Team Forecast Product Owner Discuss and clarify the selected backlog Sprint Goal Product Owner and Team agree a Sprint Goal and the Team forecast the work of the Sprint Sprint Day 1 of The Sprint 8 Hours Maximum Scrum Master Let’s start with Scrum – Sprint Planning
  • 7. As a I want so that... As a I want so that... As a I want so that... User Stories To Do WIP (Work In Progress) Done Task Cards Task Board
  • 8. Product Backlog Refinement Development Team Product Backlog Additionally Refined Product Backlog Product Owner Discuss, refine and elaborate. Add acceptance criteria and size Initially before development, then iteratively every sprint No more than 10% of development team capacity
  • 9. Managing refinement Product Backlog Refinement Sprint Committed User Stories (Sprint Backlog) In Progress Ready for Sprint Review WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work
  • 10. Apply WIP limits Product Backlog <∞> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity
  • 11. Pull system present with WIP limits Product Backlog <∞> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity Pull
  • 12. Moving downstream Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity
  • 13. Moving downstream Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done The Sprint Typically 2 weeks – Consider this a 2 week batch of work – Batch WIP limited by team velocity Pull
  • 14. Commitment and Measurement Options Refinement Sprint Committed In Progress Ready for Sprint Review Sprint Review Ready to Deploy Analysis and RFC Deploying Done Customer Lead Time Commitment is Deferred Abandon prior to commitment Commitment Point Can consider this to be discovery
  • 15. Kanban system or Scrum system? Options <∞> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done WI P Done
  • 16. Moving further upstream Project ideas <∞> Initiate <1-2> Story Mapping <1> Options <1 project> Refinement <16> Sprint Committed User Stories (Sprint Backlog) <Velocity> In Progress <3 User Stories> Ready for Sprint Review <Velocity> Sprint Review <Velocity> Ready to Deploy <16> Analysis and RFC <8> Deploying <16> Done WIP Done WIP Done WIP Done WIP Done Discovery Delivery
  • 17. Scaling across teams Project ideas <∞> Initiate <1-2> Story Mapping <1> Options <1 project > Refinement <16 per team> Sprint Committed User Stories (Sprint Backlog) <Velocity per team> In Progress <3 User Stories per team> Ready for Sprint Review <Velocity per team> Sprint Review <Velocity per team> Ready to Deploy <16> Analysi s and RFC <8> Deploying <16> Done WIP Done WIP Done TeamA WIP Done WIP Done TeamB
  • 18. Managing across a value stream? © 2013 The Agile Mindset Ltd Concept Cash
  • 19. The question was “Kanban with Scrum or is it Scrum with Kanban” What do you think? © 2018 BeLiminal LLP

Editor's Notes

  1. Stand and form pairs and triads In your groups share with your colleagues two things What you want to learn today? What you already know about this topic
  2. TR
  3. EH
  4. After Planning Meeting I – COMMITMENT – as a contract between Team and Product Owner. Explain the differences between Tactical level and Strategy Level
  5. Example Task Board
  6. After Planning Meeting I – COMMITMENT – as a contract between Team and Product Owner. Explain the differences between Tactical level and Strategy Level
  7. Is this a Kanban system, Scrum system or something else Stand to the left if it is a Kanban system Stand to the right if it is a Scrum system Stand in the middle if it is something else Discuss in pairs and triads why you think it is what you have chosen
  8. Is this a Kanban system, Scrum system or something else Stand to the left if it is a Kanban system Stand to the right if it is a Scrum system Stand in the middle if it is something else Discuss in pairs and triads why you think it is what you have chosen
  9. Table talk Stand and forms pairs and triads In your group share with each other the most important concept that you learned from the training Answer and discuss the question “Is it Kanban with Scrum or is it Scrum with Kanban”