bmad-retrospective

To conduct an agile retrospective for a completed epic, analyze project documents to extract lessons, assess successes and challenges, and prepare for future sprints. This reflective practice requires access to project artifacts and context.

A post-epic review is a reflective practice where teams analyze completed epics to extract lessons and assess success. It improves team collaboration by facilitating structured discussions with clear guidelines and psychological safety.

Yes, you can compare current retrospectives with previous ones to track improvements and identify missed opportunities. This continuous improvement analysis helps agile teams refine their processes and outcomes over time.

Prepare for the next epic after a retrospective by identifying dependencies, risks, and necessary preparation steps. This ensures future sprints are built on extracted lessons and assessed project context.

You need access to project artifacts and context to facilitate effective post-epic reviews. These documents are analyzed to extract lessons, assess epic success, and prepare for future continuous improvement work.

Yes, this retrospective approach applies to agile teams seeking to improve their processes and outcomes. It facilitates thorough post-epic reviews through reflective practice to extract actionable lessons.