Resources

The Professional Scrum with Kanban (PSK) course has now been out for more than 6 months at Scrum.org. As one of the first few trainers who wanted to teach this course when it came out, I find it is a great way to combine the Scrum framework with Kanban as a strategy to deliver value to your customer.

Hello great people of the world. It’s been a while since I wrote a blog post here. This time I want to share my experience working with Development Teams and a Product Owner at iPrice group who upgraded the way they ran their Sprint Planning.

At one point or another in our lives we have all experienced a long queue, stuck in a car on the motorway, sat on a train waiting for an open platform. My favorite memories stretch back to that line for the lunch at primary school where it was cake and custard day!

In this video, Scrum.org Professional Scrum Trainer and Professional Scrum with Kanban (PSK) course steward Yuval Yeret talks about the PSK course, helping viewers to understand more about the structure of the class and what they will learn when attending. 

One of the key Kanban practices we discuss in the Kanban Guide for Scrum Teams is Limiting Work in Process. 

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. Heck, many of the companies I meet these days still work that way.

Bottom line - Toyota Improvement and Coaching Kata is the perfect partner for flow-based retrospectives.

Bottom line - WiP limits must be applied to improve flow of the delivery of value. It's a key lever to improve the performance of Professional Scrum Teams, and it's required by the Kanban Guide for Scrum.

One of the new concepts we introduce in the Kanban Guide for Scrum Teams is the Service Level Expectation, defined as: An SLE forecasts how long it should take a given item to flow from start to finish within your workflow.

One of the key Kanban practices is Limiting Work in Progress. If you want to be pedantic, actually what this practice aims for is Reducing and stabilizing Work in Progress. This improves flow, provides predictability, and is actually even more important for creating a pull-based Kanban system than visualizing your workflow using a Kanban board. I worked with several clients that limited their WIP but didn't use Kanban boards. One could argue that maybe this practice deserves to be first in the list of Kanban practices, ahead of Visualization.

In the Kanban Guide for Scrum Teams and the Professional Scrum with Kanban workshop, we introduce 4 key flow metrics that we believe Scrum teams can use to improve their flow.

It’s been so exciting to hear so much positive feedback and interest in the new Scrum.org Kanban Guide for Scrum Teams and the accompa

Is it possible to use Scrum with Kanban? After a year of exploring the idea and working out the details, our answer is yes. Get ready to make your team stronger and more effective.

Today we announced a new class Professional Scrum With Kanban. This class helps teams practicing Scrum to apply the practices of Kanban without breaking Scrum. It shows how visualization and flow are great partners in delivering Done software and how Scrum with Kanban helps teams become more professional.

There is no need to choose between Scrum and Kanban, but certain myths have led some to believe this is the case. It’s time to debunk them once and for all.

Una de las cuestiones que se plantean habitualmente en organizaciones, equipos y Agile Coaches, es el uso de un método que permita organizar el trabajo de forma ágil.

Several of us in the Kanban and Scrum community got together recently to build a bridge between Scrum and Kanban. We are writing a series of blog posts looking at this bridge from different perspectives. In this post, we present a primer on the Scrum Framework from a Kanban perspective.

Several of us in the Kanban and Scrum community got together recently to build a bridge between Scrum and Kanban. We are writing a series of blog posts looking at this bridge from different perspectives.

Does this headline make you cringe or cheer? Scrum.org’s Steve Porter and ActionableAgile’s Daniel Vacanti weigh in on whether we should blend these two approaches.

When all you have is a hammer, everything looks like a nail! Huh? I don’t know; it’s something my father always said.