story-mapping

Story Mapping And Why It Matters In Business

Story mapping is a simple holistic approach to using stories in agile development without losing sight of the big picture. Story mapping was first introduced by Jeff Patton in 2005 and is based on the concept of user stories, or stories that communicate product requirements from the perspective of user value

Understanding story mapping

Story mapping is an engaging and collaborative activity where everyone works toward building a product backlog on a wall.

This maintains a focus on users and what they are doing with a product, helping teams avoid becoming distracted by pointless feature arguments. Instead, stories are written that capture both user and business value

By visually mapping out these user stories, teams are also able to:

  • Create an outline of product-user interactions.
  • Determine which steps will deliver the most benefit to the user, and
  • Prioritize what should be built next.

Building a story map

Story mapping is a top-down approach that breaks the product vision into actionable steps that can be prioritized. 

To better understand this concept, think of the basic structure of a story map as being similar to a tree.

The production vision is represented by the trunk, while the large branches are goals. Smaller branches denote activities and leaves denote user stories. 

Then, follow these steps.

Step 1 – Frame the journey

Before mapping can commence, the exercise must be framed around a common goal.

In other words, what does the product do? What problem is it trying to solve? Is there a specific user or target audience? What benefits will they (or the business) receive as a result of the product being built?

Step 2 – Build the story backbone

This describes the entire user story from start to finish. For someone booking a vacation rental, the first task may be signing up for account with the stay company.

At the end of their user story, they may write a review for the homeowner or hotel.

To help define the story backbone, relevant experts should be asked to walk through the story step-by-step.

Each member of the team should also contribute to encourage conversation around the sequence and flow of each step.

Step 3 – Identify and group activities

Activities are defined as common themes that group steps in a user story.

For the individual booking a vacation, signing up for an account may involve entering personal information and opening the confirmation email.

Step 4 – Break large tasks into subtasks

It’s important to understand that most steps are probably too big to be completed in one sprint.

Therefore, they should be broken down into smaller tasks and user stories.

Cards denoting steps in the user story should be split, rewritten, and reorganised so that subtasks do not get confused or muddled.

Step 5 – Fill in the blanks

Here, the project team must test for any missing tasks by having a different user persona walk through the entire user story.

Teams must be observant, noting where user behaviour flow differs from what is displayed on the story map. 

In filling in the blanks, teams should gather as broad a range of perspectives as possible.

A UX designer will be able to offer different insights compared to a developer, for example.

Step 6 – Prioritize tasks and subtasks

This very important step involves the prioritization of tasks by moving them up or down the backbone. High-priority tasks should be kept at the top of the backbone.

Prioritization will depend on the team and their particular product. However, many businesses choose to split the map into vertical sections entitled “could”, “should”, and “must”.

Step 7 – Slice groups of tasks into iterations

By this point, the team should have a backbone up top with a full suite of user stories grouped by activity and prioritized tasks underneath.

Iterations, or a full “slice” of what a product could do, can be seen by moving through the map from left to right.

Each slice then represents a minimum viable product (MVP) that progressively adds value as development progresses.

For each slice, the team must conclude by determining what they hope to accomplish.

That is, does the release contribute to broader company goals? To answer these questions, success metrics should be defined to quantify successful user behaviour.

Story mapping examples

Event site

Imagine an event business that wants to build a website where visitors can look for fun or interesting events to attend with others.

The site will also have a members area where hosts can list and promote their events and a team of moderators will ensure events adhere to rules and regulations.

The user activities with many different steps in this example include:

  1. Participate.
  2. Host, and
  3. Moderate.

Now it is time to break down each user activity into smaller stories, otherwise known as user tasks.

The team places the user tasks under the correct activity and in an order that makes sense to the user.

  1. Participate – choose event → read event details → sign-up for event.
  2. Host – list a new event → promote event → organize event participants.
  3. Moderate – review events for compliance.

With the backbone of the story map defined, subtasks are identified and placed in vertical columns under each user task. In other words:

  1. Choose event – browse event listing page → search events by location → search events by activity type → search events by date. 
  2. Read event details – view general event overview → view detailed participant information. 
  3. Sign up for event – join participants → select and pay for membership → withdraw from event.
  4. List a new event – enter details of event → receive approval from company → receive rejection from company.
  5. Promote event – share on Facebook → share on Instagram.
  6. Organize event participants – send update → confirm time, date and location.
  7. Review events for compliance – peruse new listings → approve new event → reject new event.

Fill in the blanks

At this point, it is important to walk the map from beginning to end with various user personas to identify any missing subtasks.

As we noted earlier, teams must be on the lookout for instances where the user story differs from user behavior. 

In this case, it turns out that the different personas identified quite a few subtasks that were missed by the team.

A few examples include:

  • Choose event – browse events by those added since last user visit. 
  • Sign up for event – join event wait list. 
  • Promote event – invite other members.
  • Organize event participants – mark each participant as paid. 
  • Review event for compliance – make alterations to event for compliance.
  • List a new event – receive event improvement suggestions.

Prioritizing tasks and subtasks

Once diverse user personas have been consulted, it’s time to prioritize tasks and subtasks within each activity.

There’s no use prioritizing the activities themselves since each likely contributes to the operation of the event website.

Say for instance that under the “List a new event activity”, it was determined that the “recent event improvement suggestions” subtask should be given priority over the “rejection from company” subtask.

This, the team agreed, would give event hosts the chance to improve their listing before it was denied outright.

The team should then conclude the progress by selecting tasks from each activity that collectively form an MVP.

Key takeaways

  • Story mapping is a holistic agile methodology where user stories are considered with respect to how they contribute to the overall user experience.
  • Story mapping provides a graphical representation of product-user interactions. This helps project teams prioritize iterations according to the value they provide to the user and business.
  • Story mapping is a seven step, top-down approach which uses the analogy of a tree to break the vision of a product in smaller, actionable steps.

Connected Agile Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Read Also: Business Models Guide, Sumo Logic Business Model, Snowflake

InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: SWOT AnalysisPersonal SWOT AnalysisTOWS MatrixPESTEL

Read Next: AgileDevOpsDevSecOpsScrumLeanSprint.

Read Next: Storyboarding, Business AnalysisCompetitor Analysis, Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Main Free Guides:

Scroll to Top
FourWeekMBA