Skip to content
PMPCAPM

Retrospectives (General)

A Retrospective is a recurring meeting where a team reflects on its recent work period to identify what went well, what could be improved, and what actions to take for continuous improvement.

Share:

Explanation

Retrospectives are a cornerstone of agile continuous improvement and are not limited to Scrum. Any team using any methodology can benefit from regular retrospectives. The twelfth agile principle states that the team regularly reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Retrospecti ves come in many formats beyond the simple what-went-well/what-to-improve structure. Popular formats include Start-Stop-Continue, the 4Ls (Liked, Learned, Lacked, Longed For), the sailboat metaphor (wind = helps, anchors = slows), timeline retrospectives, and appreciative inquiry. Varying the format keeps the practice fresh and surfaces different types of insights.

The most important aspect of a retrospective is follow-through. Identifying improvements is only valuable if the team actually implements them. Best practice is to select one or two actionable improvements and add them to the next iteration's work. Teams that consistently act on retrospective insights see compounding improvement over time.

Key Points

  • Regular reflection on process for continuous improvement
  • Not limited to Scrum; applicable to any team or methodology
  • Many formats: Start-Stop-Continue, 4Ls, sailboat, timeline, and more
  • Follow-through on action items is critical for realizing value

Exam Tip

Retrospectives are about continuous improvement of the process. The most important outcome is actionable improvement items, not just discussion.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Part of

Agile & Hybrid

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.