Let's Do the Kanban
Total Page:16
File Type:pdf, Size:1020Kb
Let’s Do the Kanban Presented by: Linda Westfall Copyright © 1999-2021 Westfall Team, Inc. All Rights Reserved. Logistics • Attendees are on mute • Type your comments & questions into the Question area – Linda will answer questions during & at the end of the webinar Logistics • You will receive an email tomorrow: • Which is verification of attendance for RUs, PUs, etc. • Telling you how to access the recording – please feel free to share this recording with your colleagues The Questions? What is Kanban? How do we Create a Kanban Board? What is a WIP Limit? How does a Team use Kanban to Track Flow? What Is Kanban? Kan: Visual ban: Card or board Kanban: Sign, signboard, signal card, billboard, token Origins of Kanban? Origins in Lean – Toyota Production System as a tool to help enable just-in-time delivery process. • Based on the Lean mindset • Uses Kanban boards to visualize: • Work items & their status • Work flow Kanban system: A system that uses tokens as a mechanism for managing the flow of the process. [Stuart-17] Benefits of Kanban Benefits of Kanban include: • Kanban focuses on optimizing quality & continuous improvement • Kanban manages process flow, rather than time-boxes, with a step towards continuous delivery • Kanban limits work-in-process (WIP) • Kanban is a pull system Benefits of Kanban • Kanban drives the reductions of waste • Minimizes wait time • Matches supply with demand • Kanban highlights team performance • Kanban emphasizes metrics & measurement Kanban Core Practices The core practices of Kanban include: • Visualize workflow • Limit work-in-process (WIP) • Make process policies explicit • Manage flow • Implement feedback loops • Improve collaboratively & evolve experimentally Creating a Kanban Board – 1st Example Design Implement Test A Kanban board Backlog Ready UAT Complete can be used to Doing Done Doing Done Doing Done visualize workflow. Start with existing process. Software Development Example. Creating a Kanban Board – 2nd Example CCB Debug Correct Test Backlog Ready UAT Complete Problem Report Doing Done Doing Done Doing Done Doing Done Correction Example. Limit Work-In-Process (WIP) Ready Design (3) Implement (5) Test (3) UAT WIP limits are Backlog Complete established (4) Doing Done Doing Done Doing Done (1) based on capacity of the people doing the work. Make Process Policies Explicit What does it Ready Design (3) Implement (5) Test (3) UAT Backlog Complete mean to be done (4) Doing Done Doing DoneDone Test:Doing Done (1) • Test Coverage = 100% with each process step? • Executed > 95% • Passed > 95% • No critical defects • Any major defects have work-arounds Documented in or near the Kanban board. Process Policies (exit criteria) Start of Project A Kanban board can be used to visualize workflow. At the start of Ready Design (3) Implement (5) Test (3) UAT Backlog Complete the project (4) Doing Done Doing Done Doing Done (1) everything is in the Backlog. During the Backlog Refinement Meeting – Work items are pulled Process Policies (exit criteria) into Ready until WIP limit is reached. Start of Project Those work items Ready Design (3) Implement (5) Test (3) UAT can move on Backlog Complete (4) Doing Done Doing Done Doing Done (1) into Design Doing until WIP is reached. Other work items are added to the Product Backlog in priority order as Process Policies (exit criteria) they emerge. Managing Flow Through Ongoing Development As work items Ready Design (3) Implement (5) Test (3) UAT finish design Backlog Complete (4) Doing Done Doing Done Doing Done (1) they are moved to Design Done & the next Ready work items are pulled to Design Ready. Process Policies (exit criteria) Managing Flow Through Ongoing Development And since the Ready Design (3) Implement (5) Test (3) UAT Implement WIP Backlog Complete (4) Doing Done Doing Done Doing Done (1) limit has not been reached the Done Design work item can be pulled into Implementation. Process Policies (exit criteria) Managing Flow Through Ongoing Development When work items Ready Design (3) Implement (5) Test (3) UAT in the Ready Backlog Complete (4) Doing Done Doing Done Doing Done (1) column gets low enough, another Backlog Refinement Meeting is held to fill it back up. Process Policies (exit criteria) Managing Flow Through Ongoing Development And so on ... Ready Design (3) Implement (5) Test (3) UAT Backlog Complete (4) Doing Done Doing Done Doing Done (1) Process Policies (exit criteria) Remember – Kanban Uses a Pull System Work items can Ready Design (3) Implement (5) Test (3) UAT only be pulled Backlog Complete (4) Doing Done Doing Done Doing Done (1) into an empty slot based on WIP limits. Process Policies (e xit criteria) Kanban Uses a Pull System Work items can Ready Design (3) Implement (5) Test (3) UAT only be pulled Backlog Complete (4) Doing Done Doing Done Doing Done (1) into an empty slot based on WIP limits. Process Policies (e xit criteria) Answering the Questions? What is Kanban? How do we Create a Kanban Board? What is a WIP Limit? How does a Team use Kanban to Track Flow? Questions? Upcoming Webinar from the Software Excellence Academy April 2021 topic: Agile Methods and Frameworks • 4/28/2021 – Incorporating the Software Quality Process in DevOps presented by Charles D. Carson May 3021 topic: Software Audits • 5/5/2021 – Audit Roles & Responsibilities presented by Linda Westfall • 5/12/2021 – How to Implement Different Audit Strategies presented by Linda Westfall • 5/19/2021 – TBD Webinar recordings: https://westfallteam.mykajabi.com/webinars Contact Information email: [email protected] phone: 972-867-1172 Westfall Team, Inc.: westfallteam.com Software Excellence Academy: https://westfallteam.mykajabi.com.