bmad-retrospective

To run a blameless retrospective for a completed agile epic, facilitate a systems-focused discussion across developer, QA, product owner, and architect roles to extract lessons and assess success for future iterations.

Extract actionable lessons learned by enforcing a blameless, systems-focused review process that evaluates team collaboration and process improvement, producing concrete ownerable action items rather than targeting individuals.

The best way to document post-epic reviews is to generate a concise retrospective document that captures lessons learned, assigns owners to action items, and performs continuity checks to ensure learning is applied to the next epic.

Yes, a structured retrospective workflow guides discussion across multiple perspectives including developer, QA, product owner, and architect, ensuring all roles contribute to process improvement and next-epic preparation.

You should conduct a retrospective immediately when an epic concludes to assess success, document lessons learned, and prepare continuity checks that guide future delivery and team collaboration for the next iteration.

Assign owners to action items during the post-epic review by translating the blameless, systems-focused discussion into concrete ownerable tasks, documenting them in the retrospective output to ensure accountability for process improvement.