Professional Scrum with Kanban (PSK I)

For IT leaders: Many Scrum teams hit their Sprint ceremonies but still struggle with unpredictable delivery, work that stalls mid-Sprint, and forecasts stakeholders don't trust. This course gives your team a shared way to see, measure, and manage the flow of work inside the Scrum framework they already use.

Role fit: Assign this course to Scrum Masters, Product Owners, Team Leads, and IT Practitioners on Scrum teams, including infrastructure, DevOps, and service teams that handle a steady stream of incoming work. It does not require replacing Scrum. It shows how Kanban practices complement it, which reduces change-management friction.

Time investment: Expect about 9.5 hours of video per learner across 11 skills. It starts with Scrum foundations and ends with dedicated PSK I assessment prep. Learners new to Scrum should start at the beginning. Experienced Scrum Masters can move faster through the opening skills.

Change management: Teams get the most value when they go through the course together. Flow practices such as explicit policies and WIP limits are team agreements, not individual habits.

How CBT Nuggets supports the rollout: Use Playlists to sequence this course alongside PSM I or PSPO I. Use Team Reporting to track progress and certification readiness across the group.

IT teams complete this training to turn a board that only lists tasks into a system they can actively manage and forecast from. The course moves in order through visualizing the workflow, setting explicit policies and WIP limits, measuring flow, and using that data in Sprint Planning, Reviews, and Retrospectives.

Consider a team where tickets routinely sit "in progress" for weeks. After this training, the team can define what each workflow stage means and cap work in progress. It can also set a service level expectation and flag aging items before they become escalations.

• More predictable delivery: Teams forecast from their own flow data instead of gut-feel estimates, so stakeholders get commitments they can plan around.
• Fewer stalled work items: Tracking work item age against a service level expectation surfaces blocked work early.
• Less context switching: WIP limits and pull-based work help teams finish work before starting more.
• Better Scrum events: Flow analytics give Sprint Reviews and Retrospectives concrete evidence for improvement discussions.
• Certification readiness: A dedicated assessment-prep skill prepares practitioners to sit the PSK I exam.

Knowledge

• How the Scrum framework's accountabilities, events, and artifacts provide the foundation for flow-based work
• How Kanban practices complement Scrum without replacing it
• The role of explicit policies, WIP limits, and pull in defining a team's workflow
• The four flow metrics: WIP, cycle time, work item age, and throughput
• What service level expectations are and why aging work signals risk
• How flow data supports forecasting and inspection in Scrum events

Ability

• Visualize a team's workflow and define clear start and finish points
• Set and adjust WIP limits and explicit policies as team agreements
• Track work item age and act on items at risk of missing a service level expectation
• Read flow analytics to spot bottlenecks and trends
• Use flow data to forecast delivery and inform Sprint Planning, Reviews, and Retrospectives
• Prepare for and attempt the PSK I assessment