Recommended
More Related Content
Similar to ACG SL - Kanban.pdf
Similar to ACG SL - Kanban.pdf (20)
Recently uploaded
Recently uploaded (20)
ACG SL - Kanban.pdf
- 1. Bringing Kanban to Life With Atlassian JIRA Session for Atlassian Community Group Sri Lanka Session by Rumesh Wijetunge Agile Coach, Co-chair RSG Sri Lanka, Founder APPTRA LTC
- 2. A bit about me 2 www.linkedin.com/in/rumeshwijetunge rumesh.wijetunge chanakarumesh@gmail.com www.facebook.com/chanakarumeshw RUMESH WIJETUNGE MBA (PIM-USJ), BSc (Hons.), CIM (UK), CBAP® , CSP® , CSM® , CSPO® , SAFE® SPC, SAFE® SA, SAFE® SM, PMP® , PMI-ACP® , PMI-PBA® , PRINCE2® (Foundation), ITIL® (Foundation), Management 3.0 Facilitator, NLP Practitioner § Director | Chief Executive Officer – APPTRA Holdings (Pvt.) Ltd. § Enterprise Agile Coach – Wiley Global Technologies Ltd. § 17+ years of industry experience § 12+ years as a Business Consultant, Agile Delivery Manager § 5+ years of C-Level experience § 8+ years of experience as a lecturer, trainer and coach § Certified Business Analysis Professional (CBAP®) & PMI Professional in Business Analysis (PMI-PBA®) § Certified SAFe Program Consultant (SPC), Certified Scrum Professional (CSP), IC Agile Certified Coach & Management 3.0 Facilitator § Certified Project Management Professional & PRINCE2 (Foundation) level § Trainer for IIBA® certifications, PMI® Professional in Business Analysis certification and the BCS Professional in Business Analysis certification § Trainer, Consultant & Coach for SAFe® (Scaled Agile), Agile (Scrum, Kanban), Management 3.0 and Solution Design & Design Thinking § Former President & VP Events of IIBA® Sri Lanka Chapter
- 3. Quick Intro to Kanban • A Work Management System • Designed to Visualize WIP and Maximize Efficiency of Flow • 看板 – Sign Board, Visual Signal, Card you can see • Popular framework to implement Agile and DevOps SW Development • Dates back more than 50 years to Toyota – Or even before that! • JIT principles applied to SW teams by matching amount of WIP to team’s capacity
- 4. 6 Kanban Practices 1. Visualize (the work, the workflow, and the business risks) 2. Limit Work-In-Progress (WIP) 3. Manage Flow 4. Make Policies Explicit 5. Implement Feedback Loops 6. Improve Collaboratively, Evolve Experimentally
- 5. 1. VISUALIZE Visualize the workflow Visualize the work
- 6. To Do Ongoing Done Simplest Workflow
- 7. Backlog To Do Design Development Testing Verification Done Define the workflow based on the work you do
- 8. Backlog To Do Development Testing Verification Done Ongoing Done Ongoing Done Add Buffer Statuses
- 9. Backlog To Do Development Testing Verification Done Ongoing Done Ongoing Done Standard Expedite Fixed Date Impediments Defining Classes of Service by Adding Swimlanes
- 10. Assignee To Do Development Testing Verification Done Ongoing Done Ongoing Done Rumesh Buwaneka Chris Swimlanes by Assignee, Project, Product, etc.
- 12. 2. LIMIT WORK-IN-PROGRESS (WIP)
- 13. To Do Ongoing 3 Done #001 Develop X #002 Design componen t #004 Do PoC ABC #005 Develop M H M H L #007 Test G M #008 Test L L #003 Fix bug XYZ #007 Develop G H M #009 Develop O M WIP Limits Kanban System Members are assigned work Maximum of 3 ongoing
- 14. To Do Ongoing Min = 3 Max = 8 Done #001 Develop X #002 Design componen t #004 Do PoC ABC #005 Develop M H M H L #007 Test G M #008 Test L L #003 Fix bug XYZ #007 Develop G H M #009 Develop O M WIP Limits (Min & Max values)
- 15. To Do Analysis 2 Development Testing Verification 10 Done Ongoing 3 Done 5 Ongoing 4 Done 6 WIP Limits for Buffer States
- 16. 3. MAKE POLICIES EXPLICIT High Level Policies Step Level Policies
- 17. Policies Everything in Backlog first, Board works based on workflow stage level policies New Requests have date/time, title, name of requestor by colour with SLA defined Pull from Ready to Work & not the Backlog If task takes 15 mins or less – do not add on board Only dev team can modify ready to work and WIP Weekly meetings – Backlog moves to Ready to work and Ready to work moves to Backlog How does the board work? What is written on a ticket? What goes on the board? Who can modify? Cadence High Level Policies
- 18. To Do Analysis 5 Development Testing Verification 10 Done Ongoing 3 Done 5 Ongoing 4 Done 7 Requirement is accepted and prototype is finalized Coding is done and code review for the item is completed Policies J K L M J J N Testing is done and defects fixed Step Level Policies – Pull Criteria
- 19. 4. MANAGE THE FLOW CONTINUOUS FLOW THROUGH A ‘PULL SYSTEM’
- 20. To Do Analysis 5 Development 3 Testing Verification 10 Done ∞ Ongoing Done Ongoing 5 Done 5 J K L M J J J J N J P J J J Z O R H I G F E D B C A Kanban System in Motion Requirement is accepted and prototype is finalized Coding is done and code review for the item is completed Testing is done and defects fixed
- 21. To Do Analysis 5 Development 3 Testing Verification 10 Done ∞ Ongoing Done Ongoing 5 Done 5 J K L M J J J J N J P J J J Z O R H I G F E D B C A There is free capacity here Kanban System in Motion Are Policies Met? Requirement is accepted and prototype is finalized Coding is done and code review for the item is completed Testing is done and defects fixed
- 22. To Do Analysis 5 Development 3 Testing Verification 10 Done ∞ Ongoing Done Ongoing 5 Done 5 J K L M J J J J N J P J J J Z O R H I G F E D B C A Pull Kanban System in Motion
- 23. To Do Analysis 5 Development 3 Testing Verification 10 Done ∞ Ongoing Done Ongoing 5 Done 5 J K L M J J J J N J P J J J Z O R H I G F E D B C A Kanban System in Motion
- 24. 6. IMPROVE COLLABORATIVELY, EVOLVE EXPERIMENTALLY
- 25. Throughput The number of items completed within a particular time period
- 26. Lead Time and Cycle Time Lead Time Time it takes for a ticket to move from ‘To-Do’ to ‘Done’ state. Cycle Time Time that a ticket spends in ‘In Progress’ states. This is the time where value addition happens.
- 28. Thank You! Go forth and live Kanban with Atlassian JIRA