0% found this document useful (0 votes)
155 views

BAT Agile Framework Sprint Retrospective Format and Objectives Version 0.1

This document outlines an agile sprint retrospective format and objectives. It proposes that the retrospective have the output of documenting things for the team to start, stop, and continue doing to improve velocity and quality. It provides details on preparing for and running the retrospective meeting, including reviewing sprint performance, identifying improvement opportunities, and agreeing on next steps. The overall goal is to allow the team to reflect and brainstorm ways to streamline future sprints.

Uploaded by

dx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
155 views

BAT Agile Framework Sprint Retrospective Format and Objectives Version 0.1

This document outlines an agile sprint retrospective format and objectives. It proposes that the retrospective have the output of documenting things for the team to start, stop, and continue doing to improve velocity and quality. It provides details on preparing for and running the retrospective meeting, including reviewing sprint performance, identifying improvement opportunities, and agreeing on next steps. The overall goal is to allow the team to reflect and brainstorm ways to streamline future sprints.

Uploaded by

dx
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Digital Delivery

Agile Ways of Working

Agile Sprint Retrospective Format and Objectives

Discussion Document
Digital Delivery Discussion Document

1 Revision History
Date of this revision: 5th June 2013

Revision Summary of Changes Author Changes


date marked

06/06/13 Initial draft Michael Parkinson No

2 Distribution
Consultation distribution list:

 Alex Roth
 Karl Mansour
 Steve Barker
 Femi Hezekiah
 John Cowper
 Mark Vassallo
Digital Delivery Discussion Document

3 Purpose of this document


The purpose of this document is to outline a format for an element of the proposed agile
process.

4 Introduction

Continuous improvement is a core value within the Agile framework and no matter how good the
team has performed we can always do better.

The Sprint Retrospective provides a dedicated period of time, usually one to two hours, to allow
the team to reflect on their individual, team and tool set performance during the sprint and
brainstorm improvement opportunities.

At the end of the session the Scrum Master will take away a list of actions that will help to
streamline the next sprint, as well as a commitment from the team members.

5 The Retrospective

5.1 Output:

 A document outlining:
o Start – Things the team should start doing to improve velocity / quality.
o Stop – Things that the team know are making our lives difficult and slowing down
progress or degrading the potential quality of the end product.
o Continue – What the team is doing right and should focus efforts on continuing to
do and improve.

5.2 Preparation:

 Clearly defined and published definition of done.


 Feedback from the Sprint Review.
 Sprint Burn down
 Sprint Retrospective Log updated (See appropriate document)
 Impediments list from the daily stand ups.
 A suitable location outside the core workplace with:
o White Board and working Pens
o Projector
o Refreshments
Digital Delivery Discussion Document
o Power

5.3 The Sprint Planning Meeting Agenda

 Opening – Scrum Master.


o Welcome, review purpose of meeting, outline agenda, define meeting time box
and define rules of meeting. TURN OFF MOBILE PHONES AND LAPTOPS.
 Celebrate Success – Product Owner
o Review of key sprint achievements, energise the team.
 Review Burn down & impediment list – Scrum Master / Team
o Understand how the team burnt down the stories over the sprint and review /
capture the impediments that can be actioned to improve the teams velocity.
 Stop / Start / Continue – Scrum Master / Team
o Each team member must have at least one Stop / Start / Continue item for
discussion.
o Scrum Master to record all responses on a white board.
 Identify Key Opportunities – Scrum Master / Team
o Discuss each Stop / Impediment and brainstorm what can be done. Each item
will end up in one of three categories:
 Fix It Now: Items that we can change now to improve the next sprint.
 Fix It Later: Items that are large enough to require escalation to the PDM.
 Park It: Items that are outside of the teams and PDM’s control and
require considerable engagement / cultural change within the
organisation to resolve. Escalation to PDM.
 Agree Next Step – Scrum Master
o Fix It Now - Agree next steps, time box and owners.
o Fix It Later – Agree next steps, time box and owners. PDM to bring back to next
retrospective.
o Park It – Agree who these should be escalated to. PDM to bring back to next
retrospective.
 Retrospective – Scrum Master
o Get feedback, what went well, what could we do better next time?
 Rousing Cheer - Team
o Celebrate a successful Sprint Retrospective
Digital Delivery Discussion Document

Sprint Retrospective Log


Project Name:

Date: Sprint Name / ID

Attendees: Product Owner:


Scrum Master:
Project Manager
Team:

Chickens

Sprint Metrics
Stories Story Points
Stories planned for Sprint

Number of Stories Done:

Number of Stories not completed:

Percentage of Sprint Goal Achieved:

Velocity:

Sprint Impediments
ID Impediment Who Status
1 Fixed
Issue
Parked
2 Fixed
Issue
Parked
3 Fixed
Issue
Parked
4 Fixed
Issue
Parked
5 Fixed
Issue
Parked
6 Fixed
Digital Delivery Discussion Document
Issue
Parked
7 Fixed
Issue
Parked
8 Fixed
Issue
Parked
9 Fixed
Issue
Parked
10 Fixed
Issue
Parked
11 Fixed
Issue
Parked
12 Fixed
Issue
Parked

Start / Stop / Continue


ID Item Type Who
1 Start
Stop
Continue
2 Start
Stop
Continue
3 Start
Stop
Continue
4 Start
Stop
Continue
5 Start
Stop
Continue
6 Start
Stop
Continue
7 Start
Stop
Continue
8 Start
Stop
Continue
9 Start
Stop
Continue
10 Start
Stop
Continue
Digital Delivery Discussion Document
11 Start
Stop
Continue
12 Start
Stop
Continue
13 Start
Stop
Continue
14 Start
Stop
Continue
15 Start
Stop
Continue
16 Start
Stop
Continue

Opportunities
ID Item Type Who
1 Now
Later
Park It
2 Now
Later
Park It
3 Now
Later
Park It
4 Now
Later
Park It
5 Now
Later
Park It
6 Now
Later
Park It
7 Now
Later
Park It
8 Now
Later
Park It
9 Now
Later
Park It
10 Now
Later
Park It
11 Now
Later
Digital Delivery Discussion Document
Park It
12 Now
Later
Park It
13 Now
Later
Park It
14 Now
Later
Park It
15 Now
Later
Park It
16 Now
Later
Park It

Next Steps:

Fix It Now:

 [Who – When By]: Description

Fix It Later:

 [Who – When By]: Description

Park It:

 [Who – When By]: Description

Retrospective Feedback
[Any points raised to improve Retrospective format]

You might also like