At the end of the sprint, the Product Owner, Team
and Scrum
Master meet to review the progress of the sprint. The product owner has
to
evaluate the state of the project so s/he can decide what to do next.
How does
the Product Owner ensure that s/he gets a complete and correct
understanding
about the state of the project, including all inconvenient truths? Here
is a
simple agenda/meeting template to follow, to make sure all the bases
are
covered.
Last week, I introduced that concept of a Sprint
Contract to
define the parameters of the sprint. The factors Scope, Quality, Time
and Cost
will be familiar to any project manager. Scope is defined by the
stories and in
particular their size. Quality is defined primarily by the definition
of done.
Time is fixed by the sprint duration. An upper limit on the costs is
set by the
team size * sprint duration, after adjusting for absences and other
tasks.
A simple sprint review needs to
- Confirm that the team has delivered on its commitments
- Confirm that the overall project is on track
- Examine the functionality which has been delivered.
Bookmark/Search this post with:
At the beginning of each sprint, the Scrum team
and product
owner negotiate the scope of the sprint. They have a limited amount of
time to discuss
and agree on the sprint backlog. The product owner wants functionality
implemented properly and to invest development dollars wisely. The team
wants a
mandate it can fulfill. And everyone wants the meeting to finish on
time! Here
is an agenda (complete with a downloadable template) to follow so that your sprint planning will be successful.
Bookmark/Search this post with: