A county records modernization team runs Scrum Sprints and also mirrors some Kanban habits. What is a fair distinction between Scrum’s Sprint Retrospective and typical Kanban continuous-improvement cadences?
Select an answer to reveal the explanation.
Short Explanation
Scrum parks a dedicated ‘what should we tweak?’ meeting at the end of each Sprint. Kanban is more like fixing traffic flow every day with WIP limits and metrics—improvement is continuous and ceremonies are lighter. Related goal, different machinery.
Full Explanation
Scrum includes a Sprint Retrospective as a required event that inspects people, relationships, process, and tools after each Sprint. Kanban emphasizes evolutionary change, limiting work in progress, and managing flow; improvement may be continuous and supported by optional cadences rather than Scrum’s fixed Sprint Retrospective. Distinguishing those components avoids treating all adaptive methods as identical.