PSK I · Scrum.org · Scrum framework with Kanban · Bank updated 2026-11-04
PSK I practice questions: Scrum framework with Kanban
5 free questions from 13 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Scrum framework with Kanban section of our PSK I bank (13 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 13 Scrum framework with Kanban questions and the full PSK I bank: $15 one-time.
1/5 · Scrum framework with Kanban · hard
A Scrum Team has a WIP limit of four and four items are in progress. Midway through the Sprint a stakeholder asks the Product Owner to start a new item right away, and the Product Owner relays the request to the Developers. What does the team's pull system imply?
Athe team starts the item at once and accepts that WIP temporarily exceeds four
Bthe team starts the item and lifts the WIP limit until the Sprint ends
Cthe item waits until another item finishes and WIP drops below the limit
Dthe Scrum Master decides whether the WIP limit may be exceeded for this one request
Answer: C. Limiting WIP creates a pull system: the team pulls an item only when it has capacity, and a drop below the limit is the signal to start new work. A push system would start work whenever it is requested. The team should stick to the limit once established.
Source: The Kanban Guide for Scrum Teams, Scrum.org and ProKanban.org, January 2021, CC BY-SA 4.0, Limiting Work in Progress (WIP), p. 5
Source: Kanban Guide for Scrum Teams (2021) and Scrum Guide 2020
2/5 · Scrum framework with Kanban
A newly formed Scrum Team adopts Kanban practices in its first Sprint and has no historical Cycle Time data. A Developer suggests skipping the service level expectation until data exists. What does the Kanban Guide advise?
Amake a best guess now and revisit it when enough data exists
Bleave it out until the team has collected enough finished items
Cadopt another team's SLE as is and keep it fixed
Dhave the Product Owner set it from the desired delivery dates
Answer: A. An SLE should be based on the team's historical Cycle Time. Where none exists, the Scrum Team makes its best guess and then inspects and adapts once there is enough data to do a proper calculation.
Source: The Kanban Guide for Scrum Teams, Scrum.org and ProKanban.org, January 2021, CC BY-SA 4.0, Service Level Expectation (SLE), p. 6
Source: Kanban Guide for Scrum Teams (2021) and Scrum Guide 2020
3/5 · Scrum framework with Kanban · easy
A Scrum Team sets up its first Kanban board with columns for its workflow states and cards for Product Backlog items. Which addition does the Kanban Guide list as part of the workflow visualization?
Athe Developer's name on each card
Ba story point estimate on each card
Cpolicies for limiting work in progress
Da burn-down chart of remaining Sprint work
Answer: C. Visualization of the Workflow should include defined start and finish points, a definition of work items, the workflow states with at least one active state, explicit policies for each state, and policies for limiting Work in Progress.
Source: The Kanban Guide for Scrum Teams, Scrum.org and ProKanban.org, January 2021, CC BY-SA 4.0, Definition of Workflow, p. 5
Source: Kanban Guide for Scrum Teams (2021) and Scrum Guide 2020
4/5 · Scrum framework with Kanban · hard
During a Sprint, a Scrum Team finds that merging two workflow states would remove a recurring wait. A colleague claims the Definition of Workflow can change only in the Sprint Retrospective. What does the Kanban Guide say?
Ait may change at any time, with the Retrospective as regular cadence
Bit stays fixed during the Sprint and is revised at the Retrospective event
Cit is revised at Sprint Planning, along with the Sprint Backlog items
Dit changes mid-Sprint once the Product Owner approves the new states
Answer: A. The Scrum Team inspects and adapts its Definition of Workflow using the Scrum events. Changes may happen at any time, but they materially affect team performance, so making them in the regular cadence of the Sprint Retrospective reduces complexity and improves focus, commitment and transparency.
Source: The Kanban Guide for Scrum Teams, Scrum.org and ProKanban.org, January 2021, CC BY-SA 4.0, Sprint Retrospective, p. 8
Source: Kanban Guide for Scrum Teams (2021) and Scrum Guide 2020
5/5 · Scrum framework with Kanban
On day four of a two-week Sprint, a Product Backlog item meets the Definition of Done. A stakeholder asks to use it right away, but a Developer wants to hold it back for the Sprint Review. What is correct?
Ahold it until stakeholders have seen it at the Sprint Review
Brelease it together with the other Sprint items at Sprint end
Chold it until the Product Owner has accepted the remaining Sprint items
Ddeliver it to the stakeholder now, well before the Sprint ends
Answer: D. The moment an item meets the Definition of Done an Increment is born. Multiple Increments may be created within a Sprint, and an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be a gate to releasing value.
Source: The 2020 Scrum Guide, Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0, Increment, p. 14
Source: Kanban Guide for Scrum Teams (2021) 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.