Do you create a Sprint Review/Retro email?

After any Sprint Review and Retrospective, an email should be sent to all the stakeholders to update them on the outcome from the Sprint:

Firstly, create a new email copying the information from the previous Sprint Review/Retro. As per Do you know what happens at a Sprint Retrospective meeting?, it should include the following:

It's important that an Email Group is setup for the project, and the Sprint Review is sent to that group, so that anyone who joins the project in future can access these reports from shared inbox as per Do you choose which Microsoft 365 Groups you follow?


To:	{{ PRODUCT OWNER }}
Cc:	{{ SPRINT REVIEW ATTENDEES }}, {{ PROJECT GROUP EMAIL }}, {{ SPRINT REVIEW REPORTING EMAIL }}
Subject:	{{ PRODUCT NAME }} - Sprint {{ X }} Review/Retro

Hi {{ PRODUCT OWNER }}

Here are the Sprint Goals and their status at a glance:

Sprint Goals (in priority order):

Bugfixes – Done ✅
WDM Integration – Done ✅
SSO/Roles APIs – In Progress 🕑
Download Documents APIs – Not Done ❌

Please see below for a more detailed breakdown of the Sprint:

Sprint in Review:	{{ SPRINT NUMBER }}
Sprint Duration:	{{ NUMBER OF WEEKS }}
Project:	{{ PROJECT NAME }}
Project Portal:	{{ LINK TO PROJECT PORTAL }}
Test Environment:	{{ LINK TO TEST ENVIRONMENT }}
Product Owner:	{{ PRODUCT OWNER NAME }}

Attendees: (Optional as they may be in the to and CC)

Sprint Review

ID	Title	State	Effort
24124	UI Improvements	Done	4
24112	Integrate Business Logic to MVC app	Done	8
24097	Styling	Committed	16

Figure: Sprint Backlog from {{ LINK TO SPRINT BACKLOG }}

Sprint Burndown (a quick overview of the Sprint)

Figure: Sprint Burndown
Timesheet data - Who worked in a Sprint?

sprint timesheet data — Figure: Timesheet data for a Sprint

Code Coverage (hopefully tests are increasing each Sprint)

{{ CODE COVERAGE }}
Velocity (Optional)

{{ VELOCITY }}
Burnup (for the release - the whole project, how are we tracking for the big picture?)

Figure: Release Burnup
Build Pipeline Health & Production Deployments (How many times did we deploy to Production?)

Figure: Build Pipeline Health from DevOps

Figure: Deployments from {{ DEPLOYMENT SERVICE }}
Application Health Overview Timeline (For the entire Sprint)

Figure: Application Health Overview Timeline
Product Roadmap

{{ ROADMAP LINK }}

Progress:

{{ EPIC #1 }}

Currently {{ TOTAL # OF PBIS COMPLETED }}/{{ TOTAL # OF PBIS CREATED }} PBIs completed (there will be more)
- {{ # OF PBIS COMPLETED THIS SPRINT }} Completed this Sprint
- {{ # OF PBIS CREATED THIS SPRINT }} Newly created this Sprint

{{ EPIC #2 }}

Currently {{ TOTAL # OF PBIS COMPLETED }}/{{ TOTAL # OF PBIS CREATED }} PBIs completed (there will be more)
- {{ # OF PBIS COMPLETED THIS SPRINT }} Completed this Sprint
- {{ # OF PBIS CREATED THIS SPRINT }} Newly created this Sprint

{{ EPIC #3 }}

Currently {{ TOTAL # OF PBIS COMPLETED }}/{{ TOTAL # OF PBIS CREATED }} PBIs completed (there will be more)
- {{ # OF PBIS COMPLETED THIS SPRINT }} Completed this Sprint
- {{ # OF PBIS CREATED THIS SPRINT }} Newly created this Sprint

R&D

Did we do any experimental work?

{{ INSERT DETAILS of any trial/error processes, and ensure all detail is captured as per https://ssw.com.au/rules/do-you-record-your-failures }}

{{ INSERT DETAILS of any problems for which no solutions existed, and ensure detail is captured as per https://ssw.com.au/rules/do-you-record-your-research-under-the-pbi }}

Sprint Retrospective

As part of our commitment to inspect and adapt as a team we conduct a Sprint Retrospective at the end of every Sprint. Here are the results of our Sprint Retrospective:

✅ What went well?

❌ What didn’t go so well?

💡 What improvements will be made for the next Sprint?

Definition of Ready (Optional)

{{ INSERT DEFINITION OF READY (Normally saying that the PBIs are sized with Acceptance Criteria added) }}

Definition of Done (Optional)

{{ INSERT DEFINITION OF DONE (Normally saying that it compiles, meets the acceptance criteria, and a test please has been sent if relevant) }}

< This is as per the rule https://ssw.com.au/rules/sprint-review-retro-email />

Figure: Good example - Template for Sprint Review/Retro email