All Practice Exams

100+ Free PSK II Practice Questions

Pass your Professional Scrum with Kanban II (PSK II) exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately
~60-70% Pass Rate
100+ Questions
100% Free
1 / 100
Question 1
Score: 0/0

What is the precise distinction between Cycle Time and Work Item Age?

A
B
C
D
to track
2026 Statistics

Key Facts: PSK II Exam

85%

Passing Score

Scrum.org

30 Qs

Exam Questions

60 minutes

$250

Exam Fee

Per attempt

Lifetime

Validity

No renewal needed

Partial

Credit Format

Some questions

PSK II is a 60-minute, 30-question online assessment from Scrum.org requiring 85% to pass ($250 per attempt). The exam goes deeper than PSK I: distinguishing cycle time, work item age, lead time and throughput; interpreting Cumulative Flow Diagrams (line spread = WIP, slope = throughput, gaps = bottlenecks); reading control charts for special-cause variation; running Monte Carlo simulations against historical throughput to produce 50/85/95% confidence forecasts; Right-Sizing work items; setting explicit policies and WIP limits per stage; applying Theory of Constraints to bottlenecks; and scaling flow across multiple Scrum Teams in Nexus. Lifetime certification — no renewal.

Sample PSK II Practice Questions

Try these sample questions to test your PSK II exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1What is the precise distinction between Cycle Time and Work Item Age?
A.They are synonyms for the same metric
B.Cycle Time measures finished items (start to finish); Work Item Age measures the elapsed time of items still in progress
C.Cycle Time includes queue time; Work Item Age does not
D.Work Item Age is for epics; Cycle Time is for stories
Explanation: Cycle Time is the elapsed time from when a work item started to when it finished — a backward-looking metric calculated only for completed work. Work Item Age is the elapsed time since work started for items still in progress — a real-time metric for in-flight items. Age is the leading indicator; Cycle Time is the lagging one.
2How does Lead Time differ from Cycle Time as commonly used in the Kanban Guide for Scrum Teams context?
A.Lead Time and Cycle Time are identical
B.Lead Time is from customer request to delivery; Cycle Time is from when the team starts work to when it finishes
C.Lead Time is per stage; Cycle Time is end-to-end
D.Lead Time excludes weekends; Cycle Time includes them
Explanation: Lead Time is typically measured from the customer's perspective — request to delivery — and includes time spent waiting before the team begins work. Cycle Time, as defined in the Kanban Guide for Scrum Teams, is from when work starts (item enters the workflow's 'started' state) to when it finishes. The PSK community emphasizes Cycle Time because it is what the team controls.
3On a Cumulative Flow Diagram (CFD), what does the vertical distance between the 'started' and 'finished' lines represent?
A.Throughput
B.Lead Time
C.Work In Progress (WIP)
D.Defect rate
Explanation: The vertical distance between the cumulative line of started items and the cumulative line of finished items at any point in time is the count of items that started but have not finished — i.e., Work In Progress. The CFD shows this graphically and lets teams see WIP trends across the workflow.
4On a CFD, the slope of the 'finished' line indicates which flow metric?
A.Cycle Time
B.Throughput
C.Work Item Age
D.WIP limit
Explanation: The slope (rise over run) of the 'finished' band on a CFD represents the rate at which items are being completed per unit of time — that is, Throughput. A steeper slope means higher throughput; a flat segment means nothing is finishing.
5A flat horizontal segment in a middle band of a CFD most likely indicates what?
A.Healthy steady flow
B.A bottleneck or queue building up in that stage
C.Higher throughput
D.Reduced WIP
Explanation: When the line entering a stage keeps climbing but the line leaving the stage is flat, items are accumulating in that stage — a bottleneck. The widening band signals queue growth and rising Cycle Time. Investigate that stage's policies, capacity, or upstream dependencies.
6Why are color bands typically used on a CFD?
A.Decoration only
B.To show each workflow stage so you can see WIP per stage and where queues form
C.To indicate item priority
D.To indicate team assignment
Explanation: Each color band on a CFD corresponds to a workflow stage (e.g., Ready, Dev, Review, Done). The thickness of each band over time shows how much WIP is in that stage and where queues are forming, enabling targeted bottleneck analysis.
7On a Cycle Time scatterplot, what does the 85th percentile line communicate?
A.85% of items are outliers
B.85% of historical items finished in that cycle time or less
C.85% confidence the next item will be on time
D.The team's velocity in story points
Explanation: On a scatterplot of historical Cycle Times, the 85th percentile line says 85% of past items completed within that duration. It is a empirical, distribution-based statement about historical performance — useful for setting Service Level Expectations and right-sizing items.
8A point on the Cycle Time scatterplot well above the 95th percentile line most likely signals what?
A.Normal variation
B.A possible special-cause variation worth investigating
C.A faster-than-expected item
D.A measurement error always
Explanation: Points far above upper percentile lines are outliers and typically indicate special-cause variation — something unusual happened (a blocker, dependency, scope change, illness). They warrant investigation rather than being averaged away. Don't assume the cause; gather data.
9What is a Service Level Expectation (SLE) in the Kanban Guide for Scrum Teams?
A.A binding contract with the customer
B.A forecast of how long it should take a single item to flow from start to finish, with a probability
C.A SLA enforced by management
D.A prediction of throughput
Explanation: An SLE is a forecast of how long a single work item should take to flow from started to finished, expressed with a probability — for example, '85% of items will be done within 8 days'. It is empirical (from historical data), and it is a communication tool, not a commitment or contract.
10A team's SLE is '85% of items complete within 8 days.' What is the correct reaction when an item's age reaches 9 days?
A.Cancel the item — it failed the SLE
B.It is now in the 15% expected to take longer; investigate why and decide what action to take
C.Punish the team for missing the SLE
D.Ignore it — SLE is just a guideline
Explanation: An 85% SLE explicitly expects ~15% of items to exceed 8 days. An item passing the SLE threshold is a signal to investigate (blockers, dependencies, scope creep), have a conversation with the customer, and decide whether to expedite, split, or accept the delay — not a failure to penalize.

About the PSK II Exam

PSK II (Professional Scrum with Kanban II) from Scrum.org is the advanced credential validating your ability to apply the Kanban Guide for Scrum Teams in real-world Scrum environments. With an 85% passing threshold on 30 scenario-based questions in 60 minutes (some offering partial credit), it tests deep understanding of flow metrics interpretation, Monte Carlo forecasting, workflow optimization, and scaling flow across multiple Scrum Teams. PSK I and hands-on Scrum + Kanban experience are strongly recommended.

Questions

30 scored questions

Time Limit

60 minutes

Passing Score

85%

Exam Fee

$250 (Scrum.org)

PSK II Exam Content Outline

~30%

Advanced Flow Metrics & CFD/Control-Chart Interpretation

Cycle time vs work item age vs lead time vs throughput; reading Cumulative Flow Diagrams; control-chart outliers as special-cause variation

~20%

Probabilistic Forecasting & Right-Sizing

Monte Carlo simulation with historical throughput; 50/85/95% confidence levels; Right-Sizing instead of estimation

~25%

Workflow Optimization & Explicit Policies

WIP limits per stage/person/swim lane; explicit policies (DoR, swarm, expedite); Theory of Constraints; reducing handoffs and waiting

~15%

Coaching Flow & Inspect-Adapt with Data

Throughput in Sprint Planning, work item age in Daily Scrum, cycle-time scatterplots in Retrospective; Service Level Expectations

~10%

Scaling Flow Across Multiple Scrum Teams

Integrating multi-team workflows in Nexus; end-to-end value-stream visibility; coordinating WIP and dependencies across teams

How to Pass the PSK II Exam

What You Need to Know

  • Passing score: 85%
  • Exam length: 30 questions
  • Time limit: 60 minutes
  • Exam fee: $250

Keys to Passing

  • Complete 500+ practice questions
  • Score 80%+ consistently before scheduling
  • Focus on highest-weighted sections
  • Use our AI tutor for tough concepts

PSK II Study Tips from Top Performers

1Memorize the four flow metrics in the Kanban Guide for Scrum Teams: WIP, throughput, work item age, cycle time — and what each one tells you
2Practice reading Cumulative Flow Diagrams: line spread = WIP, slope = throughput, plateaus/gaps = bottlenecks or starvation
3Run Monte Carlo simulations against your team's historical throughput and report 50%/85%/95% confidence forecasts to build intuition
4Set up explicit policies for every workflow column (entry/exit criteria, WIP limit, expedite rules) and rehearse the Right-Sizing concept vs estimation
5For scenario questions, always favor empirical, transparent, and team-empowering answers — never command-and-control or prediction without data

Frequently Asked Questions

What is the PSK II passing score?

PSK II requires 85% or higher to pass — about 26 of 30 questions. Some questions provide partial credit, so a multiple-answer question with 4 correct selections may award fractional points if you select 3 of 4. The 85% threshold is identical to PSK I, but the questions are deeper, scenario-based, and demand applied judgment.

Do I need PSK I before taking PSK II?

PSK I is not a strict prerequisite, but it is strongly recommended. PSK II assumes mastery of the Kanban Guide for Scrum Teams plus real-world experience applying flow metrics, WIP limits, and probabilistic forecasting on a Scrum Team. Most candidates earn PSK I, gain 6-12 months of practice, then attempt PSK II.

How long does PSK II certification last?

PSK II is a lifetime certification from Scrum.org — it never expires and requires no renewal fees or continuing education. This matches all Scrum.org credentials and contrasts with Scrum Alliance certifications, which require biennial renewal.

What is the difference between PSK I and PSK II?

PSK I (45 questions, $200) tests fundamental knowledge of the Kanban Guide for Scrum Teams. PSK II (30 questions, $250) tests advanced application: interpreting CFDs and control charts, running Monte Carlo forecasts, setting explicit policies, applying Theory of Constraints, and scaling flow across multiple Scrum Teams. PSK II questions are scenario-based with partial credit.

What is the best way to prepare for PSK II?

Read the Kanban Guide for Scrum Teams and the Scrum Guide 2020 multiple times. Practice running Monte Carlo simulations with historical throughput. Build and interpret Cumulative Flow Diagrams, control charts, and scatterplots from real team data. Work scenario questions on bottlenecks, WIP limits, and scaling. Take the free Scrum with Kanban Open assessment until you score 100% consistently.

What types of questions are on the PSK II exam?

PSK II includes multiple choice (single answer), multiple answer (select all that apply), and true/false questions. Many are scenario-based: 'A team has a CFD showing… what should the Scrum Master do?' Some questions award partial credit. Time pressure is real — 60 minutes for 30 questions averages two minutes each, and complex scenarios can consume 4-5 minutes.

Can I use the Kanban Guide during the PSK II exam?

The exam is online and not officially open-book, but you do have access to the Kanban Guide for Scrum Teams on your computer. With only 60 minutes for 30 scenario questions, however, you cannot afford to look up answers — internalize the four flow metrics, definition of workflow, explicit policies, and forecasting practices in advance.