1. Description of Show and Tell
Project Name
Description of Show and Tell
00 Month | Firstname Lastname

2. User stories covered Instructions:
List all the user stories (use cases for non-Scrum) to be shown, taken from the project tracker.
If there is more than one product owner, include the name of the product owner for each user story. (Scrum best practices state there should only be one product owner)

3. Rules
“This session is to show…” (Give a business description of what is going to be shown.)
It is a work in progress.
Interfaces are all stubbed / partially stubbed as appropriate.
UI standards are draft.
This session is not to have a business discussion about how things should work or for people seeing this for the first time to suggest changes.
This session is to demonstrate progress against a set of elaboration requirements we have already agreed to.

4. What feedback would we like ?
Anything that is different from what was agreed during elaboration and documented in the user stories (product/process owners mainly).
Anything that stands out as missing. (Just make note of what’s missing. There is no need to go into detail during this discussion because there will be another opportunity to get feedback from smaller audiences for specific areas.)
Opinions on UI are notoriously hard to get agreement on as everyone has a different view. These to be fed via the person responsible for UI (product owner or UI specialist)
Opinions on UI, which is notoriously hard to get an agreement on as everyone has a different view, should come from the product owner or UI specialist.
Feedback, question, and comments should go through the product owner who will decide what is valid and prioritize the feedback for inclusion as appropriate.

5. SHOW AND tell

6. Questions?