4. Product vision
• Concise statement that
• Clarifies the scope of the new
product
• Enough for funding
• Helps to keep the development
focused and consistent
• Communicated effectively
• Formats: A3,Executive
summary, Wall, Vision
document
• States
• Customers and users of the
software
• Needs addressed
• Most important product
attributes
• Revenue model
• May compare the product to
other products
Certified ScrumMaster - version 2.4 4
Metaphor:
1. How do we do
better visual product
visions
5. Theme, epic, feature and
user story
• Feature is a valuable functionality
• Theme is a collection of related features
• Epic is a large feature
• User story is a description of desired functionality told
from the perspective of the user or customer
• User stories are used to describe features, epics and themes
Theme Epic Feature(User story)
Certified Scrum Product Owner - version 1.3 5
Calendar
As a clerk
I want to use
calendar functionality
As an clerk
I want to create a new course event
so that the meeting is saved into
calendars of the trainer and the class
21.11.2010
7. Augmenting user stories
• In Agile and Scrum big frond-
end design is depreciated
• Time-boxes limit the time to use
in requirements and design
• Forces to go ahead with just
enough information
• Use augmentation only when
necessary
• Keep as light as possible
• User centric design emphasizes
UI designs to help users
understand the requirements
• Storyboards
• Mockups ( PostIt-notes)
• Prototypes
• Other examples:
• Spreadsheet showing business
rules
• Diagram showing a work flow
• Remember: product owner is
available for the Team during
the Sprints !
21.11.2010 Certified Scrum Product Owner - version 1.3 7
3. How do we do
better visualization of
user stories
8. Agile development
Certified Scrum Product Owner - version 1.3 8
• Goals
• Sprint backlog
• Dashboard
• Product vision
• Architecture
vision
• User stories
• GUI sketches
• SW design
P
TP
T
A
W
P
C
Wall
Emerging software
21.11.2010
9. Acceptance tests
• User stories are commonly
refined with acceptance tests
• Exceptions, alternative
scenarios
• In XP a tester helps the
customer to create automated
tests
• Can be expressed in a table
format
IN
• Values of the input variables
• ….
ACTION
• Description of the invocation of
the functionality ( e.g. button
click)
OUT
• Values of the output variables
• …
Certified Scrum Product Owner - version 1.3 921.11.2010
4. How do we do
better acceptance
tests ? Visual ?
10. 10
Certified Scrum Product Owner - version 1.3
Agile testing
• Goal not to detect errors
but improve programming,
design …
• Test harness prevents
errors
10
C
T
P
C
T
P
Spec
Vision
Code
Test
cases
Equal ?
Code that
Implements tests
Automated test that
Define requirements
OK?
21.11.2010
5. How do we do
better
collaboration?