After-Action Reviews: Structured Lessons Learned for Exam Success
PMBOK v8 Definition
After-action reviews (AARs) are a simple, structured process used to analyze what happened, why it happened, and how it can be done better by the participants and those responsible for the project or activity. AARs are typically conducted at the end of a project or after significant milestones to capture lessons learned and inform future activities. This concept belongs to the Monitoring and Controlling Process Group and the Project Knowledge Management knowledge area, specifically linked to the Manage Project Knowledge process.
Why It Matters for the Exam
The PMI exam frequently tests AARs because they represent a practical, structured approach to continuous improvement—a core project management principle. Questions appear in situational scenarios where you must identify the correct tool for capturing lessons learned, distinguishing AARs from other knowledge management techniques. Expect these in questions about process improvement, team performance, and closing processes.
Key Points to Remember (for the exam)
-
Origin: Originating from the U.S. Army, AARs are designed to improve team performance by reflecting on actions taken and outcomes achieved.
-
Timing: Conducted at the end of a project OR after significant milestones—not only at project close.
-
Four Key Questions (structured reflection):
- What was supposed to happen?
- What actually happened?
- Why were there differences?
- What can we learn?
-
Diagnostic Process: Involves diagnosing what went well and what did not, identifying both strengths and weaknesses.
-
Participant Involvement: All team members involved in the project participate in the review, ensuring comprehensive understanding.
-
Documentation: Findings are documented and shared with relevant stakeholders to ensure valuable lessons are captured and disseminated.
-
Primary Goal: Reinforce learning and improve future performance by applying insights gained from the review.
Typical PMI Exam Example
A project manager completes the first phase of a software development project. The team notices recurring communication delays. Which tool should the project manager use to systematically analyze what happened, why it happened, and how to improve? Answer: Conduct an After-Action Review using the four key questions to capture lessons learned and inform the next phase.
PMI Exam Traps
-
Trap: Confusing AARs with lessons learned register updates
-
Reality: AARs are the structured process (the meeting/activity); lessons learned register is the output document where findings are recorded
-
Trap: Thinking AARs only occur at project closure
-
Reality: AARs are conducted at the end of a project or after significant milestones throughout the project lifecycle
-
Trap: Assuming AARs focus only on problems
-
Reality: AARs diagnose both what went well (strengths) AND what did not (weaknesses)
-
Trap: Believing only the project manager participates
-
Reality: All team members involved in the project participate in the review
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Lessons Learned Register | Output of AARs | AARs produce findings that are documented in the lessons learned register |
| Manage Project Knowledge | Parent Process | AARs are a tool/technique within this process; lessons learned register is created early in this process |
| Lessons Learned Repository | Final Destination | At end of project/phase, AAR findings are transferred to this organizational process asset |
| Continuous Improvement | Core Principle | AARs are a primary mechanism for applying learning to improve future performance |
Quick Review Questions
-
What are the four key questions asked during a structured After-Action Review?
-
When should After-Action Reviews be conducted—only at project closure, or also at other times?
-
Who must participate in an After-Action Review to ensure comprehensive understanding?
-
What is the primary goal of conducting After-Action Reviews?
-
Where are AAR findings ultimately stored after the project or phase ends?
PMBOK v8 Reference
Section 4.6.2.2 – Manage Project Knowledge: Tools and Techniques (After-Action Reviews)