Any Team Project Retrospectives for Continuous Improvement

PMBOK v8 Definition

A retrospective is a regularly occurring workshop in which participants explore their work and results in order to improve both the process and product. Retrospectives are a form of a lessons learned meeting and are conducted frequently throughout the project (at minimum, at the end of each iteration). The term retrospective is usually used within adaptive development approaches but can refer to any lessons learned session in any approach.

Why It Matters for the Exam

This concept appears frequently in situational questions about team performance, process improvement, and tailoring decisions. The PMI exam tests your understanding that retrospectives are not exclusive to agile projects—they apply to any project approach and are a key tool in the Project Performance Domain for continuous improvement.

Key Points to Remember (for the exam)

• Definition: A retrospective is a regularly occurring workshop exploring work and results to improve both process and product
• Frequency: Conducted frequently throughout the project, at minimum at the end of each iteration
• Applicability: Term used in adaptive approaches, but refers to any lessons learned session in any approach
• Participation: The entire project team participates in retrospectives
• Typical Questions: Cover process-based questions—what worked well, what did not, and recommendations for future iterations
• Purpose: Helps ensure team can quickly address issues and implement improvements rather than waiting until project end
• Tailoring Indicator: Retrospectives help assess effectiveness of current approaches and identify areas for improvement through tailoring

Typical PMI Exam Example

A project manager is leading a hybrid project with both predictive and adaptive components. During the third iteration, the team identifies several process inefficiencies. What should the project manager do first?

Answer: Conduct a retrospective with the entire project team to explore what worked well and what did not, and gather recommendations for future iterations.

PMI Exam Traps

• Trap: Thinking retrospectives are only for agile/adaptive projects

  • Reality: The term is usually used in adaptive approaches but can refer to any lessons learned session in any approach

• Trap: Confusing retrospectives with end-of-project lessons learned

  • Reality: Retrospectives are conducted frequently throughout the project, not just at the end

• Trap: Believing only the project manager or facilitator participates

  • Reality: The entire project team participates in retrospectives

• Trap: Assuming retrospectives only focus on product improvements

  • Reality: They cover both process and product improvements, typically using process-based questions

Important PMI Connections

Quick Review Questions

1. A project team using a predictive approach wants to improve their processes. Can they use retrospectives? Why or why not?

2. At minimum, how frequently should retrospectives be conducted during a project?

3. Who should participate in a retrospective session?

4. What three typical questions are covered in a retrospective?

5. How do retrospectives relate to the tailoring of project approaches?

PMBOK v8 Reference

Section 2 – Project Management Performance Domains (Team Performance Domain) Section 3 – Tailoring (Table 3-1: Common Situations and Tailoring Suggestions)