evo-retrospective

To run an agile retrospective for completed epics, load the full retrospective workflow from the project repository path to guide discussions, capture insights, and automatically extract lessons learned into concrete action items.

An epic review is a post-epic analysis to identify what went well, what failed, and performance gaps. You need it after epic completion to turn delivery experiences into actionable lessons for future improvement.

Retrospective findings improve future epic planning by aligning extracted lessons learned and action items with roadmaps and team processes, ensuring past performance gaps inform and adjust upcoming delivery strategies.

Yes, you can use this retrospective workflow without external dependencies. It operates as a standalone process, requiring only that you load and follow the predefined workflow from your project repository.

The best way to capture actionable lessons learned is using structured retrospective prompts that guide discussions, validate outputs against predefined criteria, and automatically translate insights into concrete action items.

Yes, the epic review process requires a project repository setup. You must load and follow the full retrospective workflow from the repository path and validate outputs against predefined criteria stored there.