/review

Sprint Review Report Generator

Generate a comprehensive sprint review report for showcasing completed work and tracking commitments.

Usage

/scrum:review [PROJECT_KEY]

Example: /scrum:review SKL

Report Contents

The report includes:

• Sprint Summary: Sprint name, dates, goal, and completion status
• Completed Work: All tickets completed during the sprint grouped by epic/feature area
• Demo Script: Organized demo flow with talking points and suggested order
• Commitment Tracking: Committed vs. completed story points analysis
• Missed Commitments: Incomplete tickets with reasons (if available)
• Sprint Metrics: Velocity, completion percentage, and trends

Workflow

Step 0: Invoke the ceremonies skill

MANDATORY: Invoke the skill FIRST before any ceremony preparation

Invoke Skill: scrum:ceremonies-recipe

This loads ceremony preparation patterns, sprint review data requirements, and validation workflows.

Step 1: Run the review data generation script

Execute the script with the project key from ARGUMENTS:

cd plugins/scrum/skills/ceremonies-recipe/scripts && python3 generate_review_data.py {{ARGUMENTS}}

This will:

1. Identify the most recent completed sprint
2. Compile all completed tickets
3. Group tickets by epic/feature area
4. Generate demo script with suggested flow
5. Calculate commitment tracking metrics
6. Identify missed commitments with analysis

Step 2: Read and present the generated report

The script generates a markdown file named review_report_YYYYMMDD.md in the current directory.

Read this file and present it to the user.

Step 3: Validate report (per ceremonies skill)

Verify:

• ✓ Report file generated successfully
• ✓ Sprint identified with name and dates
• ✓ Completed tickets compiled and grouped
• ✓ Demo script generated with organized flow
• ✓ Commitment tracking calculated (committed vs completed)
• ✓ Missed commitments identified with reasons
• ✓ All required metrics calculated

If validation fails, cite specific missing data.

Step 4: Provide actionable insights

Based on the report, offer observations such as:

• Sprint completion: Percentage of committed work completed
• Feature areas: Key themes and accomplishments
• Demo flow: Suggested order for maximum impact
• Commitment analysis: Reasons for missed items
• Retrospective topics: Issues to discuss in retro
• Stakeholder highlights: Key achievements for presentation

Focus on actionable insights that help prepare for an effective sprint review.

Implementation Notes

Completed Work Compilation (AC 7.4.1):

• Identifies tickets with status "Done", "Closed", or "Resolved"
• Groups tickets by epic/feature area
• Orders groups by business priority
• Includes ticket ID, title, type, and story points
• Links to each ticket in Jira

Demo Script Generation (AC 7.4.2):

• Organizes completed work by user journey or feature area
• Suggests demo order based on logical flow
• Includes talking points for each feature
• References related tickets for context
• Estimates demo time per section (based on complexity)

Commitment Tracking (AC 7.4.3):

• Compares committed vs. completed story points
• Calculates completion percentage
• Lists all completed commitments
• Identifies missed commitments with reasons
• Suggests retrospective discussion topics

Sprint Detection:

• Automatically identifies the most recent sprint
• Prioritizes active sprints over closed sprints
• Falls back to most recently closed sprint
• Allows manual sprint specification with --sprint-id flag

Output File:

• Default filename: review_report_YYYYMMDD.md (current date)
• Custom filename: Use -o filename.md flag
• Sprint selection: Use --sprint-id ID for specific sprint

Environment Requirements:

• JIRA_EMAIL: Jira email address
• JIRA_API_TOKEN: Jira API token
• JIRA_BASE_URL: Jira instance URL