Professional Scrum with Kanban (PSK)

RM3,500.00 RM3,710.00 (after 6% SST)

Course Code: PSK

Course Duration: 2 days




Professional Scrum with Kanban (PSK) is a 2-day course that teaches Scrum practitioners how to apply Kanban practices to their work. Scrum is the defacto standard for how Agile teams work.  Scrum exists only in its entirety and functions well as a container for other techniques and practices.  Scrum Teams keep improving how they work, based on what they learn by inspecting and adapting on an ongoing basis. Through theory, case studies, and hands-on exercises, participants will understand the importance of transparency and flow as it pertains to the Scrum framework. Scrum.org have worked with Daniel Vacanti in the creation of this course. In 2007 Daniel helped to develop the Kanban Method for knowledge work. He managed the world’s first project implementation of Kanban that year.



The Professional Scrum with Kanban course is for anyone doing Scrum. It is particularly beneficial for those people within an organization who use Scrum to deliver products to market including Product Owners, Development Team Members and Scrum Masters.



All participants completing the Professional Scrum with Kanban course will receive a password to attempt the Professional Scrum with Kanban I (PSK I) assessment. This assessment is only available to students of the class currently. The test is currently under construction and will be available soon. The industry-recognized PSK I certification requires a minimum passing score of 85%. If you attempt the PSK I assessment within 14 days of receiving the password and do not score at least 85%, you will be granted a 2nd attempt at no additional cost.


What is included in the price?

The price includes two days of training, course materials and the opportunity to take the PSK assessment and certification after the course. Students attending Scrum.org training classes learn the importance of inspection, adaptation, and fast feedback cycles. 


Duration: 2 Day, Instructor-led


  • Gain a clear understanding of how flow works within the context of Scrum
  • Be introduced to Kanban practices that Scrum Teams can adopt to help improve their effectiveness and efficiency
  • Understand how to effectively use the appropriate Kanban practices without changing
  • Learn a practical approach to improving transparency and visibility of work

Training Content

Dispelling Common Myths – Myths are like Kanban is for support work, Kanban is alternative to Scrum, Kanban is for complicated domain etc. Will see how Kanban can get together with Scrum to maximize benefit of Scrum.


Definition of Workflow – Optimizing flow requires defining what flow means in a Scrum context. Each Scrum Team must create its definition of “Workflow” containing the following elements:

  • Defined points at which the Scrum Team considers work to have started and to have finished.
  • A definition of the individual units of customer value that are flowing through the Scrum Team’s system (most likely Product Backlog Items (PBIs)).
  • A definition of the workflow states that the PBIs flow through from start to finish (of which there must be at least one active state).
  • Explicit policies about how work flows through each state (which may include items from a Scrum Team’s definition of “Done” and pull policies between stages).
  • A definition of how Work in Progress (WIP) will be limited.
  • A set Service Level Expectation (SLE) that communicates a forecast of how long it should take to complete work items.


Understanding Professional Scrum – First, a quick review of a key tenet of The Scrum Guide: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.

Scrum mandates that the Sprint Backlog be transparent, but it provides limited guidance on how to accomplish this. Nor does it define how to achieve explicit transparency to the flow of work into the Product Backlog, from the Product Backlog into the Sprint Backlog, and whatever happens to the work after it makes it into a “Done” increment. This is where Kanban can help. By visualizing work in new ways, a Scrum Team can apply the set of practices laid out in this guide to more effectively optimize value delivery. These practices borrow from and build upon the principles of lean thinking, product development flow, and queuing theory.


Kanban Theory, Principles and Practices – Scrum Teams achieve flow optimization by using the following four practices:

  • Visualization of the workflow
  • Limiting WIP
  • Active management of work items in progress
  • Inspecting and adapting their definition of “Workflow”


Kanban in Practice – Visualization using the Kanban board is the way the Scrum Team makes its workflow transparent. The board’s presentation should prompt the right conversations at the right time and proactively suggest opportunities for improvement.

Work in Progress (WIP) refers to the work items the Scrum Team has started but has not yet finished. Scrum Teams using Kanban must explicitly control these in-progress work items from the time they consider them “started” until the time they consider them “finished.” That control is usually represented as a number or numbers on a Kanban board. Those numbers are called “WIP Limits.”

Limiting WIP is a necessary component to achieve flow, but it alone is not sufficient. The third practice to establish flow is the active management of work items in progress. Active management can take several forms, including but not limited to the following:

  • Responding quickly to blocked work items.
  • Making sure that work items are only pulled into the workflow at about the same rate that they leave the workflow.
  • Ensuring work items aren’t left to age unnecessarily and are completed according to an established SLE.
  • Unclogging work that piles up in a column or columns.


Scrum with Kanban – Kanban in a Scrum context does not require any additional events to those outlined in The Scrum Guide. However, using a flow-based perspective can enhance Scrum events.