15 Topics
5 Days
75 Sessions
Programme Overview
Training Description
Who Should Attend
- Scrum Developers and Agile Team Members
- Project and Product Managers
- Delivery Managers
- Business Analysts
- Agile Transformation Professionals
- Team Leaders and Managers
- Software Development and IT Professionals
- Professionals working in Lean-Agile environments
- Organizations seeking to improve flow and predictability within Scrum teams
Session Objectives
- Understand how to apply Kanban practices to the Scrum framework
- Learn to visualize the flow of work for enhanced transparency
- Discover how to limit work in progress to improve focus
- Use flow metrics to forecast and manage delivery
- Identify and remove bottlenecks and impediments to workflow
- Learn how to improve team predictability and efficiency
- Understand the role of Kanban in Scrum events
- Explore the importance of continuous improvement in PSK
- Gain a deeper understanding of the PSK principles and practices
About the Course
The Flow & Focus: Professional Scrum with Kanban (PSK) Training Course provides participants with practical knowledge and techniques for integrating Kanban practices with Scrum to improve workflow, transparency, predictability, and value delivery.The course explores how Scrum teams can use Kanban principles to visualize work, manage work in progress, identify bottlenecks, improve flow, and make more informed decisions without changing the fundamental Scrum framework. Participants will learn how to apply flow metrics and Kanban practices to enhance team effectiveness and continuously improve product delivery.
Curriculum & Topics
15 Topics | 75 Sessions
-
Workshop 1.1:
A brief review of the Scrum framework
-
Workshop 1.2:
The purpose of Scrum's roles, events, and artifacts
-
Workshop 1.3:
Understanding the Scrum values and their importance
-
Workshop 1.4:
How Scrum provides a framework for complexity
-
Workshop 1.5:
The role of self-managing teams
-
Workshop 2.1:
Understanding the four core Kanban principles
-
Workshop 2.2:
The importance of evolutionary change
-
Workshop 2.3:
Respecting current roles and responsibilities
-
Workshop 2.4:
The value of visualizing workflow
-
Workshop 2.5:
The concept of continuous improvement
-
Workshop 3.1:
How to create a team Kanban board
-
Workshop 3.2:
Identifying different types of work and their states
-
Workshop 3.3:
The importance of a shared understanding of the workflow
-
Workshop 3.4:
Using swim lanes to manage different work items
-
Workshop 3.5:
The value of a clear Definition of Done
-
Workshop 4.1:
Why limiting WIP is crucial for flow
-
Workshop 4.2:
The impact of multitasking on efficiency
-
Workshop 4.3:
Different strategies for setting WIP limits
-
Workshop 4.4:
How WIP limits create pull-based systems
-
Workshop 4.5:
The relationship between WIP and lead time
-
Workshop 5.1:
The importance of continuous flow
-
Workshop 5.2:
Understanding blocked work and how to resolve it
-
Workshop 5.3:
The concept of a pull system
-
Workshop 5.4:
Measuring flow metrics like throughput and lead time
-
Workshop 5.5:
Using flow to identify system bottlenecks
-
Workshop 6.1:
How to use the board in Sprint Planning
-
Workshop 6.2:
Visualizing the Sprint Goal and Product Backlog
-
Workshop 6.3:
The role of the Kanban board in the Daily Scrum
-
Workshop 6.4:
How to use flow metrics in the Sprint Review
-
Workshop 6.5:
Using the board to inform the Sprint Retrospective
-
Workshop 7.1:
The Scrum Master as a flow master
-
Workshop 7.2:
Coaching the team on Kanban practices
-
Workshop 7.3:
Facilitating the use of flow metrics
-
Workshop 7.4:
Helping the team identify and resolve flow issues
-
Workshop 7.5:
Advocating for continuous improvement
-
Workshop 8.1:
Using flow metrics to make better forecasts
-
Workshop 8.2:
How the Kanban board aids in Product Backlog management
-
Workshop 8.3:
The importance of ordering items for continuous flow
-
Workshop 8.4:
Communicating flow and predictability to stakeholders
-
Workshop 8.5:
Collaborating with the team on WIP limits
-
Workshop 9.1:
Understanding key flow metrics
-
Workshop 9.2:
Calculating throughput and cycle time
-
Workshop 9.3:
Using Cumulative Flow Diagrams (CFD)
-
Workshop 9.4:
The importance of Little's Law
-
Workshop 9.5:
Making data-driven decisions
-
Workshop 10.1:
Using historical data for forecasting
-
Workshop 10.2:
The difference between forecasting and committing
-
Workshop 10.3:
How to create reliable forecasts
-
Workshop 10.4:
The impact of WIP on predictability
-
Workshop 10.5:
Communicating forecasts to stakeholders
-
Workshop 11.1:
The role of retrospectives in improving flow
-
Workshop 11.2:
Using the Kanban board to identify improvement areas
-
Workshop 11.3:
Experimenting with different workflow designs
-
Workshop 11.4:
How to adjust WIP limits over time
-
Workshop 11.5:
The importance of a learning culture
-
Workshop 12.1:
Building a culture of transparency
-
Workshop 12.2:
The importance of collaboration and cross-functionality
-
Workshop 12.3:
The role of a shared understanding of the workflow
-
Workshop 12.4:
Encouraging team ownership of the process
-
Workshop 12.5:
Fostering a blameless culture
-
Workshop 13.1:
Applying PSK in large-scale product development
-
Workshop 13.2:
The challenges of multiple teams using Kanban with Scrum
-
Workshop 13.3:
The importance of shared workflow visualization
-
Workshop 13.4:
Scaling WIP limits across teams
-
Workshop 13.5:
The role of coordination in a scaled environment
-
Workshop 14.1:
Hands-on exercises and simulations
-
Workshop 14.2:
Analyzing real-world examples of PSK adoption
-
Workshop 14.3:
Discussing challenges and successes
-
Workshop 14.4:
Collaborative problem-solving sessions
-
Workshop 14.5:
Applying course concepts to your own context
-
Workshop 15.1:
Addressing resistance to change
-
Workshop 15.2:
Avoiding common mistakes in implementation
-
Workshop 15.3:
The dangers of "Kanban-izing" without purpose
-
Workshop 15.4:
Ensuring the Scrum framework is not lost
-
Workshop 15.5:
Troubleshooting common flow issues
