User story mapping overview
•Als PPTX, PDF herunterladen•
1 gefällt mir•267 views
Provides an overview of user story mapping (what it is, why use it & terminology). Contains an example story map that I created for a shoe website. Presentation can be used to provides an overview about the technique + in workshops when creating a story map for your product.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Empfohlen
Empfohlen (20)
User story mapping overview
- 1. User Story Mapping By Ryan Thomas Hewitt
- 3. GOAL ACTIVITIES TASKS STORIES WHAT IS A STORY MAP?
- 4. BENEFITS ● Understand the end to end solution ● Structure requirements by user tasks + priority ● Helps with planning releases (i.e. slices) ● Becomes your product backlog
- 5. Example
- 6. SHOES COMPANY GOAL ACTIVITIES TASKS STORIES We want to create a website selling shoes to teenagers. It’s called Shoes Company
- 7. SHOES COMPANY GOAL ACTIVITIES TASKS STORIES Find a product View a product Buy a product Add a product
- 8. SHOES COMPANY GOAL ACTIVITIES TASKS STORIES Find a product Browse navigation 3rd party search View featured products Search on site Read a Facebook post Read a promo email Read an advert Read a text alert
- 9. SHOES COMPANY GOAL ACTIVITIES TASKS STORIES Search on site Search by keyword (e.g. Adidas, Nike, Jordans) Filter by shoe size Filter by colour Sort by price Sort by popularity Find a product
- 10. SHOES COMPANY
- 11. Let’s try Activities e.g. Investigate case Tasks e.g. Attach evidence Stories e.g. Attach photos, attach videos
Hinweis der Redaktion
- I am going to provide a high level overview of user story mapping as a technique. Now some of you may already be familiar with this technique but for those of you who are not i will give you a high level explanation of what it is before we do an activity where we can practice using this.
- Story mapping is a technique invented by Jeff Patton.
- A story map is a tool to help you visualise the scope of your product. It has an added benefit that you can see the high level structure and use it to prioritise stories. To create an impact map you need to answer 4 key questions Why are you doing this? What is the goal What are the high level user activities What are the tasks users need to do What are the user stories that achieve these tasks It’s a living document. That means it can and will change as work is identified + priorities change
- Owners per epic Identify gaps Better than a list of JIRA tickets
- Lets take a look at an example of this…
- A FES example of an activity might be “receive a case” Activities are high level tasks
- A FES example of an activity might be “receive a case” Task = a short verb that describe what people do
- Lets take a look at an example of this…
- Try it for your real project