The Kanban Method is a powerful approach to visualizing work items and workflow, creating a pull-based system without bottlenecks, and driving incremental improvements to your specific software development process, whatever it might be. This course gets you started with Kanban by describing its fundamentals and how to set up a Kanban system in your environment, and it shows you how to use Kanban metrics to analyze, deeply understand, and pursue changes to your development system that will make it work better for your team and for your business. Start with what you do now, agree as a team to evolve your system incrementally, and encourage acts of leadership that deeply involve participants at all levels.
Who Is This Course For?
This course is for software development teams that want to analyze, understand, and significantly improve the flow and throughput of their unique development system.
After completing this course, you will:
- Fully understand what Kanban is
- Appreciate the ways in which Kanban is richer, deeper, and more disciplined than you might currently think
- Be able to set up a Kanban system that reveals the realities of your development workflow
- Know how to use metrics to analyze, understand, and continuously improve your development system so that it works for the individuals using the system and the business
Limiting Work in Process (WIP); pull systems; using metrics in Kanban; continuous process improvement; limiting batch sizes; differentiating the Kanban method from a process visualization board; work process massaging; using the scientific method; measuring flow; work prioritization; importance of team buy-in and discipline; time management; chart discipline; using a Cumulative Flow Diagram (CFD); holding retrospectives in Kanban; cycle time; lead time; comparing and contrasting Kanban and Scrum; ways to avoid thrashing; the definition of “done”; daily standups; queue management strategies; process variation for different classes or work; SLAs; entry/exit criteria.
Scrum Overview covers Scrum implementation considerations including the role of feedback and the types of timelines used in Scrum, techniques for developing requirements in Scrum, Agile estimation techniques, and other implementation pitfalls. Agile Planning and Estimation contains sections designed specifically for the Scrum team and for the leadership team. Its multiple-audience approach leads to improved communication to and from the engineering and business sides of the company. Both teams gain insights by seeing the bigger picture, including the planning and estimation techniques used by each team.
Resources: Workbook, Section Guides, Knowledge Checks, Key Points, Practices Paper
Duration: 2.5-3.5 hours