Home
Do you create a Sprint Review/Retro email?
  v16.0 Posted at 19/10/2015 3:57 PM by Christopher Briggs
​​After any Sprint Review and Retrospective, an email should be sent to all the stakeholders to update them on the outcome from the sprint:
  • Subject: <Client Name> Sprint XX Review/Retro
  • This is a reply to the Sprint Forecast email
  • Screenshot of Burndown from TFS
  • Breakdown of work completed (including current code coverage value)
  • Link to test environment
  • Relevant notes from the retrospective

Hi [Product Owner],

Sprint in Review: [Sprint Number]
Sprint Goal: [Goal​]
Sprint Duration: [Numbe​r 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
24124UI ImprovementsDone
24112Integrate Business Logic to MVC appDone
24097StylingNew
Figure: Sprint Backlog from [Link to Sprint Backlog in TFS]

 

As per http://rules.ssw.com.au/Management/RulesToBetterScrumUsingTFS/Pages/RetrospectiveMeeting.aspx, we review:

1. Sprint Burndown (a quick overview of the sprint)

Figure: Sprint Burndown

2. Code Coverage (hopefully tests are increasing each sprint)
XXX

3. Velocity (Optional)
XXX

4. Burnup (for the release - the whole project, how are we tracking for the big picture?)

Release Burnup.jpg
Figure: Release Burnup

5. Production Deployments (How many times did we deploy to Producti​on?)

production-deploy.jpg
Figure: Deployments from Octopus Deploy

6​​. Application Health Overview Timeline (For the entire spirnt)

Application Health Overview Timeline.png

​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?
<insert what went well from retro>

What didn’t go so well?
<insert what did not went well from retro>

What improvements will be made for the next Sprint?
<insert what improvements will be made for the next Sprint>

Definition of Ready - Optional

<insert the definition of Ready. Normally that the PBIs are Sized with Acceptance criteria added>

Definition of Done - Optional

<insert Definition of Done. Normally that it compiles, meets the acceptance criteria, and a test please has been sent if relevant>​

<This is as per the rule: http://rules.ssw.com.au/Management/RulesToBetterScrumUsingTFS/Pages/Do-you-create-a-Sprint-Review-email.aspx>

Figure: Good Example - Template for Sprint Review/Retro Email. Subject: Sprint xxx Review/Retro

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address:

    Comments: