back to notes

Sprint Retrospective Conversation Checklist

This list is to help teams assess their current Scrum implementation. It is meant to be used as a tool during the team's retrospective to help drive conversation and experiment with new ideas.

Recommended but not always Necessary
Teams has all the skills needed to bring backlog items to done
PBL items are broken into tasks within a sprint
Team members not locked into specific roles
Velocity is measured
All items in sprint plan have an estimate
Velocity only includes items that are Done
Iterations that doomed to failure terminated early
Standup is every day same time & place
PO participates at least a few times per week
SM focusing on removing impediments
Max 15 minutes
PO has product vision that is in sync with PBL
Team members pick up any tasks, regardless of their specialty
Document decisions (meeting minutes)
Define Acceptance Criteria for each ticket
Team has clear goal
Team has a Scrum Master(SM)
SM has strategy for how to fix top impediment
Each team member knows what the others are doing
Escalated to management when team can't solve
PBL and product vision is highly visible
Everyone on the team participates in estimating
PO available when team is estimating
Team has a sprint burn down chart


last updated august 2019