Agile Retrospective Checklist
Use this framework to easily perform retrospectives. The retrospective affords the team a dedicated opportunity to collectively evaluate their processes. Retrospective meetings embrace a teams commitment to continuous improvement. The goal of these meetings is to inspect and adapt team practices and processes in an effort to identify and take action on key issues that are impeding the team's progress of health.
How often should this be used?
On the last day of each iteration or weekly if appropriate.
Library
Categories
Agile Retrospective
Attendees
Team Members
ScrumMaster and/or Facilitrator
Product Owner
Preparation / Inputs
Details and accomplishments from the prior iteration
List of issues or impediments
Agenda
Review meeting agenda and guidelines
Purpose:
The retrospective affords the team a dedicated opportunity to collectively evaluate their processes.
Retrospective meetings embrace a teams commitment to continuous improvement.
The goal of these meetings is to inspect and adapt team practices and processes in an effort to identify and take action on key issues that are impeding the team's progress of health
Key considerations:
- Always remember, and remind the team, that retrospectives are intended to focus on the process and not people
- Whoever facilitates should make an effort to ensure all team members participate
Team reviews what went well during the last iteration
Team reviews what didn't go well or as planned during the last iteration and why
Team identifies the most important items or issues to focus on next iteration
Team notes any additional impediments preventing them from adopting and/or improving their process
Confirmed outputs
Prioritized impediments or newly identified stories for action in an upcoming iteration
We help you and your business
Make ChecklistsItemize your repeatable tasks once - perform them many times.
Document ProcessesProvide detailed documentation alongside tasks.
