game-postmortem

Run a structured project post-mortem by automatically pulling git history, milestone data, and retrospective notes to generate a report. This process extracts actionable lessons aligned with a five-phase workflow to build a reusable knowledge base.

Conduct a post-mortem analysis when a major project or milestone is complete, not for sprint-level reviews. Post-mortems analyze broad project outcomes, whereas sprint retrospectives focus on shorter iterative cycles.

Yes, you can use this post-mortem workflow for general software deliveries with milestones. While designed for game development projects, the structured analysis applies to any software project utilizing git history and milestone data.

The best way to extract actionable lessons is automating pattern analysis across git history and retrospective notes. This identifies what went well and wrong, generating a structured post-mortem report that feeds a reusable knowledge base.

Yes, you need retrospective notes, git history, and milestone data to generate a post-mortem report. These inputs are automatically pulled to ensure the analysis covers development progress and team feedback comprehensively.

Automated post-mortem analysis is limited if you lack git history, milestone data, or retrospective notes. It is not intended for design reviews or sprint-level retrospectives, requiring a defined post-mortem workflow to function correctly.