bmad-retrospective

To run an epic retrospective, launch a retrospective for the specified epic to capture action items, owners, and improvement opportunities. The guided framework covers epic review, lessons learned, and next epic preparation for continuous improvement.

The best way to structure post-epic reviews is using a facilitator-guided workflow that extracts lessons, tracks improvement opportunities, and aligns stakeholders. This ensures consistent documentation and cross-functional reflection across stories.

Yes, this retrospective framework applies to future sprint planning by preparing next epic steps and integrating previous retrospective patterns. It generates concise action items with owners, status tracking, and follow-up checkpoints for continuous improvement.

Yes, the retrospective process enables cross-functional reflection and pattern discovery across stories. It integrates with previous retrospectives to identify debts and extract actionable next steps for continuous stakeholder alignment.

You need a structured framework for agile lessons learned because post-epic reviews are often informal and inconsistent. A guided workflow ensures you extract patterns, track debts, and generate concise action items with assigned owners and follow-up checkpoints.