CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Lessons learned (retrospectives at project level) capture what went well and what should improve. BAs contribute requirements-focused insights: which elicitation techniques produced high-quality requirements, where stakeholder engagement was insufficient, and how requirements errors could be prevented in future projects.

**Why not A:** Lessons learned reviews are not exclusive to executives. They are collaborative sessions that include team members from various roles, including BAs, project managers, developers, and testers. Excluding BAs would miss valuable insights about requirements quality and stakeholder engagement that only BAs can provide.

**Why not B:** A lessons learned review is a project-level activity, not a personal educational reflection. It examines the collective experience of the project team to identify organizational and process improvements. Framing it as a personal learning exercise misrepresents its purpose and scope entirely.

**Why not D:** While project managers may facilitate lessons learned sessions, the output is not simply a list of mistakes authored by one person. Effective lessons learned capture both successes and areas for improvement from the entire team's perspective, and the BA's contributions about elicitation effectiveness and requirements practices are an essential part of the analysis.