Scrum.org PSK I: Using Kanban to Improve Flow in Scrum
The Professional Scrum with Kanban I certification is aimed at practitioners who already understand Scrum and want to improve how work flows through a Scrum Team. Scrum.org currently lists PSK I as a 45-question, 60-minute assessment with an 85% passing score. Training is recommended but not required, and the resulting credential is lifetime-valid without an annual renewal fee.
The important idea is that Kanban does not replace Scrum. PSK I tests whether a candidate can add flow practices to the existing Scrum framework without weakening Scrum’s accountabilities, events, artifacts, commitments, or empirical approach. That makes the assessment less about memorizing a second method and more about understanding how complementary practices expose waiting, overload, and unpredictability.
Within Scrum certifications, PSK I is unusually focused on the mechanics of flow. A practitioner who has already built a foundation through Professional Scrum Master I knowledge will recognize the Scrum rules, but PSK I asks what happens when a team begins managing work in progress, measuring cycle time, and making workflow policies explicit.
Scrum stays intact while Kanban makes flow more visible
One of the most important distinctions is that Scrum is still Scrum. The Product Owner remains accountable for maximizing value, the Scrum Master remains accountable for establishing Scrum as defined in the Scrum Guide, and Developers remain accountable for creating a usable Increment each Sprint. Adding Kanban does not create a new role, eliminate the Sprint, or turn the Product Backlog into a generic ticket queue.
Kanban contributes practices for understanding and improving flow. That means visualizing work, actively managing items in progress, limiting work in progress where appropriate, and inspecting flow metrics. These practices give the team more evidence about how work moves from started to finished. The result should be better decisions inside Scrum, not a parallel process that competes with it.
This distinction matters because many teams use a board while still pushing too much work into progress. A visual board alone does not create flow. A useful Scrum board should expose the real state of work and help the team see queues, blocked items, and aging work early enough to act.
A Definition of Workflow turns hidden operating rules into explicit policy
Teams often have unwritten rules about when work is considered started, what states it passes through, what qualifies it to move, and when it is finished. Those assumptions become a source of friction when different people apply different definitions. A Definition of Workflow makes those policies inspectable. It can describe work-item states, how work moves, work-in-progress controls, and a Service Level Expectation for how long work is expected to take.
Explicit policies are valuable because they reduce arguments that are really caused by ambiguity. If an item cannot enter testing until certain evidence exists, that rule should be visible. If blocked work should receive priority before new work is pulled, that should be understood by the team. The policy is not meant to become bureaucracy; it is a shared model that can be inspected and changed when evidence shows a better approach.
Work-in-progress limits change behavior, not just board appearance
Limiting work in progress is one of the strongest ways to expose a system problem. When a column reaches its limit, the team cannot simply start more work and hide the constraint. People have to finish, swarm, remove a blockage, or reconsider how work is entering the system. This creates pressure to solve the cause of delay rather than increase the amount of partially completed work.
A WIP limit is not a productivity quota. A lower number is not automatically better, and a team should not spend energy gaming a number that no longer reflects its workflow. The practical question is whether the control encourages finishing and improves flow while preserving quality. If a limit is constantly broken, the team should learn why instead of treating the violation as a moral failure.
This is also why Scrumban-style flow ideas can be informative without changing the PSK I principle: Kanban practices should serve the Scrum Team’s ability to deliver value, not turn the team into a collection of individually optimized specialists.
Flow metrics answer different questions about delivery
PSK I candidates should understand the four core flow measures commonly used with Scrum and Kanban: work in progress, cycle time, work item age, and throughput. They are related but not interchangeable. Work in progress tells the team how much has started but not finished. Cycle time measures elapsed time for completed work. Work item age shows how long an in-progress item has been active. Throughput counts completed work over a period.
The strongest use of these measures is diagnostic. An aging item may indicate a dependency, unclear requirement, unavailable environment, or oversized slice of work. Rising WIP with flat throughput often signals that starting more work is not creating more value. A cycle-time distribution can reveal variability that an average hides. The exam can therefore test whether a candidate knows which metric helps answer a particular flow question.
The metrics become more useful when the team studies them together rather than turning one number into a target. A throughput increase can be encouraging, but if work item age is also increasing it may mean newer, easier items are finishing while older work remains stuck. Falling WIP can improve focus, but a sudden drop caused by reclassifying unfinished work tells the team nothing useful. The purpose is to understand the behavior of the workflow. A team that can explain why a metric moved is in a better position to design an experiment than a team that merely celebrates a favorable chart.
Candidates should also recognize the difference between a point estimate and a distribution. Two periods can have the same average cycle time while one is much more variable and therefore harder to forecast. Looking at the spread of completed-item times, the age of current work, and the shape of queues helps the Scrum Team ask better questions about predictability. Kanban evidence is most valuable when it changes a decision about finishing, splitting work, removing a constraint, or adjusting an explicit policy.
Service Level Expectations support realistic forecasting
A Service Level Expectation is not a guaranteed deadline for every item. It is a forecast, usually expressed as a time threshold with an associated probability, that helps a team and its stakeholders understand what is reasonably likely based on observed history. A useful SLE makes expectations transparent without pretending that complex work is deterministic.
This changes the conversation around estimates. A team can use historical flow to discuss how likely work is to finish within a given time instead of converting every item into a promise. Traditional Agile estimation techniques may still be useful, but PSK I expects candidates to recognize that flow data can support forecasting directly, especially when the workflow and work-item types are stable enough for the history to be meaningful.
Scrum events become better when flow evidence is brought into them
Kanban practices do not add replacement ceremonies. They improve the evidence available during existing Scrum events. In Sprint Planning, the team can consider WIP, flow history, and current aging work when discussing what is realistic. During the Daily Scrum, Developers can focus on how work is moving toward the Sprint Goal rather than giving individual status reports. An old item that is not advancing may deserve more attention than a newly started item.
The Sprint Review can use outcome and delivery evidence to help stakeholders understand what was learned and what became usable. The Retrospective can look for recurring queues, policy problems, or bottlenecks and define an experiment to improve them. That turns Agile retrospectives into a place for system learning rather than a repeating list of feelings and action items.
Product decisions still determine what should flow through the system
Flow efficiency is not valuable if the team is efficiently finishing low-value work. The Product Owner still orders the Product Backlog and connects near-term choices to the Product Goal. Kanban can improve delivery information, but it cannot decide which outcome matters or which stakeholder problem deserves attention.
The relationship between the Product Backlog and Sprint Backlog remains important. The Product Backlog is an emergent source of work for the product, while the Sprint Backlog is the Developers’ plan for the Sprint. Flow practices should help Developers manage selected work effectively without turning the Sprint Backlog into a centrally assigned task list.
Preparation should focus on interpreting scenarios, not collecting definitions
PSK I questions often require a candidate to reason from Scrum and Kanban principles. A good study plan therefore starts with the current Scrum Guide, the Kanban Guide for Scrum Teams, and the Scrum.org PSK subject areas. Candidates should be able to explain what changes when Kanban is introduced and, just as importantly, what must not change.
Practice should include scenarios: a team has too many aging items, a WIP limit is repeatedly exceeded, throughput is stable but cycle time is rising, or stakeholders are treating the SLE as a hard commitment. For each scenario, identify the evidence, the likely system issue, and the next empirical action. The point is not to memorize one universal response but to choose an action that improves transparency and learning.
PSK I is most valuable when the candidate can connect metrics to behavior. The certification is not about making a board look sophisticated. It is about using visible workflow, explicit policies, flow measures, and empiricism to help a Scrum Team finish valuable work with greater focus and predictability.