About this class
Did you realize how difficult is to visualize the product as a whole when working with a typical Flat Product Backlog?
A solution is User Story Mapping. A user story map is a simple idea, is about arranging user stories into a helpful shape. User Story mapping are used by top companies of any industries to visualize goals with activities and agree fast on how to achieve them with minimum versions of the product.
This workshop will guide you step by step with a realistic example that you can also follow with your own project.
Why taking the class? What you will gain?
- Become more effective in planning your sprints, roadmaps and interact with stakeholders and developers.
- Skills to create User Story mapping
- Tips to facilitate a User Story Mapping Session
- A Story Mapping for your own Products.
- Interaction and exposure for using one of the best tools
This class can always be improved, so if you have any topic that you would like to know more, please let me know so I can see to include it in this class or in future courses.
What are you waiting? Start this course now :)
About me
Hi my name is Ignacio. https://www.linkedin.com/in/ignaciopaz/
I led, coached, led and managed Agile projects and scrum teams since 2005 for customers all over the world.
During my career of intensive learning I got many scrum certifications including Certified Scrum Professional Scrum Master, Professional Product Owner and Certified Agile Leadership which are very difficult to achieve.
I worked 15 years as a Professor for Agile Methodologies and Systems design.
I love to teach Agile and Scrum and I designed a lot of hours of training that I am bringing online. I prefer to teach with games and activities that can simulate the real world.
I trained hundreds of students in Agile that became top professionals in the industry.
Teaching what I learned in my 20 years of experience allows the students to gain realistic learning that they can apply at work.
Required: Some knowledge of Scrum, Agile and User Stories.
This course is not suitable for:
- People with Zero knowledge of Scrum, Agile and User Stories
- People looking to learn how to wrtie User Stories
- People looking to learn about of Scrum and Agile. I will have new classes for that
- People that want to take certifications. I will have new classes for that
What you will learn?
- Persona
- Product Vision
- Elevator Pitch
- Flat Product Backlog vs. User Story Mapping
- User Story Mapping, goals, activities, cards
- Adding Personas to User Story Mapping
- Prioritize with Story Mapping
- Define MVP and Releases
What you will you create?
In this workshop you will create a complete User Story Mapping for a realistic example, for your own project or both.
- A Persona
- The Product Vision
- The Product elevator pitch
- A Product Backlog
- A complete refined User Story Mapping with goals, activities, users and cards
- Define the MVP for your product and releases
This course is specifically for:
- People familiar with Agile, Scrum and User Stories who want to learn new techniques
- People that have problems orgranizing the Product Backlog and planning releases and roadmaps
- People that like a activities and workshop style
- Business people, managers that want to lean how Agile would help them
- Product Owners, Product Managers, Leaders, Designers, UX, Scrum Masters, Agile Coaches.
- Developers, Project Managers, Business Analysts, Solution Architects, Enterprise Architects, Data Base Administrators and basically anyone interested in learning more of Agile.
Assignment Instructions
- Persona Template: Print or make a working copy of the persona Template https://docs.google.com/document/d/1y4PWVqjscPelUEDDz1AWmBM-L7GMCVzBywJwFiu1dFs/edit?usp=sharing
- Create: Write the profile of a persona for one of these options:
- For your Product: A product or project that you are working on
- Course Project related: A shoes customer
- Inspiration:
- Consider thinking about people you know
- You can call a friend or family member to understand how they behave.
- A bit more out of our comfort zone, You can go to a shop and ask people help you to understand their customer behaviors for your training course.
Assignment Instructions
Using the following template for an elevator pitch:
For [target customer], who [needs/problems], our product [product name] is a [product category], that [key benefit]. Unlike [primary competitor], our product [differentiator features].
- Create: Write an elevator pitch for a product that you are currently working on. Use the persona and product vision of the previous assignments as an input.
- Practice: Practice your elevator pitch: At work or with friends, whenever someone asks you what you are working on, use your elevator pitch to explain them really quickly. Check their reactions, interest, and questions and use them to adapt and improve your elevator pitch.
Alternatively, you can write a new version of the elevator pitch for the UniqueShoes sample product of this course.
--
Another format: Optionally, if you'd like, you can try another format. There are many templates for an elevator pitch. This another format I really like too:
- Hook: Amazing fact, statistics, or question to catch the attention
- Problems: Which problems and needs I cover
- Solutions: Which solutions I bring and benefits
- Traction/Why me: Why the project is the right one
- Call to action/Ask: next steps, request
If you are interested you can see an example here: https://youtu.be/5Ha_eF5cPOU?t=452
Learn User story sizes with a puzzle of concepts and their descriptions.
Get familiar with these concepts by interacting and reflecting on their meaning.
Use this template: https://docs.google.com/drawings/d/1-6Ppz7lKqzXouwnireuGdIg0BMHVvFJmoExzhLEbkqQ/edit?usp=sharing
IMPORTANT:
- Go to File>Make a copy and work on your own copy.
- Follow the steps in the video.
1) User Stories
Consider the following Product Vision: “Build a website that allows customers to customize shoes and buy a unique pair of shoes”
Write a Product backlog with a list of User stories titles for this Vision using the format: As a <User type>, I want <something> so that I <benefit>
2) Acceptance Criteria / Split
- Prioritize: Select the most important user stories in your opinion.
- Basic Acceptance Criteria: Write basic acceptance criteria using the rule-oriented format as a checklist.
- Split: Split them using Divide and conquer and the SPIDR approach.
- Reprioritize: Once the most important stories have been trimmed, re-prioritize the list of stories as, when trimming, some of the trimmed stories should have low priority.
- Detailed Acceptance criteria: write more detailed acceptance criteria with the format that you prefer or both:
- Scenario oriented: given/when/then
- Rule oriented: checklist
3) Acceptance Criteria with Scenario oriented format
Introduction
Given the following User Stories with basic rule-oriented Acceptance criteria, Re-write the Acceptance criteria. Please select at least one of them and re-write the acceptance criteria using the format: Scenario, Given, when, then.
You can make up or invent all scenarios and alternative cases that you want beyond this short bullet list.
When there is no previous user interface, as in this case, it can sometimes be useful to draw a draft of how the user interface might look like to understand how it would be tested.
Stories to rewrite:
--------------
User Story: As a Customer, I want to customize the product color so I have a unique product
Acceptance Criteria:
- Applies only to 3 products.
- Possible colors: Black, White, red, green, blue, yellow.
- Can combine up to 3 colors.
User Story: As a Customer, I want to search for products by category so I find a product for my needs.
Acceptance Criteria:
- Search term is performed within Title, description, and category.
- Categories will be displayed in autocomplete and to select one to filter all results.
- Results are ordered by Relevance.
--------------
You can use the following partially completed example as a starting point or create your own:
User Story: As a Customer, I want to customize the product color so I have a unique product
Acceptance Criteria:
Scenario 1: Fully Customize a pair of shoes
Given: that the user is in the detail page of a customizable pair of shoes that allows all colors.
When: ...
Then: ...
Scenario 2: Restricted customization
Given: that the user is in the detail page of a customizable pair of shoes that only allows black, white, and red.
When: ...
Then: ...
Scenario 3: Not customizable shoes
Given: that the user is in the detail page of a pair of shoes that are not customizable.
When: ...
Then: ...
Scenario 4: ...
Given: ...
When: ...
Then: ...
Create a Definition of Ready with a Template. Follow the steps in the video or use these steps and template: https://www.linkedin.com/pulse/definition-ready-template-what-needs-completed-before-ignacio-paz/
Recommended Tools you can use for this workshop:
- Option 1: Free registration on StoriesOnBoard tool https://storiesonboard.com/
- Option 2: A wall, sticky notes and markers
Other Tools that you can use for User Story Mapping:
- Atlassian Jira (Requires Plugins/Apps)
- Jira Apps for User Story Map
- User Story Mapping for Jira (Good Free App)
- FeatureMap
- Mural
- Miro
Tools you can use:
- Option 1: Free registration on StoriesOnBoard tool https://storiesonboard.com/
- Option 2: A wall, sticky notes and markers
- Final version of the User Story Map: https://nachopaz.storiesonboard.com/m/YTRSXKH_6E-m1AN6jvvihw
- Your final version: Post a picture, screenshot or link of your User Story Mapping