The document provides a template for conducting a Sprint Review, Retrospective, and Planning meeting. It includes sections for demoing completed work, reviewing work accepted in the previous Sprint, discussing key performance metrics and action items from the prior Retrospective, setting the Sprint goal, and estimating work for the upcoming Sprint.
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Sprint Review and Planning Template
1. Sprint Review and Planning Meeting
Template
• I am a Scrum Master for multiple Scrum Teams
• I use the following template to guide the teams through
• Sprint Review/Demo/Retrospective
• Sprint Planning
• I show a couple of reporting views to encourage reflection
and conversation
• I share the completed deck with the teams once we have
completed Sprint Planning
3. Project Review/Demo
• Demos
• Nothing is too small to demo!
• Doesn’t have to be a software demonstration
• New functionality demo 1
• New functionality demo 2
• Updated UI demo 1
• Monitoring demo 1
4. Work Accepted
• I will export a list of work accepted from Rally and include
it here
• I do this just to document the Development Team’s work
effort
5. Sprint Retrospective
• How Are We Doing KPIs
• Performance: Velocity over Time
• Performance: Release Burnup
• Performance: Work Accepted
• Planning: Planned Velocity vs. Actual Velocity
• Quality: Rolling 30-day Defect Trend
6. Velocity Over Time
100% Accepted - 95 out of 95 points.
Last 3 Average: 96 points
Best 3 Average: 117 points
0
20
40
60
80
100
120
140
52
92
104.5
65
115
130.5
102
122
Q1 Velocity
7. Q1 Release Burnup
35
87
179
283.5
348.5
463.5
632
734
856
400
500
600
700
800
850 856 856 856
0
100
200
300
400
500
600
700
800
900
December
1st Half
2012
January 1st
Half 2013
January 2nd
Half 2013
February 1st
Half 2013
February
2nd Half
2013
March 1st
Half 2013
Q1 Pre-
Release
Cycle
April 2nd
Half 2013
May 1st Half
2013
Q1 Release Burnup
14. Sprint Goal
• On this slide I will call out the goal of the sprint.
• Or the top goals of the sprint. Many times we will have 2-3 main
user stories or defect fixes that we are working.
• I find it provides a little bit of help with team focus.
15. Sprint Planning
• We will assign points to ALL user stories and defects
• EVERY we pull into a sprint defect will get a minimum of 3
points