Run data-driven sprint retrospectives

Analyze sprint health metrics and action items

Engineering teams running retrospectives who want data-driven insights from git history supplemented by team feedback.

• · Git log data (commits, authors, timestamps)
• · Sprint metadata (story points, velocity)
• · Team feedback or blockers

• · Retrospective document with findings grouped by framework
• · 3-5 specific, assignable action items
• · Metrics table (velocity, cycle time, bug rate)

• · Git (git log, git shortlog)

• · Sprint has completed
• · Git history available for analysis

• · May miss subjective team dynamics (only git-based)
• · Weekend commits do not always signal burnout (could be time-zone work)
• · Large PRs could be legitimate features, not scope creep

• · Gathers git metrics: commits per author, large PRs, reverted commits, weekend patterns
• · Five analysis categories (what went well, didn't go well, metrics, action items, output)
• · Looks for 'fix fix' and 'wip' commit messages (rushed work signals)
• · Outputs structured retro document ready for team sharing