Final Product Review
1 Audience and Purpose
As you know, a product review is targeted at the product owner.
The
purpose is to convince the product owner that the acceptance criteria
have been satisfied.
However, unlike the reviews for earlier sprints, the final review
will be observed by all members of all of the teams. This is so that
everyone can learn from the other teams' presentations.
2 Incomplete Features
The product you demonstrate must not contain any incomplete features. In
other words, if the user interface makes it seem like a feature is
available then it must actually be available. For example, the
product must not have any menu options that do not do anything or
buttons that do not do anything.
3 Length
You will have 20 minutes for the review, including setup-time and
break-down time. If it will take longer than 20 minutes to
cover all of the acceptance criteria then you must prioritize them.
4 Demonstration Environment
You must demonstrate your implementation using the "lab laptop"
that will be available at the instructor's podium.
You must bring a "thumb drive" that contains the application (as an
executable .jar
file). If the marketing and sales team
has requested multiple variants (e.g., for branding reasons), then
it will need to contain multiple .jar
files. If the
marketing and sales team has requested that the product support
multiple languages, then you may need to run the program from the
command-line in order to override the default locale.