A few weeks ago I was in Boston to visit the Scrum.org offices and learn to teach the Professional Scrum with Kanban (PSK) training class co-taught by Steve Porter and Daniel Vacanti . This is a new Professional Scrum training course created by Ken Schwaber, Scrum.org, the Professional Scrum Trainer Community and Daniel Vacanti who helped to develop the Kanban Method for knowledge work. The new class was just announced by Ken & Scrum.org and includes a Kanban Guide for Scrum Teams that describes Kanban within the context of the Scrum Framework .
Also Check out:
TL;DR;
Now you can not only learn Scrum from those that created and maintain it, but you can add the Kanban Method from those that developed it as well. This new class show how to take the core practices of Kanban and implement them within the context of Professional Scrum without changing Scrum. I have already posted on how you can flow work across the Sprint boundary and that was a direct learning from me attending this class.

This is a 2 day class that also has an assessment that will earn you a PSK certification. I’ll be teaching this class in combination with Chris McDermott , founder of Lean Agile Scotland, to bring some much needed Kanban team experience to the class. While I have significant experience with Scrum teams, I have only worked with a few Kanban teams.
Kanban Guide for Scrum Teams
The Kanban community and the Scrum community have been working towards the same end for some time. Since the mission of Scrum.org is to improve the profession of software delivery then anything that we can do to make that a reality is within scope.
Scrum is more than 20 years old and has been trawling some baggage with it. Since the creation of the Scrum Guide Ken & Jeff have been working to remove much of that baggage from the definitive and agreed definition of Scrum and they have done a fantastic job. You will not find a mention of User Stories, Story Points, or Velocity in the Guide. They are not required to create an empirical control system.
I am not saying that they are bad, just that they are merely complimentary practices that you can choose to use or not. And let’s be super clear, if you have an amateur team then you should be starting with User Stories, Story Points, or Velocity, they are good practices. For more advanced teams that are already delivering working software on a regular cadence you might want to change those practices out for ones that focus more on flow, and you might also choose to use User Stories.
You can read the Kanban Guide for Scrum Teams which is an extension to the Scrum Framework. The Scrum Framework is closed for modification and open for extension which is reflected in this new guide. The new Kanban extension adds the following practices:
- Visualisation of the workflow
- Limiting WIP
- Active management of items in progress
- Inspecting and adapting workflow
In order to adapt your workflow to maximise the flow of value to your customers we also need to add the following metrics:
- WIP
- Cycle Time
- Work Item Age
- Throughput
This is an implementation of Kanban within the context of Scrum and as such has a definition that might differ from other Kanban implementations. Have a read of the guide and see if it appeals to you. For me the ideas of limiting WIP are ones that I have always encouraged teams to do and velocity always seamed like a broken metric.
Professional Scrum with Kanban Training
Working with Daniel Vacanti has opened my eyes to throughput and how it can replace velocity and help answer many of the questions that I have been asking for some time. His training and this class made so much sense that I don’t know why we have not yet adopted these practices in mainstream Scrum. I think that is time for a change.
If you are interested in the same revelations that I had you can read the Guide, and if you like what you see then attend a Professional Scrum with Kanban (PSK) training class with Chris McDermott and I.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Professional Kanban Trainer for Applying Professional Kanban
Learn about becoming a Professional Kanban Trainer, the Applying Professional Kanban course, certification process, and key Kanban …
My journey into Professional Scrum
Reflects on experiences with Professional Scrum, highlighting its impact on software development, team culture, training, and the challenges …
Professional Scrum is for everyone in your organisation
Explains how involving everyone in Professional Scrum training fosters organisational agility, breaks down silos, and empowers teams to …
Understanding the Power of Kanban in Scrum
Explains how integrating Kanban with Scrum boosts transparency, limits work in progress, and improves workflow, helping teams identify …
My journey with Kanban and why I actively recommend it to clients
Explains how adopting Kanban improves workflow, predictability, and transparency for any team or industry, offering practical insights and …
Unlocking the Power of Kanban: Transform Your Workflow with Data-Driven Insights
Learn how Kanban uses data-driven insights and probabilistic forecasting to optimise workflows, improve delivery, and enhance transparency …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …