Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

ScrumBan : Best of Both Worlds. A Fertile Hybrid

2,315 views

Published on

Fusion at its best. The ScrumBan is a combination of best practices from Scrum and Kanban. Scrumban can be used effectively to have on demand agility

Published in: Technology

ScrumBan : Best of Both Worlds. A Fertile Hybrid

  1. 1. ScrumBan : Best of Both worlds A Fertile Hybrid by using Scrum & Kanban 1
  2. 2. Jaya Shrivastava SW Development Consultant Agile Coach & Trainer Status Quo Disruptor ● CSM ● CSPO ● CSP ● SPC Speaker, Blogger & Preacher Solution Oriented NOT problem focuses 2
  3. 3. ScrumBan is ● Combination ● Application of Kanban method with scrum support. ● Applying Kanban together with Scrum concepts. ● Highly influenced by Kanban Model of Work. So.... Need to understand Scrum & Kanban for understanding ScrumBan 3
  4. 4. When to Use Scrumban ● Uncertainty ● Production Support/ Maintenance ● Helpdesk Support ● Projects with frequent requirement changes ● Work like System integration packaging or Deployment. Those who want to practise Agile & Lean :)4
  5. 5. SCRUM The Framework Image Source : en.wikipedia.org/wiki/Jeff_Sutherland Image Source : en.wikipedia.org/wiki/Ken_Schwaber 5
  6. 6. Scrum 6
  7. 7. Scrum : The Artifacts & Output 7
  8. 8. A Visual Retreat Kanban 8
  9. 9. Kanban - History ● In 1940s, Toyota Production System under the leadership of Taichii Ohno came up with better engineering process for “Just In Time” delivery process called “KANBAN” ● KANBAN is a Japanese term meaning visual signal or card. Toyota engineers use the same for actual manufacturing work. Image Source : en.wikipedia.org/wiki/Taiichi_Ohno 9
  10. 10. Kanban journey to Software World ● A community was formed around 2007 with David J Anderson and few others as main stakeholders. ● Kanban today has its own success story to share in software world. Image Source : David J Anderson Twitter Handle 10
  11. 11. Why Visual Signal is important? ● Human brain processes visual information almost 60,000 times faster than textual information ● Almost 40% of all nerve fibers connected to brain linked to retina 11
  12. 12. 3 Core Properties of KANBAN 1. Visualize the workflow 2. Limit Work in Progress 3. Measure & Manage Work Flow ( Lead time / Cycle Time) 12
  13. 13. 1. Visualize the workflow ● Make the Work & its flow Visible ● How: Split in such a way so that it can be written on a postcard size paper 13
  14. 14. The Kanban Board - Sample 14
  15. 15. Kanban board with work items 15
  16. 16. 2. Limit Work In Progress (WIP) ● Each column in kanban represents WorkFlow State. ● Each workflow state is assigned an explicit limit ○ This limit is deduced by historical data / Availability basis - Improve Transparency 16
  17. 17. 2. Limit Work In Progress (WIP) 17
  18. 18. Measure & Manage Work Flow 18
  19. 19. ● Lead Time: ○ Time it takes from Requirement state to Done State. i.e it starts even before it comes to ToDo state. ● Cycle Time: ○ Time it takes from ToDo to Done State. ● The basic idea is to optimize the process so that the lead time is small. Measure the Cycle Time / Lead time : The Flow 19
  20. 20. Lead Time & Cycle Time 20
  21. 21. Kanban Pull System at Work 21
  22. 22. Kanban is a Pull System and not Push System PULL PUSH 22
  23. 23. Pull System at work - 1 23
  24. 24. Pull System at work - 2 24
  25. 25. Pull can also be based on Priority 25
  26. 26. Pull system Sub-States Ongoing & Done 26
  27. 27. Workflow Inner States 27
  28. 28. WIP Limit applied at Ongoing State 28
  29. 29. Each WorkFlow state also has D0D (Definition of Done) The DoD is not applicable for First & Last state i.e ToDo & Done 29
  30. 30. Advantages of Kanban ● Flow visibility ● Flow control ● Easy bottleneck identification ● Visible resource engagement ● Reduced need inventory storage. ● Reduced waste and scrap ● Total low cost 30
  31. 31. ScrumBan A fertile hybrid of Kanban & Scrum 31
  32. 32. Lets Do ScrumBan Taking Kanban As base reference 32
  33. 33. Step-1 : Start with a Kanban Board and add Product Backlog to it 33
  34. 34. The Product Backlog for Scrumban ● Product backlog of Scrumban is similar to that of Scrum and can be owned by a Product Owner. ● There is no (WIP) work in progress limit for Product Backlog. Let it come ● Can be prioritized, can be written in the form of User Stories/ Task ● Estimations can be done in Story Points / Man hours / T-shirt size of S/M/L 34
  35. 35. Release Planning : Release Product Backlog ● Use Product Backlog for Release Planning ● Planning should be done for upcoming releases ● Appropriate duration should be around 3 (+- ) months 35
  36. 36. Release Product Backlog 36
  37. 37. Scrumban: Release Product Backlog to TODO list via small planning session 37
  38. 38. Planning On Demand ● No Sprint planning is done to bring the items from Release Product Backlog to TODO list. ● Based on the capacity of TODO list, the items from Release Product Backlog will move to TODO list based on ○ Priority ○ Product Owner Choice ○ Business requirements ○ Technical Requirements ● Of course a small planning is required :) but it's not as elaborate as Sprint Planning.38
  39. 39. Scrumban: Flow of work items based on capacity 39
  40. 40. Scrumban: TODO list is Getting Empty : Call For Planning 40
  41. 41. Scrumban: Post Planning TODO list 41
  42. 42. Scrumban: Priority Changed.. Do Planning Again and change ToDo list Item 42
  43. 43. Scrumban: Having items in Done..Do Product Demo 43
  44. 44. 33 - 50% time spent already Spent : Prune Release Product Backlog ● Remove items which cannot be done in this release. 44
  45. 45. 66 - 75% time spent already Spent : Feature Freeze and start of Release Stabilization ● Post feature freeze, team shall not take any new items even if it’s there in ToDo list. The remaining item should go back to Product Backlog. ● Only stabilization related changes shall be allowed at this stage ● The Scrumban board shall be converted in Stabilization Board ● Stabilization board may or may not have WIP limit. All team memebers are working towards same goal 45
  46. 46. Stabilization Board 46
  47. 47. ScrumBan : Flow 47
  48. 48. Scaling ScrumBan 48
  49. 49. One Product Backlog can cater the need of multiple ScrumBan Teams49
  50. 50. ScrumBan Team size : As long as you can manage the number50
  51. 51. Distributed ScrumBan 51
  52. 52. Thank You @Agivetta 52 @AgileJaya trainings@agivetta.com

×