Skip to content

Sprint Retrospective Report

Example prompt: "At the end of each 2-week sprint, pull all completed and incomplete stories from Jira, calculate our velocity, and generate a sprint retro doc in Notion."

How to automate sprint retrospectives with GloriaMundo

The Problem

Sprint retrospectives should be about honest reflection and improvement, but too often the first 20 minutes are spent compiling the data: someone scrolls through Jira pulling out what was completed, what carried over, what was added mid-sprint, and then tries to calculate velocity by hand. The numbers are approximate, the context behind each item is missing, and by the time a retrospective document is written up, it is the following week and the insights have gone stale. For teams running fortnightly sprints, this preparation work happens 26 times a year.

How GloriaMundo Solves It

We build a workflow that runs at the end of each sprint cycle. An integration step queries Jira for all stories in the sprint — completed, incomplete, and added mid-sprint — along with their story points, assignees, and status transitions. A code step calculates the key metrics: velocity (points completed vs planned), completion rate, carry-over count, and per-person contribution. An LLM step takes the raw data and generates a formatted retrospective document with sections for what went well, what did not, velocity trends compared to previous sprints, and suggested discussion topics. The finished document is created in Notion, ready for the retro meeting. Glass Box preview shows you the full document before it is published.

Example Workflow Steps

  1. Trigger (scheduled): Runs at the end of each 2-week sprint (e.g., every other Friday afternoon).
  2. Step 1 (integration): Query Jira for all stories in the current sprint — status, story points, assignee, date completed, and whether the item was added mid-sprint.
  3. Step 2 (code): Calculate sprint metrics — velocity, completion rate, carry-over items, points added mid-sprint, and per-person breakdown.
  4. Step 3 (llm): Generate a structured retrospective document with sections for completed work, incomplete items, velocity analysis, observations, and suggested discussion topics.
  5. Step 4 (integration): Create the retrospective document as a new page in the team's Notion workspace.
  6. Step 5 (integration): Post a link to the retro doc in the team's Slack channel with a summary of the key metrics.

Integrations Used

  • Jira — source of sprint data including stories, points, statuses, and assignees
  • Notion — where the formatted retrospective document is published for the team
  • Slack — notifies the team that the retro doc is ready with a summary of key metrics

Who This Is For

Scrum masters, engineering managers, and team leads who run regular sprint cycles and want to arrive at retrospective meetings with the data already compiled and the document already drafted. Especially useful for teams of 5-15 engineers where manual sprint reporting falls to one person every two weeks.

Time & Cost Saved

Compiling sprint data and writing a retrospective document manually takes 1-2 hours per sprint. Over a year of fortnightly sprints, that is 26-52 hours of preparation work. This workflow delivers a ready-to-use retro document within minutes of the sprint ending, so the team can spend their retrospective time discussing and improving rather than gathering data.