HKSM

A self-managing, empowered Scrum Team reviews what went well and what did not in each Sprint, capturing takeaways that guide targeted improvements in the very next Sprint.

Key Points

• Lessons are primarily surfaced in the Sprint Retrospective and refined throughout the Sprint.
• Focus on improving process, quality, collaboration, and value delivery, not assigning blame.
• Turn insights into concrete actions (e.g., update working agreements, Definition of Done, checklists) and add them to the Sprint Backlog.
• Apply improvements immediately in the next Sprint to enable continuous, incremental growth.

Example

After a Sprint, the team discovers that vague acceptance criteria led to rework. They agree to add an acceptance criteria template, schedule a refinement checklist review, and pilot pair testing for complex stories in the next Sprint.

PMP Example Question

During a Sprint Retrospective, a Scrum Team identifies recurring delays due to unclear handoffs. What is the best next step?

1. Record the lesson for project closure and continue current practices until then.
2. Escalate the issue to the PMO and wait for an organization-wide process update.
3. Create specific improvements (e.g., define handoff criteria, update working agreements) and add action items to the next Sprint.
4. Replace the team member most associated with the delays.

Correct Answer: C — Implement concrete improvements based on Sprint lessons.

Explanation: Scrum Teams convert lessons from the Retrospective into actionable changes for the next Sprint rather than deferring action or blaming individuals.