A detailed sprint report that recaps progress, extracts key performance metrics, and delivers a business impact report for stakeholders.

1.0

Anthropic: Claude 3.7 Sonnet

Project: Purpose Project: Features / Advantages Project: Target Audience Project: Tech Stack Formatter Sprint Issues

• Input: Sprint issues, sprint goals, and associated ticket data.

• AI Task:

  • Compile a table of current sprint progress and tasks.

  • Align each task to the corresponding sprint goals and goal tickets.

• Output: A table view summarizing:

  • Task/Issue

  • Aligned Sprint Goal

  • Current Status/Progress

• Input: List of sprint issues with their fields (e.g., status, priority, type, sprint goal alignment, story points, blocker flag, creation date, assignee, labels, epic association).

• AI Task:

  • Extract and calculate key metrics that can be derived from the available issue fields, such as:

    • Total Issue Count: Total number of issues in the sprint.

    • Completion Rate: Percentage of issues marked as "Done" or "Closed" versus total issues.

    • Sprint Goal Alignment: Count or ratio of issues linked to sprint goal tickets.

    • Issue Type Distribution: Breakdown of issues by type (e.g., bug, feature, task).

    • Priority Distribution: Breakdown of issues by priority level (e.g., high, medium, low).

    • Blocked Issues Count: Number of issues flagged as blocked or impeded.

    • Average Story Points: Average of story points across issues (if available).

    • Unresolved Issues Count: Count of issues that remain open or in progress.

    • Assignee Coverage: Ratio of issues assigned versus unassigned.

    • Average Issue Age: Average duration from issue creation to the current date.

    • Reopened Issues Count: Count of issues that were reopened after initial closure.

    • Assignee Workload Distribution: Number of issues assigned per team member.

    • Label Frequency Analysis: Frequency of tags/labels used across the issues.

    • High-Priority Issue Percentage: Percentage of issues marked as high priority.

    • Epic Association Rate: Proportion of issues linked to epics or larger features.

    • Bug Ratio: Ratio of bug-type issues compared to non-bug issues.

    • Critical Issues Count: Number of issues marked as critical (if a severity field exists).

    • Recent Activity Rate: Percentage of issues updated during the sprint period.

• Output: A summary table listing:

  • Metric Name

  • Measured Value

  • Trend/Commentary (if applicable)

• Input: Consolidated insights from the sprint recap and key metrics.

• AI Task:

  • Synthesize the findings into a clear report focused on business value.

  • Eliminate technical details and emphasize outcomes that drive business impact.

  • Provide actionable recommendations tailored for stakeholder decision making.

• Output: A stakeholder-focused report featuring:

  • Executive Summary

  • Business Impact Overview

  • Actionable Recommendations