bmad-retrospective

To facilitate an epic retrospective, trigger a structured workflow that analyzes completed stories, extracts lessons learned, and generates concrete action items. This process drives continuous improvement by synthesizing story-level insights into patterns and risks.

An epic retrospective in Scrum is a post-epic review to extract lessons and assess success. You should run this retrospective process when an epic is completed to evaluate team learning, review technical debt, and close feedback loops.

You extract lessons learned from completed agile stories by executing a guided retrospective workflow that synthesizes story-level analysis and previous retro reviews. This surfaces patterns, risks, and opportunities while capturing actionable process improvements.

Yes, you can plan the next epic using retrospective action items. The workflow integrates next-epic planning with dependency awareness and readiness checks, ensuring that lessons learned and process improvements directly inform future sprint execution.

The best way to capture technical debt and process improvements after an epic is through a deterministic retrospective workflow. It coordinates artifact generation across review phases to synthesize insights and document concrete action items for the team.

Yes, the retrospective workflow integrates previous retro reviews to close feedback loops. By applying story-level analysis and prior lessons learned, it ensures continuous improvement and prevents recurring issues across subsequent epics.