1. The document provides guidance on transforming ideas into software requirements through establishing a product vision, identifying users, writing user stories, and building a prototype.
2. It emphasizes balancing business and user needs, iterating to improve the product, and focusing on user experience (UX).
3. The agenda includes creating a product vision, identifying personas, writing user stories organized on a user story map, and building a paper prototype using the Pop app to demo functionality.
2. Most people with an idea…
• ‘know’ they’ve got a market for a product
• have limited UX/design capabilities
• will develop something that users don’t really
want
• need to move fast as they probably have a
limited (or zero) budget
10. Agenda…
• Create your Product Vision
• Identify your Users
• Write User Stories
• Build a Prototype
11. Product Vision
Why - the reason for creating the product
What – the goal you are aiming for
12. Who Creates the Product Vision?
Everyone involved in developing the product as
the whole team must share the same vision
Source: http://www.productmanagerclub.com/category/envisioning/
13. Benefits
• Avoid useless features
• Prioritise the backlog targeting the main goal
• Align information across the team
14. Golden rules
• Target the customer
• Target the customer’s needs
• Identify the market
• Identify Product attributes
• How do I know if my product vision works?
ELEVATOR TEST!
15. Product Vision Template
For _______________ who ___________________
(target customer) (customer need)
___________________ is a ___________________
(product idea) (market category)
that ____________________________
(key benefit)
Unlike ________________, __________________
(competitor) (unique differentiator)
16. Product Vision Example
“For a mid-sized company's marketing and sales departments
who need basic CRM functionality, the CRM-Innovator
is a Web-based service that provides sales tracking, lead
generation, and sales representative support features that
improve customer relationships at critical touch points.
Unlike other services or package software products,
our product provides very capable services at a moderate
cost”
Source: http://www.quora.com/What-are-some-good-examples-of-a-product-vision
17. Exercise 1: Create your Product Vision
• Each team should brainstorm and come up with
a product idea (e.g. Smart Fridge)
• Create a Product Vision Statement for your
product idea
• Pitch your Product Vision to the group
Duration: 15 Minutes
18. Identify Your Users
• What is a Persona?
– archetypal users of an system that represent the
needs of larger groups of users
– identify the user motivations, expectations and
goals
• Why do we need them?
– Helps identify user motivations, expectations and
goals
19. Personas must be…
• Relevant to business goals and the product
• Data driven with clearly defined assumptions
• Enlightening and inspiring
22. User Stories…
• Describe functionality that
is useful to the user or
customer
• Tell a story about how
someone uses the product
23. Focus on the User
• Describe functionality
from the perspective of
your target users
• Use personas or user
roles in your stories
24. Engage in Conversation
• A story is not a specification.
• It captures the essence of a conversation
about the features of a product
• User Stories encourage creativity
• Stories facilitate dialogue between the team
and the customer
25. Example User Story
Amanda, a new Netflix customer,
wants to see recommendations for other movies
she could watch based on her past viewings
so that she gets to know what else is available to
watch without having to browse a long list of
movies
26. Epic
• A high level goal of a Persona
• Usually too big to implement in single iteration
• Usually split into features and then stories
29. Exercise 2: Write User Stories
• Identify 2 personas for your product idea
• Write a few User Stories for each persona
• Group the User Stories into Themes (Features)
• Group the Themes into high level goals (Epics)
• Create a User Story Map
Duration: 30 Minutes
32. Exercise 3: Create a User Story Map
• Organise Epic, Themes and User Stories into a
User Story Map
• Assign each User Story a T-shirt size (S,M,L,XL
or XXL)
• Arrange User Stories in priority order (highest
at the top)
Duration: 20 Minutes
34. Exercise 4: Build a Prototype
• Download the Pop™ App to your
Smartphone
• Create paper prototypes of typical screens
for your App
• Capture your prototypes with Pop™
• Link the screens inside Pop ™
• Demo your prototype
Duration: 30 Minutes
35. Summary
• You have just converted your idea into Agile
Software Requirements
• You now have enough information to
– Engage a UX Designer
– Engage a Web Developer
– Engage an App Developer
– Learn some coding and do it yourself!
• Congratulations!
http://www.payton-consulting.com/run-user-story-workshop/
‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in.
‘Epic’ – a large user story that will usually be split into smaller stories
‘Theme’ – a group of features
‘Feature’ – A discrete piece of business value.
‘User Story’ – Contributes to a Feature. What teams deal with everyday.
‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in.
‘Epic’ – a large user story that will usually be split into smaller stories
‘Theme’ – a group of features
‘Feature’ – A discrete piece of business value.
‘User Story’ – Contributes to a Feature. What teams deal with everyday.
‘Epic’, ‘Feature’ and ‘Theme’ have had different meanings in every company I have worked in.
‘Epic’ – a large user story that will usually be split into smaller stories
‘Theme’ – a group of features
‘Feature’ – A discrete piece of business value.
‘User Story’ – Contributes to a Feature. What teams deal with everyday.
