User Story Mapping

Aug 27, 20138 likes3,628 views

User Story Mapping (USM) helps teams get a common understanding of requirements from the user's perspective to facilitate backlog creation. It improves backlog quality and team communication. USM creates a map with user stories arranged in a usage flow. Each story follows the "As a <user>, I want <goal> so that <benefit>" format. Together, the mapped stories provide an overview of a product from the user experience while maintaining granular stories for planning and testing.

User Story Mapping (USM)
Manik Choudhary, PMI-ACP, CSPO, PSM-1
manikchoudhary@yahoo.com
Picture Source: Jeff Patton www.AgileProductDesign.com

Disclaimer
 These are my personal opinions on the subject and in no way represent
that of my employer.

How do you combine Design and Development ?
Product Vision Product Backlogs Product Creation
Business Model Framework
Business Model Canvas / Lean Canvas
Design Thinking
User Story
Mapping
Lean / Scrum

Software Requirements
Use Case
Scenario User Stories
IEEE 830
http://astheqaworldturns.wordpress.com/category/software-development-life-cycle-sdlc/

Software Requirements - IEEE 830 Standards
 It Shall be possible to Search for the Books
 It Shall be possible to Pay for the Books
 It Shall be possible to order the Books
 It shall be possible to check the status of
ordered Books.
http://standards.ieee.org/findstds/standard/830-1998.html
 IEEE 830 Standards describe
behavior of the software not the
behavior or goals of a user
 It focus on a checklist of
requirements rather than on the users’
Goal
 Time consuming to write and Read

Backlogs
are usually flat
You don‘t get the big
picture
Why User Story ?
Source: Jeff Patton www.AgileProductDesign.com

User Story Mapping
Why User Story Mapping ?
User Story Mapping helps teams to get a common understanding of the requirements from the user's
point of view and it facilitates the backlog creation.
 The backlog quality improves & the team wins time
 Communication within the team, with other teams and with customers improves
The Three C’s of a User Story
 Card
 Written description of the Story used for
planning and as a reminder
 Conversation
 Flesh out the details of the Story
 Confirmation
 Tests that convey the document details
and can be used to determine when a
story is complete
As a <Persona>, I want to <feature> So
that <Value>
As a Carl I want to
use my credit card to
pay for books so that
it's convenient for
me.
Test with Visa Card
Test with Master Card
Test with Expired Card
ConfirmationConversation

A Good Story is - INVEST
 Independent
 Negotiable
 Value to users
 Estimable
 Small
 Testable
As Carl I want to
use my credit
card to pay for
books so that it's
convenient for
me.
Picture Source: Jeff Patton
www.AgileProductDesign.com

Who?
 Create the map with the whole team
 Enhance and validate the map with customers (End users and business
owners) and stakeholders
Picture Source: Jeff Patton www.AgileProductDesign.com

User Story Map - On Line Grocery Shopping Store
Usage Sequence
Logon
Search for
the Items
Search for
the Items
Place a
Order
Cash On
Delivery
User
Handling
Search Order Payment
Credit Card
Vision
Priority
Add to
Basket
BACKBONEWalkingSkeleton
fromhightolow
Time
Customer
Owner
As Owner, I want to search
(Via Free Text) for the
Items so that I can quickly
find out the stock of the
items
As Customer, I want to Pay
for the ordered Items using
Cash on Delivery so that I
don't have to enter
payment data on the
internet.
Slicing

References
 http://commonsenseux.com/ia/persona-template-for-axure/
 www.AgileProductDesign.com

Thank you !!
 Manik Choudhary
 manikchoudhary@yahoo.com
 Linked In - http://www.linkedin.com/pub/manik-choudhary-pmi-acp-cspo-
psm/1/54/529

This document discusses user story mapping and provides an example of mapping out a morning routine. It explains that user story mapping helps create a shared understanding by focusing conversations on user experiences. The mapping process involves writing individual tasks or stories, organizing them into a narrative flow, exploring alternatives, distilling the map into a backbone, and slicing tasks to achieve specific outcomes. It then demonstrates this process by mapping out tasks for different goals of getting ready in the morning, either in a rush or with more leisurely time.

Story Mapping in a NutshellVersionOne

Arlen Bankston Arlen is an established leader in the application and evolution of process management methodologies such as Lean, Six Sigma and BPM, as well as Agile software development processes such as Extreme Programming (XP) and Scrum. He is a Lean Six Sigma Master Black Belt and Certified ScrumMaster Trainer. He also has twelve years of experience in product design, leveraging principles of information architecture, interaction design and usability to develop innovative products that meet customers’ expressed and unspoken needs. Arlen has led Agile and Lean deployment and managed process improvement projects at clients such as Capital One, T. Rowe Price, Freddie Mac, and the Armed Forces Benefits Association. Arlen’s recent work has centered on combining Lean Six Sigma process improvement methods with Agile execution to dramatically improve both the speed and quality of business results. He has also led the integration of interaction design and usability practices into Agile methodologies, presenting and training frequently at both industry conferences and to Fortune 100 clients.

User Story Mapping 101Martin Etmajer

The document provides an overview of user story mapping, which is a technique used to help product teams understand user needs and plan product development. It discusses the limitations of a traditional flat user story backlog and how user story mapping addresses these by visualizing the overall user journey and relationships between stories. The key steps of user story mapping involve framing the product, mapping the big picture of user tasks and activities, exploring stories in more detail, and slicing the map into prioritized product releases.

User Story Mapping Workshop (Design Skills 2016)Bartosz Mozyrko

User Story Mapping (USM) is a top-down approach of gathering "requirements" in agile environments. "A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release (from Jeff Patton's The New User Story Backlog Is a Map)."

Agile Transformation v1.27LeadingAgile

The document discusses goals for adopting agile practices like predictability, quality, early ROI, lower costs, and innovation. It then covers considerations for transformation based on organization size, dependencies between teams, and resistance to change. Finally, it outlines key elements of transformation including backlogs, teams, and working tested software and discusses governance structures with portfolio, program, and delivery teams.

User Story Mapping (2008)Jeff Patton

The document discusses a presentation on using user story mapping to build better products. The presentation aims to teach how to use a user story backlog to describe a user's experience with a product. It covers mapping user stories based on user experience, planning valuable incremental releases from the story map, and iteratively constructing software. The presentation discusses starting with user stories, mapping them based on tasks and activities, and slicing the story map into valuable product releases.

User Story Splittingtrishly

This document discusses techniques for splitting large user stories into smaller stories for an agile team. It provides examples of splitting stories by workflow, business rules, operations, data, performance, and interface. Some key techniques include focusing first on the happy path, starting with foundational capabilities like create/read, prioritizing the most important rules, and keeping the interface simple initially. Splitting stories properly allows teams to learn, adapt, and deliver working functionality in short iterations.

User stories in agile software developmentSandra Svanidzaitė, PhD, CBAP

The document provides an overview of user stories in agile software development. It discusses the agile manifesto and its focus on individuals, interactions, working software, and responding to change. It then covers what user stories are, how they are written in a "who, what, why" format, and how they provide an alternative to traditional work breakdown structures. It also discusses techniques for writing user stories like modeling user roles and trawling for requirements. The document emphasizes that both functional and non-functional requirements should be considered and that the agile team is responsible for fully understanding requirements.

User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders

User story mapping is an intuitive way to build and organize a product backlog. During this session you’ll get hands-on experience building a user story map. You’ll learn: How story mapping drives productive conversations with users and stakeholders. How to plan incremental releases of your product using minimal holistic slices that deliver value at each product release. Secrets to effective prioritization for both planning releases, and figuring out what to build next. Tactical management of your backlog as you grow your working software to releasability. The backlog building and managing strategies in this session will take you well beyond the agile basics.

Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson

To deliver the right outcomes, you need to learn your customers needs and validate your assumptions as early as possible. This means getting an early version of your product completed to start testing, validating and improving. This session will demonstrate how to combine Lean Startup and User Story Mapping techniques to determine where to start and how to learn early and often. Participants will start with a partially completed Lean Canvas to flesh out and then define a product roadmap by building a Story Map. We will use Lean Startup concepts of Minimal Viable Product (MVP) and validated learning to focus on outcome over output. Learning objectives: Understand the importance of accelerated learning and techniques to achieve it How a Lean Canvas can help shape your product vision and MVP How to build a story map to create a product roadmap How to use a story map to validate your users' journey

User Story WorkshopPeter Antman

The document contains instructions for drawing a summer meadow scene with specific elements like flowers, grass, cows, birds, and a sun. It begins with more open requirements to draw blue and red flowers with cows and birds under a sun. Then it provides closed, detailed requirements specifying the number and characteristics of each element to include in the drawing. The document discusses the difference between open and closed requirements.

Writing Good User Stories (Hint: It's not about writing)one80

Story writing and mapping.pdfSage Software Consulting, Inc.

Agile coach - roadmap and user story map Rubens Sonntag Dipl.-Ing., MSc, DIC

Story maps and personas an introMark Kilby

Story of user storyBalaji Sathram

WTF is a Product Roadmap?Fresh Tilled Soil

Introduction to user story mapping open camp editionMichael Calleia

User Stories Writing - Codemotion 2013Fabio Armani

Stefano Leli (Freelance) - Fabio Armani (OpenWare) Scrivere user stories dovrebbe essere facile...almeno in teoria. In realtà nella pratica ci troviamo troppo spesso a combattere con storie vaghe o troppo tecniche, storie che non possono essere testate o addirittura che non portano alcun valore. In questo workshop cercheremo assieme di comprendere la differenza tra requisiti funzionali e User Story, tra User Story e Use Case, mediante dei case study.

User Storiesguest446c0

The document discusses planning and estimating user stories for software development. It provides guidance on writing user stories, estimating story points, determining team velocity, prioritizing stories, and planning iterations and releases. Key points include writing stories from the user's perspective using active voice, estimating stories as a team in story points rather than hours, using velocity from past iterations to plan future work, and prioritizing stories based on business value and risk.

How to write good user storiesJose E. Rodriguez Huerta

This document discusses improving user stories by following best practices like the INVEST acronym. It explains that user stories address common requirements gathering pitfalls by focusing on delivering value to end users, using their language, and enabling prioritization and incremental development. The document provides guidelines for writing "good" user stories, including having context, value, and acceptance criteria, as well as being independent, negotiable, estimable, small in size, and testable. It also identifies potential "user story smells" to avoid.

Strategies to split user storiescpolc

This document discusses user stories (also called PBIs), which are short descriptions of a software feature written from the perspective of an end user. It provides templates and examples for writing user stories, as well as tips on splitting large stories into smaller, testable pieces. Some key points covered include writing stories that focus on the user's goal and benefit, using personas to discover needed features, and decomposing large "epic" stories until they are clear and feasible to implement.

Story writing and mappingSage Software Consulting, Inc.

User Story Splitting.pptxPaul Boos

How to Break the Requirements into User StoriesShriKant Vashishtha

The document discusses how to break down large requirements into smaller, independent user stories for agile software development. It recommends following the INVEST principles to create user stories that are independent, negotiable, valuable, estimable, small, and testable. Some patterns for splitting large stories are also described, such as breaking stories into workflow steps, major efforts, business rule variations, and operations. The goal is to create functional pieces that deliver business value iteratively in a manageable way.

Epics and User StoriesManish Agrawal, CSP®

This document discusses epics and user stories in agile software development. It defines epics as large features or requirements too big to complete in a single sprint that need to be broken down into smaller user stories. User stories are simple descriptions of features written from the perspective of the end user that follow a who, what, why template. The document provides examples of epics and user stories and guidelines for when and how to split large stories or epics into smaller independent stories that can be estimated and implemented within a sprint.

Invest In Good User StoriesCraig Brown

21 Story Splitting PatternsKent McDonald

User Story MappingStefano Leli

Scrum XP è sempre più la metodologia di riferimento per i team e alcuni concetti sono divenuti di uso comune per chiunque operi nel mondo dell’IT (sia piccole realtà sia grandi aziende). Tra questi spiccano termini come user story e Product Backlog. L’utilizzo delle user story ha sempre più spesso rimpiazzato i tradizionali documenti di specifiche funzionali e gli use case, mentre il Product Backlog è diventato lo strumento per tracciare tutto ciò che riguarda la realizzazione di un Prodotto. Eppure entrambi hanno una serie di punti deboli. In questo talk mi concentrerò da una parte sulla difficoltà di avere un quadro completo ed evoluto a partire dal Backlog che è aihme piatto e mono dimensionale e dall’altro parlerò di cosa vuol dire veramente avere un approccio iterativo e incrementale nello sviluppo di un sistema.

Lean StartupManik Choudhary

This document discusses the Lean Startup methodology. It notes that the vast majority of new products and startups fail. The Lean Startup approach was developed by Eric Ries to help startups search for a scalable and profitable business model through experimentation and customer feedback. It advocates developing a minimum viable product and using the build-measure-learn process to continually pivot based on learning. The Lean Startup principles of validating learning and innovation accounting are also summarized.

More Related Content

What's hot (20)

User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders

Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson

User Story WorkshopPeter Antman

Writing Good User Stories (Hint: It's not about writing)one80

Story writing and mapping.pdfSage Software Consulting, Inc.

Agile coach - roadmap and user story map Rubens Sonntag Dipl.-Ing., MSc, DIC

Story maps and personas an introMark Kilby

Story of user storyBalaji Sathram

WTF is a Product Roadmap?Fresh Tilled Soil

Introduction to user story mapping open camp editionMichael Calleia

User Stories Writing - Codemotion 2013Fabio Armani

User Storiesguest446c0

How to write good user storiesJose E. Rodriguez Huerta

Strategies to split user storiescpolc

Story writing and mappingSage Software Consulting, Inc.

User Story Splitting.pptxPaul Boos

How to Break the Requirements into User StoriesShriKant Vashishtha

Epics and User StoriesManish Agrawal, CSP®

Invest In Good User StoriesCraig Brown

21 Story Splitting PatternsKent McDonald

User Story Maps: Secrets for Better Backlogs and PlanningAaron Sanders

Lean Startup + Story Mapping = Awesome Products FasterBrad Swanson

User Story WorkshopPeter Antman

Writing Good User Stories (Hint: It's not about writing)one80

Story writing and mapping.pdfSage Software Consulting, Inc.

Agile coach - roadmap and user story map Rubens Sonntag Dipl.-Ing., MSc, DIC

Story maps and personas an introMark Kilby

Story of user storyBalaji Sathram

WTF is a Product Roadmap?Fresh Tilled Soil

Introduction to user story mapping open camp editionMichael Calleia

User Stories Writing - Codemotion 2013Fabio Armani

User Storiesguest446c0

How to write good user storiesJose E. Rodriguez Huerta

Strategies to split user storiescpolc

Story writing and mappingSage Software Consulting, Inc.

User Story Splitting.pptxPaul Boos

How to Break the Requirements into User StoriesShriKant Vashishtha

Epics and User StoriesManish Agrawal, CSP®

Invest In Good User StoriesCraig Brown

21 Story Splitting PatternsKent McDonald

Viewers also liked (20)

User Story MappingStefano Leli

Lean StartupManik Choudhary

MTA2 - Fatiando o produto com User Story MappingMarcello Cardoso

UNA - Eng Usa '12 - aula 03Marcello Cardoso

Tools for Remote WorkerThe Cloud Communications division of NTT Ltd.

Web Packages...Internet Marketing....Hosting webhostingguy

Site Web Developers Ltd (SWDL) is a web design and communications company established in 1999 that provides web design, development, hosting, marketing and related services. It has experience working with internationally renowned businesses and offers a range of solutions including websites, internet services, design, stationery and web tools. SWDL aims to provide high quality, cost-effective solutions while maintaining a personal approach to clients.

Lean startup & Design ThinkingManik Choudhary

The document discusses lean startup and design thinking practices. It notes that 9 out of 10 new products fail and 75% of startups fail. Lean startup focuses on experimentation to test hypotheses about customer problems and solutions. Key lean startup principles include validating learning through building-measuring-learning cycles and innovation accounting. Design thinking is a method for solving complex problems and creating new ideas. The document provides references for further reading on lean startup and its practices like customer development and the business model canvas.

Story Mapping and JIT AnalysisBen Mathews

Story maps can help prioritize product backlogs by providing more context than traditional lists. They visualize activities, tasks, and stories on a map to clearly show what is needed for minimum viable products and future releases. Just in time analysis uses simple, low-fidelity artifacts and conversations rather than extensive upfront documentation and analysis to support collaboration on large teams. Daily stand-ups, story mapping sessions, and ad-hoc discussions allow teams to analyze needs as they work rather than trying to anticipate all future questions.

Iso9001 2008 Transition Asq GovindGovind Ramu

The document discusses the key changes between ISO 9001:2000 and ISO 9001:2008 standards. It provides guidance on transition planning, impact assessment, and changes to documentation, processes, audits, and other aspects of quality management systems. Some of the main changes include greater emphasis on outsourced processes, competence of all personnel, and effectiveness of corrective and preventive actions. While the requirements have not changed, organizations should review the amendments and their implications to properly transition to the new standard.

The Business of Story MapsInternational Map Industry Association

Circular story mappingLora Hammon

Circular story mapping is a strategy that uses visual depictions to help students comprehend stories. It involves mapping out the main story elements, such as characters, settings, problems, and events, in a circular format to show how they are interconnected and the story begins and ends in the same place. This strategy aids reading comprehension by helping students visualize story components and sequence events. It is best introduced using simple stories and focusing on basic story elements for younger grades before expanding to more complex plots and abstract thinking for older grades.

User Story MappingSteve Rogalsky

User story mapping is a technique popularized by Jeff Patton that will cause you to revoke your membership in the Flat Backlog Society. A user story map allows you to see the big picture in your backlog; acts as a visual project plan; provides a technique for gathering scope and stories fast; supports better user story slicing, prioritization, and scoping; and helps you to build the right thing first. In this session you will find out what a user story map is and how to create one with your team immediately after the conference.

SkyBIM Cloud based management & real-time costing of BIM projectsSkyBIM

Collaboration is coming to the building industry. It’s a monumental shift that promises speed and efficiency. A shared building model which digitally captures ALL project information and makes it available to the entire project team throughout the lifecycle of the building is widely seen as the Next Big Thing in design and construction. The one who controls the project information will be at the center of the building enterprise. SkyBIM is a cloud-based platform to host all the information collected throughout a building's lifecycle to optimise the way buildings are designed, costed, constructed, and managed. Since projects are securely hosted in the cloud, multiple members of the project team can simultaneously collaborate on an estimate. Whether you are the architect, estimator, contractor or owner - you can view a project’s latest takeoff quantities, edit product costs, create construction assemblies and print reports. SkyBIM can provide massive automation in the real-time management and cost estimating of chain stores. Once we have configured and costed one store, the rest are essentially automatic. If you are involved with Revit projects that are chain-store based (Subway, Chipotle, Starbucks, WalMart, Woolworths, McDonald's, etc) or have a high degree of repetition, please contact [email protected]

User Story MappingSteve Rogalsky

This document discusses user story mapping, an agile technique for planning and prioritizing product development work. It provides definitions of key terms like user activities, user tasks, and user stories. It also outlines the basic steps to do user story mapping, such as gathering user tasks, grouping and ordering them, adding more detailed stories, and prioritizing and breaking work into releases. The document notes that while agile aims to be simple, it is not always easy to implement due to competing interests. It suggests user story mapping can help with decision making, delivering value, and addressing scepticism.

Design Thinking und agile Softwareentwicklung oder: Woher kommt der Backlog?Jochen Guertler

Human Centered DesignManik Choudhary

Human-centered design (HCD) is a design approach that puts human needs and experiences at the center of problem-solving. It is a collaborative, optimistic, and experimental process. HCD follows an iterative approach of understanding user needs through empathy, defining insights, ideating solutions, prototyping concepts, and validating with users. It brings together multidisciplinary teams in a creative space to tackle challenges through this process and create positive impact. The goal of HCD is to design innovative solutions by understanding human experiences.

Getting started with Microsoft Excel MacrosNick Weisenberger

Project Management Toolsostephens

This document discusses various tools and techniques for project management. It describes how tools can help with defining project plans and tasks, monitoring progress, managing budgets and risks. It discusses creating a project plan that includes tasks, deliverables, schedules, evaluations, and risks. Specific tools mentioned include MS Project, ProjectPlace, mindmapping software, and Gantt charts for task scheduling and tracking progress. Communication methods like meetings, video conferencing, reports, and websites are also discussed.

Essentials of Agile User Story Mapping at TwitterAtlassian

Agile Requirements with User Story MappingAndreas Hägglund

User Story MappingStefano Leli

Lean StartupManik Choudhary

MTA2 - Fatiando o produto com User Story MappingMarcello Cardoso

UNA - Eng Usa '12 - aula 03Marcello Cardoso

Tools for Remote WorkerThe Cloud Communications division of NTT Ltd.

Web Packages...Internet Marketing....Hosting webhostingguy

Lean startup & Design ThinkingManik Choudhary

Story Mapping and JIT AnalysisBen Mathews

Iso9001 2008 Transition Asq GovindGovind Ramu

The Business of Story MapsInternational Map Industry Association

Circular story mappingLora Hammon

User Story MappingSteve Rogalsky

SkyBIM Cloud based management & real-time costing of BIM projectsSkyBIM

User Story MappingSteve Rogalsky

Design Thinking und agile Softwareentwicklung oder: Woher kommt der Backlog?Jochen Guertler

Human Centered DesignManik Choudhary

Getting started with Microsoft Excel MacrosNick Weisenberger

Project Management Toolsostephens

Essentials of Agile User Story Mapping at TwitterAtlassian

Agile Requirements with User Story MappingAndreas Hägglund

Similar to User Story Mapping (20)

Behaviour Driven Development (BDD) - Closing the Loop on a Great Fiori UXJohn Patterson

BDD (Behavior Driven Development) involves defining requirements as structured scenarios to guide development and act as automated tests. It promotes collaboration between developers, testers, and customers. User stories and acceptance criteria written in a common language like Gherkin provide requirements, documentation, and tests. Automating tests based on these scenarios provides fast, reliable feedback to close the development loop.

Designing Outcomes For Usability Nycupa Hurst FinalWIKOLO

MarkoHurst.com :: My topic of discussion at the Feb 17 2009 NYC UPA. Even as the pace of society, business, and the Internet continue to increase, many budgets and time lines continue to decrease. To compound this issue, there is a serious disconnect between business goals, user goals, and what visitors actually do on your site. UX practitioners need a simple and efficient way to reconcile these diverse needs while taking action on their data. Join us to learn about a new method for incorporating quantitative data such as web analytics and business intelligence into your qualitative user experience deliverables: personas, wireframes, and more. This presentation will include discussions of online business models, feedback loops for ensuring cross-discipline collaboration, and ongoing revisions.

Developing User stories - Beyond the BasicsKubair Shirazee

A business case for User Storieslaurence b

User stories are short descriptions of features or capabilities that provide value to end users. They follow a standard format of "As a <role>, I want <feature> so that <benefit>" to clearly define the who, what and why. Additional details like acceptance criteria, scenarios, and assumptions help ensure user stories are independent, negotiable, valuable, estimable, small, and testable. Best practices include writing stories from the perspective of a specific user role, defining scenarios using a "Given/When/Then" structure, and using stories to guide automated testing and prevent regressions across the entire project.

Business analyst 101 program Mumbai IndiaDeepak Kadam

Business analyst Training and certification program Mumbai India At Ziphertech we have designed a Training program for students and graduates who aspire to become business Analysts. A Business Analyst requires niche skills to become successful in IT industry. Our program has been designed by veteran IT industry experts who have combined over 100 years of experience in IT business analysis. This program will be conducted by professional Business Analysts from IT industry with a minimum experience level of 15 years.This program ensures thorough training and grooming of skills for the candidate to become a professional Business Analyst. And we never forget to mention that we have trained more than 400 Business Analysts in just last 2 years. Contact us - +919004939659 for more Info

UX STRAT USA, Peter Merholz, "My Journey with Experience Strategy"UX STRAT

User Story Mapping Definitions & Basics - StoriesOnBoard.pdfStoriesOnBoard

User Story Mapping Definitions & Basics - by StoriesOnBoard Learn more & start your 14-day free trial: https://storiesonboard.com/ - How to start story mapping - Definitions - Basics - What is user story mapping? - How do you conduct a story mapping session? - What does a story map consist of? - Who created story mapping? - What is the lifecycle of story mapping? - What is a user story workshop? - Why is story mapping important? - How do you make a story map? - What is user story in Agile? - How to write a good story? - How do you use story mapping? - User goals & steps in a narrative flow - Who writes a user story? - What is user persona on the story map? - What are releases? - How to brainstorm user stories? - Why is prioritization crucial while working with user stories? - How to convert a story map into conventional product backlog? - What is MVP release? - What is the difference between epics and user stories? StoriesOnBoard is a visual and collaborative story mapping tool to prioritize the customer value sprint by sprint. Build your story map on StoriesOnBoard.com

Defining DoneDavid Rogers

UX Design Process Jason Gonzalez

The document outlines the user experience (UX) design process, including gathering user feedback through various research methods, creating user stories and flows, wireframing, prototyping, testing, and iterating based on user testing results to improve the design. Key steps involve understanding users, mapping their tasks and objectives, brainstorming solutions, and refining the design based on user research. The overall process is one of gathering insights, designing, testing, and refining the design through iterative cycles.

Jason-Phillip Park on Creating User Stories that get your Developers ExcitedCarlos González de Villaumbrosia

How do you create user stories that get your developers excited about a certain feature? Here is a breakdown of all of the components of a solid user story is and how to tell the difference between a good one and a bad one. If you want to attend any or all of our events in your area, check out our upcoming Product Management workshops here: http://www.eventbrite.com/o/product-school-7016750825 And to request a syllabus or apply to an upcoming course visit our website: https://www.productschool.com

User Storiesscornelius

Art of Writing in Agile : STC Summit 2017Shikha Saxena

Build Services that Fit: Product Discovery Lessons LearnedTremis Skeete

Business Analyzopedia - Your Pocket Gita for Business AnalysisDEEPRAJ PATHAK

Scrum - Requirements and User StoriesUpekha Vandebona

This document discusses how requirements are handled in Scrum projects using user stories. It explains that in Scrum, requirements are handled through ongoing conversations between stakeholders and the development team, rather than being fully defined upfront in documentation. User stories are used as placeholders to represent requirements at varying levels of detail and promote these conversations. The document outlines best practices for writing effective user stories using the "INVEST" criteria of being Independent, Negotiable, Valuable, Estimatable, Small, and Testable.

Vijayasarathy_Ranganathan-Portfolio-Apr2022.pdfVijayasarathy Ranganathan

The document provides details about Vijayasarathy Ranganathan's experience and qualifications. He has over 15 years of experience in user experience design and research. He has led teams and worked with various companies to deliver user experience solutions. Some of his roles and responsibilities include designing frameworks, conducting user research, developing prototypes, and validating designs. The document also lists some of his recent key research engagements and case studies with organizations like the World Bank and Walmart.

Stuart Hilton CX Portfolio-print 2Stuart Hilton

The document outlines opportunities to improve Southern Cross's customer experience by enabling easier plan comparisons, improving self-service capabilities, explaining healthcare fundamentals authoritatively, and formalizing needs analysis. It describes customers' journeys through exploring options, buying insurance, onboarding, claiming, and changing plans. Customers feel overwhelmed by information and lack of control or understanding of processes. The document advocates addressing issues around business rules and processes to benefit both customer retention and managing policies.

Stan Gaidar: How far can you go improving user experience with AI? Lviv Startup Club

Writing Effective User StoriesJaneve George

Growth Hacking with Lean UXJohn Rockson

The document discusses how to use Lean UX principles for growth hacking. It advocates quickly testing assumptions through user interviews, mockups, and prototypes rather than waiting until after launch. Some key Lean UX tools mentioned include user research, user needs, user personas, user journeys, prototypes, and validation after launch through A/B testing and surveys. The document provides examples of how to generate user needs from research and create user personas. It also outlines a typical Lean UX process and discusses how content marketing, virality, outreach, and having a great product are major growth levers that can be optimized through Lean UX.

Behaviour Driven Development (BDD) - Closing the Loop on a Great Fiori UXJohn Patterson

Designing Outcomes For Usability Nycupa Hurst FinalWIKOLO

Developing User stories - Beyond the BasicsKubair Shirazee

A business case for User Storieslaurence b

Business analyst 101 program Mumbai IndiaDeepak Kadam

UX STRAT USA, Peter Merholz, "My Journey with Experience Strategy"UX STRAT

User Story Mapping Definitions & Basics - StoriesOnBoard.pdfStoriesOnBoard

Defining DoneDavid Rogers

UX Design Process Jason Gonzalez

Jason-Phillip Park on Creating User Stories that get your Developers ExcitedCarlos González de Villaumbrosia

User Storiesscornelius

Art of Writing in Agile : STC Summit 2017Shikha Saxena

Build Services that Fit: Product Discovery Lessons LearnedTremis Skeete

Business Analyzopedia - Your Pocket Gita for Business AnalysisDEEPRAJ PATHAK

Scrum - Requirements and User StoriesUpekha Vandebona

Vijayasarathy_Ranganathan-Portfolio-Apr2022.pdfVijayasarathy Ranganathan

Stuart Hilton CX Portfolio-print 2Stuart Hilton

Stan Gaidar: How far can you go improving user experience with AI? Lviv Startup Club

Writing Effective User StoriesJaneve George

Growth Hacking with Lean UXJohn Rockson

More from Manik Choudhary (6)

Design thinkingManik Choudhary

Design thinking is a method for solving complex problems and creating new ideas that combines multidisciplinary teams, a creative space, and an iterative approach. It involves empathizing with users to understand their needs, defining the problem, ideating potential solutions, prototyping ideas, and validating solutions with users. The process is iterative, with learnings applied between each stage to develop innovative and user-centered solutions.

School 2 work_prototypeManik Choudhary

The document describes two prototypes created for ideas to redesign the school-to-work transition: a mentorship program and industrial training. The mentorship program prototype uses a storyboard to show a student getting career guidance and mentorship from an industry professional assigned through a new program between his college and company. The mentor provides resources and assigns monthly tasks to review the student's progress. The industrial training prototype also uses a storyboard format. It depicts students applying for and going on a paid month-long training program with a partner company to gain practical experience to complement their academic learning. Feedback is solicited on how to improve the prototypes, particularly around user interfaces for applying and tracking progress in the programs.

School 2 work_ideationManik Choudhary

The document discusses ideas for improving the school-to-work transition for students in India. It identifies insights such as the need for career mentorship, industrial exposure, family support, and access to learning materials. Three key ideas are proposed: 1) A mentorship program where industry leaders provide career guidance and feedback to students. 2) Developing a culture of creativity and innovation by providing support for prototyping ideas and learning from failures. 3) Encouraging industrial training so students gain practical skills and can apply academic theory. The ideas aim to better prepare students for their careers by addressing gaps in experience, support, and skill development.

Customer development approachManik Choudhary

The document discusses the customer development approach for startups. It notes that most startups fail and outlines lean startup principles like validating learning and building-measuring-learning. The customer-problem-solution hypothesis is presented as a way to test if customers have a problem, would buy a solution, and buy from that startup. Methods like lean canvas and customer development are referenced as ways to systematically test plans and get outside the building to learn from customers.

School 2 workManik Choudhary

Raj is a 23-year-old unmarried male who recently completed his BE in electric and electronics and a PG in thermal power. He enjoys swimming, playing cricket and electronic gadgets. He will soon begin work as an assistant manager in the power sector. The document summarizes Raj's interview and identifies insights about his experiences. It determines that Raj needs career mentoring, industrial exposure while studying, family support and access to better learning materials and tools in order to continuously improve, gain practical knowledge, sustain himself financially and emotionally, and develop expert domain knowledge. The problem statement is that Raj requires ways to access these things as he enters the workforce.

Design thinking action labManik Choudhary

This document outlines a design thinking process to redesign student lockers at a large public high school. It includes personas for 5 user groups - three students of different ages and sexes, a security guard, and a locker manufacturer. For each persona, it lists collecting an empathy map to understand their perspectives. The design thinking process then involves brainstorming how might we statements to define problems, ideating potential solutions, prototyping top ideas, and validating a final solution.

Design thinkingManik Choudhary

School 2 work_prototypeManik Choudhary

School 2 work_ideationManik Choudhary

Customer development approachManik Choudhary

School 2 workManik Choudhary

Design thinking action labManik Choudhary

Recently uploaded (20)

Image processinglab image processing image processingRaghadHany

Procurement Insights Cost To Value Guide.pptxJon Hansen

Complete Guide to Advanced Logistics Management Software in Riyadh.pdfSoftware Company

Explore the benefits and features of advanced logistics management software for businesses in Riyadh. This guide delves into the latest technologies, from real-time tracking and route optimization to warehouse management and inventory control, helping businesses streamline their logistics operations and reduce costs. Learn how implementing the right software solution can enhance efficiency, improve customer satisfaction, and provide a competitive edge in the growing logistics sector of Riyadh.

"Rebranding for Growth", Anna VelykoivanenkoFwdays

2025-05-Q4-2024-Investor-Presentation.pptxSamuele Fogagnolo

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Automation Hour 1/28/2022: Capture User Feedback from AnywhereLynda Kane

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

Salesforce AI Associate 2 of 2 Certification.docxJosé Enrique López Rivera

Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots. 📕 Here's what you can expect: - Modeling: Build end-to-end processes using BPMN. - Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes. - Operating: Control process instances with rewind, replay, pause, and stop functions. - Monitoring: Use dashboards and embedded analytics for real-time insights into process instances. This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes. 👨‍🏫 Speaker: Andrei Vintila, Principal Product Manager @UiPath This session streamed live on April 29, 2025, 16:00 CET. Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

"Client Partnership — the Path to Exponential Growth for Companies Sized 50-5...Fwdays

Mobile App Development Company in Saudi ArabiaSteve Jonas

EmizenTech is a globally recognized software development company, proudly serving businesses since 2013. With over 11+ years of industry experience and a team of 200+ skilled professionals, we have successfully delivered 1200+ projects across various sectors. As a leading Mobile App Development Company In Saudi Arabia we offer end-to-end solutions for iOS, Android, and cross-platform applications. Our apps are known for their user-friendly interfaces, scalability, high performance, and strong security features. We tailor each mobile application to meet the unique needs of different industries, ensuring a seamless user experience. EmizenTech is committed to turning your vision into a powerful digital product that drives growth, innovation, and long-term success in the competitive mobile landscape of Saudi Arabia.

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Network Security. Different aspects of Network Security.gregtap1

Learn the Basics of Agile Development: Your Step-by-Step GuideMarcel David

Automation Dreamin': Capture User Feedback From AnywhereLynda Kane

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including: -Artificial Intelligence Market Overview -Strategies for AI Adoption in 2025 -Anticipated drivers of AI adoption and transformative technologies -Benefits of AI and Big data for your business -Tips on how to prepare your business for innovation -AI and data privacy: Strategies for securing data privacy in AI models, etc. Download your free copy nowand implement the key findings to improve your business.

Image processinglab image processing image processingRaghadHany

Procurement Insights Cost To Value Guide.pptxJon Hansen

Complete Guide to Advanced Logistics Management Software in Riyadh.pdfSoftware Company

"Rebranding for Growth", Anna VelykoivanenkoFwdays

2025-05-Q4-2024-Investor-Presentation.pptxSamuele Fogagnolo

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

Automation Hour 1/28/2022: Capture User Feedback from AnywhereLynda Kane

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

Salesforce AI Associate 2 of 2 Certification.docxJosé Enrique López Rivera

Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

"Client Partnership — the Path to Exponential Growth for Companies Sized 50-5...Fwdays

Mobile App Development Company in Saudi ArabiaSteve Jonas

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Network Security. Different aspects of Network Security.gregtap1

Learn the Basics of Agile Development: Your Step-by-Step GuideMarcel David

Automation Dreamin': Capture User Feedback From AnywhereLynda Kane

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

User Story Mapping

1. User Story Mapping (USM) Manik Choudhary, PMI-ACP, CSPO, PSM-1 [email protected] Picture Source: Jeff Patton www.AgileProductDesign.com

2. Disclaimer  These are my personal opinions on the subject and in no way represent that of my employer.

3. How do you combine Design and Development ? Product Vision Product Backlogs Product Creation Business Model Framework Business Model Canvas / Lean Canvas Design Thinking User Story Mapping Lean / Scrum

4. Software Requirements Use Case Scenario User Stories IEEE 830 http://astheqaworldturns.wordpress.com/category/software-development-life-cycle-sdlc/

5. Software Requirements - IEEE 830 Standards  It Shall be possible to Search for the Books  It Shall be possible to Pay for the Books  It Shall be possible to order the Books  It shall be possible to check the status of ordered Books. http://standards.ieee.org/findstds/standard/830-1998.html  IEEE 830 Standards describe behavior of the software not the behavior or goals of a user  It focus on a checklist of requirements rather than on the users’ Goal  Time consuming to write and Read

6. Backlogs are usually flat You don‘t get the big picture Why User Story ? Source: Jeff Patton www.AgileProductDesign.com

7. User Story Mapping Why User Story Mapping ? User Story Mapping helps teams to get a common understanding of the requirements from the user's point of view and it facilitates the backlog creation.  The backlog quality improves & the team wins time  Communication within the team, with other teams and with customers improves The Three C’s of a User Story  Card  Written description of the Story used for planning and as a reminder  Conversation  Flesh out the details of the Story  Confirmation  Tests that convey the document details and can be used to determine when a story is complete As a <Persona>, I want to <feature> So that <Value> As a Carl I want to use my credit card to pay for books so that it's convenient for me. Test with Visa Card Test with Master Card Test with Expired Card ConfirmationConversation

8. A Good Story is - INVEST  Independent  Negotiable  Value to users  Estimable  Small  Testable As Carl I want to use my credit card to pay for books so that it's convenient for me. Picture Source: Jeff Patton www.AgileProductDesign.com

9. Who?  Create the map with the whole team  Enhance and validate the map with customers (End users and business owners) and stakeholders Picture Source: Jeff Patton www.AgileProductDesign.com

10. User Story Mapping – How it looks?

11. User Story Map - On Line Grocery Shopping Store Usage Sequence Logon Search for the Items Search for the Items Place a Order Cash On Delivery User Handling Search Order Payment Credit Card Vision Priority Add to Basket BACKBONEWalkingSkeleton fromhightolow Time Customer Owner As Owner, I want to search (Via Free Text) for the Items so that I can quickly find out the stock of the items As Customer, I want to Pay for the ordered Items using Cash on Delivery so that I don't have to enter payment data on the internet. Slicing

13. References  http://commonsenseux.com/ia/persona-template-for-axure/  www.AgileProductDesign.com

14. Thank you !!  Manik Choudhary  [email protected]  Linked In - http://www.linkedin.com/pub/manik-choudhary-pmi-acp-cspo- psm/1/54/529

User Story Mapping

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to User Story Mapping (20)

More from Manik Choudhary (6)

Recently uploaded (20)

User Story Mapping