PSK I · Scrum.org · Scrum events with Kanban (flow-based) · Bank updated 2026-11-04
PSK I practice questions: Scrum events with Kanban (flow-based)
5 free questions from 25 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Scrum events with Kanban (flow-based) section of our PSK I bank (25 questions on this area). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 25 Scrum events with Kanban (flow-based) questions and the full PSK I bank: $15 one-time.
1/5 · Scrum events with Kanban (flow-based) · hard
During a Sprint, a Scrum Team using Kanban sees work piling up in one column and wants to inspect its flow policies without waiting for the usual Sprint events. Which action does the Kanban Guide for Scrum Teams permit?
Areplace the Sprint Retrospective with a flow-based retrospective
Bmove the Sprint Retrospective to the middle of the Sprint
Cpostpone the discussion until the next Sprint Review has been held
Dhold an extra flow-based retrospective at the moment it is needed
Answer: D. The guide says the Sprint Retrospective still takes place after the Sprint Review and before the next Sprint Planning. However, "flow-based retrospectives need not coincide within the boundaries of a Sprint" and can occur just in time or on a cadence. The team can therefore add one when the need arises.
Source: The Kanban Guide for Scrum Teams (2018), Scrum.org, KanbanGuideST2018-p8, p. 8
Source: Kanban Guide for Scrum Teams (2018) and Scrum Guide 2020
2/5 · Scrum events with Kanban (flow-based) · hard
On day six of a ten-day Sprint, a Scrum Team finishes a feature that fully meets its Definition of Done. Stakeholders would like to start using it, but a team member says it must wait. What should the team do?
Aask stakeholders to accept it at the Sprint Review first
Bbundle it with the remaining Done items at Sprint end
Ckeep it back until the Sprint Retrospective concludes
Ddeliver it to stakeholders before this Sprint is over
Answer: D. The Scrum Guide says an Increment may be delivered to stakeholders prior to the end of the Sprint, and "The Sprint Review should never be considered a gate to releasing value." The item meets the Definition of Done, so it can be delivered.
Source: The 2020 Scrum Guide, Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0, ScrumGuide2020-p13, p. 12
Source: Kanban Guide for Scrum Teams (2018) and Scrum Guide 2020
3/5 · Scrum events with Kanban (flow-based)
A Scrum Team using Kanban has an item that was started nine days ago and still sits in the review state. The team wants a metric that shows how long this and every other unfinished item has been underway so far, to spot items that are lingering. Which metric serves this purpose?
AWork Item Age of each started item
BCycle Time of each started item to date
CThroughput of the Sprint so far
DWIP counted across the whole board today
Answer: A. Work Item Age is defined as the amount of time between when a work item started and the current time, and "This applies only to items that are still in progress." Cycle Time is tempting but is measured between start and finish. Throughput and WIP are counts, not elapsed times.
Source: The Kanban Guide for Scrum Teams, Scrum.org and ProKanban.org, January 2021, CC BY-SA 4.0, The Basic Metrics of Flow, p. 4
Source: Kanban Guide for Scrum Teams (2018) and Scrum Guide 2020
4/5 · Scrum events with Kanban (flow-based)
Halfway through a Sprint, a competitor's launch makes the Sprint Goal obsolete. The Developers and the Scrum Master agree that continuing the Sprint is pointless. Who has the authority to cancel the Sprint?
Athe Product Owner of the Scrum Team
Bthe Scrum Master of the Scrum Team
Cthe Developers of the Scrum Team
Dthe whole Scrum Team by joint decision
Answer: A. The Scrum Guide says a Sprint could be cancelled if the Sprint Goal becomes obsolete, and "Only the Product Owner has the authority to cancel the Sprint." Agreement of the Developers and Scrum Master does not transfer that authority.
Source: The 2020 Scrum Guide, Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0, The Sprint, p. 8
Source: Kanban Guide for Scrum Teams (2018) and Scrum Guide 2020
5/5 · Scrum events with Kanban (flow-based)
At a team's Sprint Review, the Developers demonstrate the finished work while stakeholders watch and rarely speak. Afterwards the Product Owner notes that nobody discussed what to do next. Which change aligns best with the Scrum Guide?
Alimit it to a presentation of the Increment and gather written comments later
Brun it as a working session in which attendees collaborate on next steps
Creplace it with a status report that the Product Owner circulates
Dreduce it to a Product Owner check of each item against the Definition of Done
Answer: B. The Scrum Guide says the Scrum Team and stakeholders review what was accomplished and what changed, then collaborate on what to do next. It adds: "The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation."
Source: The 2020 Scrum Guide, Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0, Sprint Review, p. 10
Source: Kanban Guide for Scrum Teams (2018) and Scrum Guide 2020
Other PSK I areas
The same kind of free sample for every other section of the PSK I bank:
Practise PSK I with instant feedback
6 free questions in study mode · no card · full PSK I bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start PSK I free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by Scrum.org. PSK I and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official Scrum.org materials (as of November 2026); always confirm current details with the vendor before booking.