Skip to main content

Post-Implementation Review: Epic {N}

Epic: {Epic Name}
Status: COMPLETE
Review Date: {YYYY-MM-DD}
Reviewer: {Name/Username}
Version Range: {Start Version} to {End Version}
PIR Version: 1.0.0

Executive Summary​

[One paragraph summary of Epic outcomes, key achievements, and overall assessment]

Goals Assessment​

  • Goal 1: {Goal Description}

    • Status: {Achieved/Partially Achieved/Not Achieved}
    • Assessment: {Detailed assessment of goal achievement}
    • Evidence: {Supporting evidence or metrics}

  • Goal 2: {Goal Description}

    • Status: {Achieved/Partially Achieved/Not Achieved}
    • Assessment: {Detailed assessment of goal achievement}
    • Evidence: {Supporting evidence or metrics}

  • Goal 3: {Goal Description}

    • Status: {Achieved/Partially Achieved/Not Achieved}
    • Assessment: {Detailed assessment of goal achievement}
    • Evidence: {Supporting evidence or metrics}

Stories Review​

[Review each Story in the Epic]

Story {N}: {Story Name}​

  • Status: COMPLETE
  • Version: {Version}
  • Goals Achieved: {Yes/No/Partial}
  • Quality: {Excellent/Good/Satisfactory/Needs Improvement}
  • Key Findings: {Summary of story outcomes}
  • Tasks Completed: {Count} / {Total}
  • Notable Achievements: {List key achievements}
  • Issues Encountered: {List any issues or blockers}

Technical Assessment​

Architecture Decisions​

{Key architecture decisions made during Epic execution}

  • Decision 1: {Description}

    • Rationale: {Why this decision was made}
    • Impact: {Impact on project}

  • Decision 2: {Description}

    • Rationale: {Why this decision was made}
    • Impact: {Impact on project}

Code Quality​

  • Overall Assessment: {Excellent/Good/Satisfactory/Needs Improvement}
  • Code Review Coverage: {Percentage or description}
  • Technical Debt Introduced: {Description of any technical debt}
  • Code Quality Metrics: {Any metrics available}

Documentation​

  • Completeness: {Excellent/Good/Satisfactory/Needs Improvement}
  • Documentation Created: {List key documents}
  • Documentation Gaps: {Any gaps identified}
  • Documentation Quality: {Assessment}

Testing​

  • Test Coverage: {Percentage or description}
  • Test Quality: {Excellent/Good/Satisfactory/Needs Improvement}
  • Test Types: {Unit/Integration/E2E/etc.}
  • Test Results: {Summary of test outcomes}

Lessons Learned​

What Went Well​

  • {Item 1: Description of what worked well and why}
  • {Item 2: Description of what worked well and why}
  • {Item 3: Description of what worked well and why}

What Could Be Improved​

  • {Item 1: Description of what could be improved and how}
  • {Item 2: Description of what could be improved and how}
  • {Item 3: Description of what could be improved and how}

Patterns Identified​

  • Pattern 1: {Description of pattern}

    • Context: {When/where this pattern appears}
    • Value: {Why this pattern is valuable}
    • Recommendation: {How to leverage this pattern}

  • Pattern 2: {Description of pattern}

    • Context: {When/where this pattern appears}
    • Value: {Why this pattern is valuable}
    • Recommendation: {How to leverage this pattern}

Anti-Patterns Identified​

  • Anti-Pattern 1: {Description of anti-pattern}

    • Context: {When/where this anti-pattern appears}
    • Impact: {Negative impact of this anti-pattern}
    • Recommendation: {How to avoid this anti-pattern}

  • Anti-Pattern 2: {Description of anti-pattern}

    • Context: {When/where this anti-pattern appears}
    • Impact: {Negative impact of this anti-pattern}
    • Recommendation: {How to avoid this anti-pattern}

Follow-Up Actions​

[Actions identified during review that should be tracked as Kanban tasks]

  • Action 1: {Description}

    • Priority: {High/Medium/Low}
    • Owner: {Assigned to}
    • Related Work: {Link to related Epic/Story/Task}

  • Action 2: {Description}

    • Priority: {High/Medium/Low}
    • Owner: {Assigned to}
    • Related Work: {Link to related Epic/Story/Task}

Knowledge Capture​

[Key knowledge items to preserve for future reference]

Best Practices​

  • {Best practice 1: Description and context}
  • {Best practice 2: Description and context}

Lessons for Future Epics​

  • {Lesson 1: Description and application}
  • {Lesson 2: Description and application}

Documentation Recommendations​

  • {Recommendation 1: What documentation should be created/updated}
  • {Recommendation 2: What documentation should be created/updated}

Metrics​

  • Duration: {Start Date} to {End Date}
  • Stories Completed: {Count} / {Total}
  • Tasks Completed: {Count} / {Total}
  • Versions Released: {Count} (Range: {Start Version} to {End Version})
  • Time to Completion: {Duration in days/weeks}
  • Epic: Template path under docs/: project-management/kanban/epics/Epic-{N}/Epic-{N}.md (replace {N}; do not paste unresolved {N} into markdown links — Docusaurus validates paths).
  • Stories: {Links to all stories in Epic}
  • Related PIRs: {Links to any related PIR reports}
  • Follow-Up Tasks: {Links to Kanban tasks created from this PIR}

References​

Template Usage:

  • Copy this template when creating an Epic PIR
  • Fill in all relevant sections
  • Update Epic document with PIR summary
  • Create follow-up Kanban tasks for identified actions
  • Link PIR to Epic document bidirectionally

This template is part of the Workflow Management Framework. See packages/frameworks/workflow mgt/ for complete framework documentation.