The Scrum Field Guide: Practical Advice for Your First Year (Agile Software Development Series) by Mitch Lacey

Author:Mitch Lacey
Language: eng
Format: mobi, epub
Publisher: Pearson Education
Published: 2012-03-11T18:30:00+00:00

Preparing for the Meeting

First, I am a fan of using slides in the sprint review meeting. They help the team members organize their thoughts and provide something for the stakeholders to take with them when they leave. For every sprint review meeting, I use the following template; each bullet is an individual slide:

• The sprint goal

• The stories we committed to delivering

• The stories we completed

• The stories we failed to complete

• Key decisions made during the sprint, which may include technical, market-driven, requirements, etc., and can be decisions made by the team, the product owner, the customers, or anyone else

• Project metrics (code coverage, etc.)

• Demonstration of the completed work

• Priority review for the next sprint

Depending on the type of system you are building, you may also find you need to prepare technically, for instance, have a build ready or deployed to a pre-production or staging environment. In these cases, consider a mock run-through. Have a team member spend some time going through and reviewing some of the stories that will be shown to the customers. Is the data correct? Are the connection strings working? Did data get repopulated from one environment to the next? These small details can come back to bite you when you’re in the meeting.

At first, all that preparation seems to be in direct violation of the rules, and if taken to the extreme, it is. Preparation should not get in the way of the work. Spending some time getting information together and planning the review meeting goes a long way toward making a team appear more informed and helping the stakeholders understand what they are supposed to be looking for. I don’t live by a hard and fast rule that the team can spend only one hour preparing for the meeting, as this is extremely difficult for new Scrum teams to do. That being said, there’s a limit to how much prep time is too much. I’ve seen teams take two days to get things ready, which, especially in a short sprint, is overkill, and points to larger issues. Therefore, although new teams will likely need more time to prep than an experienced team, all teams should be working toward the goal of prepping for an hour or less each sprint.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.