User Story Mapping

Picture yourself trying to assemble a complex piece of furniture without the visual instruction manual - just a long list of steps. Frustrating, right? That's exactly how many teams feel when working from a flat product backlog. They have lists of features and requirements, but they've lost sight of the complete customer journey.

That's where user story mapping comes in. It helps us see the forest before getting lost in the trees.

The Power of Narrative Flow in Product Discovery

User story mapping transforms how teams approach product discovery. Rather than diving straight into features, it helps you visualize the complete journey a customer takes with your product, from beginning to end. This focus on customer centricity ensures you're building features that truly matter.

As Jeff Patton, who pioneered user story mapping, explains, traditional flat backlogs are like trying to understand a book by reading a list of sentences in random order. Sure, all the content is there, but the story—the user's journey—gets lost.

"User story mapping is a facilitated, curated conversation that brings everyone along for the journey. It's an opportunity for the product manager to brain dump their insights (who is deep in this stuff day in, day out) and get it into the minds of the team who are about to deliver on it." - Nicholas Muldoon, Co-Founder and CEO, Easy Agile

Creating Your First User Story Map

Let's walk through creating a user story map for a streaming service like Netflix or Apple TV. We'll see how their teams might map out the user experience of watching a movie.

Step 1 - Start with the Big Picture

‍

Begin by identifying the major activities your users go through - what Jeff Patton calls the "backbone" or "narrative flow" of your story map. Think of these as the chapter titles in your user's story.

For our streaming service example, the backbone might look like this:

• Select movie
• Purchase movie
• Watch movie
• Review/recommend movie

‍

🎯 Team Exercise: Gather your team and ask, "What are the major steps our users take to accomplish their goal?" Write each step on a card or sticky note, arranging them left to right in chronological order.

Step 2 - Add User Tasks

Now comes the rich detail. Under each major activity, add the specific tasks users need to complete. These become your user stories.  The key is to maintain focus on user value rather than technical implementation.

In the above example, these could be your user stories for the "Select movie" activity:

• Free text search
• Browse by genre
• Browse by recent addition
• Browse by most popular
• Browse by most popular by genre
• Browse by recent addition by genre

💡 Pro Tip: Write these tasks from the user's perspective. Instead of "implement search functionality," write "search for specific movies."

‍

Step 3 - Master Backlog Prioritization

Here's where user story mapping truly shines compared to flat backlogs. You'll organize your stories both horizontally (in sequence) and vertically (by priority). This approach helps with both feature prioritization and sprint planning.

Horizontal: Organize stories left to right in the sequence users would naturally perform them. 

Vertical: Arrange stories from top to bottom in order of priority, by value to the user. You can identify the value through conversations with users, analytics on usage patterns, or another form of insight appropriate for your product.

Think of it like building a house. The foundation (must-haves) comes first, then the walls (should-haves), and finally the decorative touches (nice-to-haves).

Priority Framework: 

HIGH (Must have)

• Core functionality essential for basic user journey
• Critical user needs identified from research
• Example: Basic search, Movie playback, Payment processing

MEDIUM (Should have)

• Important features that enhance user experience
• Validated user desires from feedback
• Example: Genre filtering, Recommendations, Ratings display

LOW (Nice to have)

• Additional features for delight
• Potential future enhancements
• Example: Social sharing, Advanced recommendations, Multiple watch lists

‍

Step 4 - Identify Your Releases

With your map laid out, draw horizontal lines to slice your map into releases. Each slice should represent a complete, valuable user experience.

Facilitating User Story Mapping Sessions

Running an effective user story mapping session requires more than just following the steps above. Whether your team is co-located or distributed across time zones, here's how to make these sessions productive and engaging:

Pre-Session Checklist

• Invite the right people (product owner, developers, designers, subject matter experts)

• Prepare customer research insights and data 

• Set up physical or digital collaboration space

• Define clear session objectives 

• Schedule adequate time (typically 2-4 hours for initial mapping)

During-the-Session Checklist

• Start with customer context (share research findings, personas) 

• Keep focus on user's perspective 

• Document questions and assumptions 

• Take photos/screenshots of work in progress 

• Capture action items and decisions

User Story Mapping For Co-Located Teams

Make sure the physical space is well-equipped for the perfect user story mapping session.

• Large wall space or whiteboard
• Plenty of sticky notes in different colors
• Markers for everyone
• Space for team movement and discussion

User Story Mapping For Remote Teams

Many teams often need to conduct user story mapping sessions remotely. While the principles remain the same, the execution requires some additional consideration:

1. Digital Workspace:
   • Choose collaborative tools like Easy Agile TeamRhythm
   • Set up template beforehand
   • Ensure everyone has access and basic tool familiarity
2. Engagement Techniques:
   • Use smaller breakout rooms for detailed discussions
   • Leverage digital voting for prioritization
   • Use timer-based activities to maintain energy
   • Schedule shorter sessions with clear breaks
   • Record sessions for team members in different time zones

Making Remote User Story Mapping Work for You

During the pandemic, Lyft turned to Easy Agile TeamRhythm’s remote user story mapping to keep their teams connected and focused while working from home. This tool made it easy for their distributed teams to collaborate, visualize customer journeys, and stay on top of priorities—even with everyone apart.

The result? A 20% boost in efficiency and smoother, more aligned teamwork. It’s a great example of how the right tool can make remote work feel a lot less remote.

Ready to try it? Let’s map your team’s success with Easy Agile TeamRhythm!

Common Pitfalls to Avoid

1. "We're losing the big picture"

Solution: Keep your backbone visible at all times. Regularly step back and walk through the complete user journey.

2. "Technical discussions are derailing us"

Solution: Create a "parking lot" for technical discussions. Focus first on the user's journey, then tackle implementation details in separate sessions.

3. "Remote participants aren't engaging"

Solution: Use round-robin techniques to ensure everyone contributes. Create explicit opportunities for input from remote team members.

4. "Our map is becoming outdated"

Solution: Schedule regular review sessions. Make updating the map part of your sprint ceremonies.

Keeping Your Story Map Alive

Your user story map shouldn't be a one-time exercise that gets filed away. It should evolve as your understanding of users deepens. Keep it alive and relevant by:

1. Making it visible

• Display it prominently in your team space
• Keep it accessible in your digital tools
• Reference it in planning sessions

2. Updating regularly

• Add new insights from customer feedback
• Adjust priorities based on learnings
• Mark completed items
• Note changes in user needs or behavior

3. Using it for alignment

• Reference during sprint planning
• Share with stakeholders
• Use for onboarding new team members

Measuring Success

Finally, look for these indicators to know if your story mapping is effective. Special props to you and the team if you nail them all.

✓ Team members naturally reference the map during discussions 

✓ Customer feedback aligns with your prioritization 

✓ Releases deliver coherent user experiences 

✓ Reduced scope creep and feature bloat 

✓ Improved team alignment on priorities 

✓ Better sprint planning sessions

Remember, user story mapping isn't about creating a perfect document - it's about fostering better conversations about user needs and ensuring we're building the right things in the right order.

‍

Want to dive deeper into building customer-centric products? Download our free ebook "Understanding Customer Value in Agile" to learn:

• How to escape the "build trap" and focus on real customer outcomes
• Practical techniques for understanding your customers deeply
• Frameworks for capturing and acting on customer insights
• Step-by-step guidance for creating meaningful personas and journey maps
• A concrete 30-60-90 day plan to transform how your team understands and delivers customer value

Download your free copy here and start your journey toward truly customer-centric agile development.

‍

What is User Story Mapping? And more importantly, WHY would you want to run a story mapping session with your team?

Let’s start off by talking about the origins of User Story Mapping.

It’s now a common practice in agile software development, but it wasn’t always that way.

If you have experience with a Scrum or Kanban backlog, you've likely run into the dreaded flat backlog.

Why Story Mapping

In its simplest form, a flat product backlog is a laundry list of stuff 'to do' that will ultimately provide some form of value to your users/customers. At least we hope so.

Many of us have contributed to making these backlogs longer and longer, and they inevitably become overwhelming.

Regardless of whether the team pulls work from the backlog one-by-one or groups it into sprints, prioritizing work in a flat backlog comes with its challenges.

The flat backlog is a 2 dimensional view. It’s like a shopping list, which doesn’t provide context for the work.

Enter, the User Story Map! The concept of a User Story Map was born out of a desire to kill the flat backlog and create a more holistic, customer centric overview of our work.

A user story map is a visualisation of the journey a customer takes with a product, and includes the activities and tasks they would typically complete.

Usually conducted at the beginning of a Project, a user story mapping session is done with the sole purpose of creating a shared understanding amongst the team of who your customers are and how you should focus your time working on stories that provide the most value for them.

You can do this on a whiteboard with sticky notes, or you can do it in Jira using our app, Easy Agile TeamRhythm.

How to build a user story map

To create a visualisation of the journey a customer takes with a product, start by identifying each stage, and then list the activities and tasks the customer would typically complete for each.

Next, begin to associate each item of work in the backlog with its corresponding touchpoint in the customer journey.

At this point in a User Story Mapping session, a matrix should begin to emerge, containing a list of tasks or stories to which the team has committed to delivering, organized according to the steps in the customer journey.

From there, the map is divided into the time blocks the team uses to plan their work. For example, in sprint 1, the team might commit to 5 user stories, which are attached to 3 epics.

This helps build understanding of how progress will be made against larger pieces of work.

Why user story mapping is better than a flat backlog

Connecting the work in the backlog to the customer journey in this way begins to answer key questions like:

• WHY are we building this?
• WHO are we building this for?
• WHAT value will it provide them?
• WHEN do we expect to deliver this?

User story mapping essentially converts the 2D flat backlog in a three-dimensional view, because it gives us a way to say, “ok I’m currently working on building this user story, and I can visualise what piece of the customer journey this will be directly impacting AND we know when it will be delivered.”

Also, by putting the focus on the user, a story map ensures that the backlog contains work that add real value for the customer by helping them achieve their goals.

How to run a user story mapping session

Now that you have a better understanding of the value of a User Story Map, let's look at how to create one. First, you’ll need to set up a Story Mapping session with your team.

But whatever you do, don’t make it an open invite. This is really important, because if you don’t have the right people in the room then it won’t be effective.

People you could consider inviting are:

The product owner for the team

• a tech lead
• a user experience designer
• a marketing lead
• a data analyst and,
• someone from customer support

It’s also important to set some ground rules for the session.

There should be one person facilitating the session. A good practice is to involve a Product Manager from another team to run the session.

Depending on the scope of the story mapping session you may want to take a whole day or spread it out over a couple of days.

The scope all depends on how big your team is and how many user stories you need to add to your map.

There should be no phones or laptops out except for the facilitator.

Also, everyone in the room should be familiar with the user stories being discussed.

Now that you know the benefits of a user story map and what to consider when setting up the mapping session with your team, start thinking about who you can invite to participate in and facilitate the session.

Backlogs are so full of potential, right? Ideas and possibilities for your product to become bigger and better than ever before.

But when you’ve got more than a few items on your list, backlogs are also overwhelming.

Without some kind of clear structure or prioritization, your team won’t know what to work on first.

They might work on whatever they feel like, whatever’s easiest, or most interesting, or not do anything at all.

You need a way to figure out what you should work on first. Not only that, but you need to make sure that what you’re doing delivers value to customers, makes sense for each release, fits into the bigger picture of your organization’s goals.

That’s where user story mapping comes in.

What is user story mapping?

User story mapping is a useful way to organize and prioritize your user stories so that you can schedule your work and design your releases.

It helps you visualize the customer’s journey through your product from start to finish, including all the tasks they’d normally complete along the way.

What’s a user story mapping session?

User story mapping is usually done in sessions over 1-2 days where you bring key people together in the same room.

During these sessions, your product manager (and sometimes other stakeholders) shares their customer insights with the team, who also share their ideas for the product.

Together, you brainstorm user stories, unpack the steps in your customer journey, list out any current issues, and put these onto a user story map. Your user story mapping session gets everyone on the same page about what needs to happen.

What’s a user story map?

A user story map is the artefact or visual board you produce as a result of a user story mapping session.

Your teams will refer to this map throughout each sprint to make sure they’re on schedule, coordinate dependencies, and keep sight of the big picture.

What’s a user story?

In order to understand what a user story map is, it’s important to take a step back and define one of the key components: the user story.

A user story is a goal or outcome that the user or customer wants to achieve. Usually, you’ll write user stories like this:

“As a [persona type], I want to [action] so that [benefit].”

A user story should be the smallest unit of work that can deliver value back to the customer.

You might also consider a user story to be a task that’s written from the user or customer’s perspective. User stories are usually added to your backlog, and from there, you can arrange and prioritize them, and plot them on a user story map so that they’re scheduled to a release or sprint.

Read more about user stories in our blog: How to write good user stories in agile software development.

What does a user story map look like?

User story mapping is traditionally done on a physical story mapping board:

But increasingly, companies are doing their story mapping digitally. If you use Easy Agile User Story Maps, yours might like more like this:

Whether you do your user story mapping physically or digitally, you’ll see both approaches have a few things in common:

• A backbone (the row along the top of the sticky notes), often consisting of epics
• Cards or sticky notes with user stories under each item in the backbone
• These stories are sequenced vertically from most important (to the customer) at the top, to least important at the bottom
• Horizontal cut lines or swimlanes define where your releases or sprints start and stop

(Psst: read more in our blog, Anatomy of an agile user story map.)

What’s involved in a user story mapping session?

A user story mapping session involves discussing and planning all the parts that make up your story map:

1. Your team will get together and decide on the backbone - the big steps that make up your user journey.
2. Next they’ll brainstorm user stories - all the little steps that make up the user journey and any issues (bugs or ideas) and add them to the backlog.
3. They’ll organize these stories under the backbone item they’re associated with.
4. Next they’ll discuss and estimate the work involved in each user story, assigning story points.
5. After that, your team can add cut lines to mark out what they’ll deliver and when - either by sprint or release. At this point, you might shuffle some stories around if it makes sense for the user to get them in the same release.
6. If everyone’s happy with the plan, the story map is done (for now) and it’s time for your team to start the first sprint.
   

That seems like an awful lot of effort. So, what’s the point?

What’s the point of user story mapping?

User story mapping benefits both your customers and your team.

Customers get more value delivered, sooner

helps you understand what your customers want. Because the focus is on the customer journey and what tasks they’d need to complete in order to use your product, it helps you prioritize work that’ll help fill in the gaps for customers and deliver value to them.

Teams prioritize and collaborate better

A three-dimensional view helps with prioritization because your team can see what user stories should be grouped within a release to deliver a new experience for users. For example, adding the ability to customize your profile isn’t all that meaningful unless you have a community aspect where users can view other profiles and/or interact with one another. User story mapping helps you fit all the pieces together - and make sure you can realistically deliver them within the sprint or release.

Plus, you can more effectively plan your work and collaborate as a team with your user story map. That’s because you can see the big picture and full customer journey before you start the work.

For more insights, check out our blog on why user story mapping.

What’s the alternative to user story mapping?

If you haven’t done user story mapping until now, you’ve likely been using another method to understand customer requirements and plan/prioritise your work.

The most common approach is known as the “flat backlog”. Essentially, this is a task list that’s ordered from highest to lowest priority, and might be broken up by cut lines for sprints or version releases. The flat backlog is simple (it’s basically a to-do list) but if you have a complex product, lots of teams working on it, dependencies, and a massive, ever-changing backlog… you’re going to need something more robust so that you don’t lose sight of your goals, customer-focus, and priorities.

Speaking of alternatives, check out this little story from one of our customers…

What user story mapping can do for teams

"Our teams were looking for an alternative view to the standard Jira backlog/board view, which doesn't lend itself to organizing and grooming massive backlogs with lots of epics.

The Easy Agile User Story Maps app allows our teams to better organize their work. The user interface is logical, and product owners (who are usually non-technical folk) like the layout of cards in columns under their respective epics.

This vertical view seems to foster better communication doing planning meetings and does a great job of providing a visualization of what comes next."

- Christopher Heritage, The Atlassian Team @NextEra Energy

So, as you can see from this example, a lot of teams start with flat backlogs or board views, but find that they outgrow this as their backlog gets bigger.

How user story mapping can upgrade your flat backlog

What makes user story mapping different from the flat backlog is that it has a whole other element. It’s not flat, but more three-dimensional.

You’ve got the list of activities/tasks, but they’re first sorted by how they impact the customer journey. Only then are they prioritized and broken up by when they’re being released.

User story mapping is a little more complex to set up than the flat backlog, but it makes the work more meaningful, customer-focused, and impactful. With a user story map, you can see the big picture and collaborate on it.

We talk more about this in our blog, The difference between a flat product backlog and a user story map.

Try user story mapping inside Jira

Want to know the best way to understand what user story mapping is?

You can’t learn how to ride a bike by reading about it. And you can’t *really* learn what user story mapping is without doing it and experiencing the benefits firsthand.

So, give it a try!

If your team uses Jira for project management and workflows, you can get an add-on that helps you turn that flat backlog into a three dimensional user story map.

Easy Agile User Story Maps for Jira creates the X-axis so you can add your customer journey backbone and organize your stories to fit into this journey. That way, your team gets the big-picture view of what they’re working on, and they can prioritize tasks to deliver maximum value to your customers, sooner.

Best of all, you can do all your user story mapping inside of Jira so that it’s digital, collaborative, and constantly available to your team - even if they’re working remote/distributed. And since it fits in with your existing backlog, you can hit the ground running with pre-filled user stories. In other words, you can expect to save a whole bunch of time.

You can get started with Easy Agile User Story Maps for Jira, with a FREE 30-day trial today or check out the demo here.

Try now

Hopefully, you’ll find it just as useful as our customers…

We’ve found that Easy Agile User Story Maps brings the team together in one room. As a result, we find ourselves mapping more as a group, which creates a common understanding. Since using the add-on, we’ve been able to speed up planning and more efficiently conduct large story mapping exercises.

- Mike Doolittle, Product Director @Priceline

Since using Easy Agile User Story Maps, we’ve improved our communication and team alignment, which has helped give us faster results.

- Casey Flynn, Distribution Forecast Analyst @adidas

Easy Agile User Story Maps has helped us visualize our workload and goals, as well as speed up our meetings. We love the simplicity!

- Rafal Zydek, Atlassian Jira and Confluence Expert Administrator @ING Tech Poland

With Easy Agile User Story Maps, we find it much easier to use and navigate Jira. Our favorite features include the ability to drag and drop stories across the Epics, being able to view the work using FixVersion and Sprint Swim Lanes, and Excel export. We’ve been using Story Maps functionality for quite sometime now and I recommend it to other project teams, as well.

- Sathish K Mohanraj, Lean-Agile Coach @Equifax

Learn more about user story mapping

Want to learn more about user story mapping? Check out our User story mapping ultimate guide - it has everything (and we mean everything) you could possibly want to know.

We’re always happy to answer your questions. Just send us a tweet @EasyAgile or contact us if you’re not sure about what user story mapping is, how to do it, or how it could help your team.

Storytelling is an excellent way to describe anything because stories conjure detailed images. Once you create a visual association, cognitive processes leap into action to make the story in the user journey map a reality that is easy to track.

This is what the customer journey map (CJM) is all about—epic storytelling that involves comprehensive planning to capture the design process and deliver a unique customer experience.

Creating a customer journey map (also called the user journey map) involves planning a project from the user’s point of view and using personas, epics, features, user stories, and tasks. This visualization process also involves several stakeholders as user personas on the road to planning perfection.

By the end of the project, your CJM should help achieve business goals and exceed customer expectations with enough touchpoints along the way to motivate satisfaction. The process is a little like rubbing Aladdin's lamp to manifest your deepest wishes.

What is the user journey map?

In contrast to the flat backlog, the customer journey map makes the vision for your project come alive in real-time. You get to use creative storytelling to generate a magical customer experience through visual representations.

Project team members accomplish this by developing an empathy map to an almost-perfect plan from the customer’s perspective. User journey mapping captures the customer’s emotional state, which helps identify touchpoints and pain points. Teams then use these points to elevate the customer experience.

Unlike rubbing a genie’s lamp for results, you get to use convenient software to develop a service blueprint where design thinking reflects a shared vision between stakeholders.

The starting point is to anticipate customer interactions with the mobile app or other e-commerce project development story. That’s why user research is another vital element in developing the customer journey map template.

This customer journey map template should also draw valuable information from the empathy map and the experience map. An in-depth understanding of the KPIs and metrics that go into storytelling helps direct product usability through appreciating customer interactions with the product.

Customer interactions generate feedback, which leads to understanding customer's needs. Additional touchpoints can then be included or modified to build on the overall project outcomes.

Essentially, you use hierarchical storytelling on a magical customer journey map template to meet real-life expectations that resonate with the customer experience.

The customer journey mapping hierarchy

When beginning the journey to create the ideal customer experience, team members should visualize the project from the user’s current state. Once you capture the essence of the current customer perspective, you can better understand what needs to change and improve.

A simple example may be a travel app that encompasses services such as travel agent services, flight bookings, and accommodation in a geographical area (present state). The client wants to create a future state app which contains tourist activities to augment the customer experience. The basic process will then look like this:

For app customers who want a value-add experience with our travel app which is a helpful resource that provides tips on local tourist activities.

Your user journey map hierarchy involves four building blocks to meet customers’ needs:

1. Understanding user personas or buyer personas
2. Developing themes and epics to address touchpoints
3. Using steps or features to support epics and the narrative flow
4. The stories in the customer journey map

1. Understand user personas or buyer personas

The user journey map starts with defining the user personas or buyer personas as vital stakeholders in project development. These customer personas represent the top of the hierarchy, which is the starting point of the customer journey map.

A detailed visual reflection of the user persona is vital to getting your final product right. To deliver this, you need to walk through the story mapping journey from the customer’s perspective. This helps avoid the nasty consequences of inadequate planning that results in sub-optimum deliverables and unhappy teams and customers.

To understand user personas, you need to identify the various potential touchpoints in the journey and customer pain points through use cases and feedback. You’ll need to anticipate as many potential scenarios as possible from the buyer persona’s perspective.

Although the “who,” “what,” and “why” are instrumental in defining the user story, it all begins with visualizing user personas and thinking about customer behaviors, demographics, needs, and goals.

Once you define who your customer personas are, you can follow up with themes and epics to deliver on customer expectations. The epics are the heroes or heroines in this story visualization method.

2. Develop themes and epics to address touchpoints

The customer journey map positions epics at the top of the storyboard because they are vital to creating a great project.

Team leaders must consult with the client and relevant stakeholders to develop an overarching project theme, to translate into epics. Epics flow through this theme from left to right. These epics show large bodies of work broken down into smaller features which can meet continuous delivery value.

Epics are also strategic directives that begin with the current state of an issue and move the situation into a desirable future state. This epic future state is built on tactics, or features and tasks, which team members use to clarify project requirements and move toward that magical future state of project success.

Before team members can move forward, they need to get the epics right. Epics cover three fundamental foundations: user persona, product, and design requirements, which reflect visually on the user journey map.

The epics should meet several foundational requirements:

• Follow through by aligning the overall business goals with detailed buyer personas and demographics
• Broadly outline the user persona’s needs
• Meet specific customer needs by addressing touchpoints and pain points
• Include specific functions, features, and benefits
• Produce a future state ideal project

After designing your heroic epics to cover the project's primary goals, you can start breaking these into steps that integrate with the overall narrative flow of the user story.

3. Use epics for highlighting the narrative flow

Once you clearly define your epics, it’s time to generate narrower steps or features.

As your epics move from left to right, you must define each of the necessary steps to accomplish business goals. This customizable process uses epics to relay the user journey over the project duration to reflect project outcomes.

The customer journey map template also forms the basis of the ideal user story as you transition from epics to features. The features originate from the epics, which is why the epics are the heroes in this story. They “save” customers with excellent planning and deliverables.

At its most basic level, features should include the following elements:

• Deliverables that add value and support epics completion
• Generate business value by considering KPIs, metrics, customer acquisition, and retention
• Demonstrate sufficient definition for team members to follow through on time estimates and complete tasks within one to three sprints
• Team members must be able to test the results of their features
• Establish test criteria for each feature to set acceptable quality standards that meet customer expectations before moving to the next step

In short, the user acceptance criteria (UAC) in the user journey map should include a brief item value description, a feature benefit explanation, and the feature quality completion points that team members must achieve.

Only once you nail these details can you tell the user stories from the customer's perspective. Similarly, only once you complete these three fundamental building blocks in the customer journey map can you focus on user stories and business goals that include customer satisfaction and retention.

4. Begin storytelling through the user journey map

After the third step in the hierarchy of the user journey map, the actual user stories begin. This is the final step in design thinking related to the visualization of epics into manageable stories and tasks.

To state the buyer persona case, team members must understand the “who,” “what,” and “why” of the customer experience. Understanding and defining the customer personas forms the basis of user story creation, enabling delivery of the most acceptable product possible.

Developing the best story relies on creating user stories that highlight the customer experience and use cases that highlight the finer details of system performance.

In the story creation phase, team members assume the customer’s perspective to define requests. Team members can consider exploring social media to understand customer behavior and experiences to use as story inputs. User stories can also include enabler tasks to augment feature completion.

Team members typically write their user stories to complete these in short sprints. Sprint completion involves task completion for release before completing one epic and moving to the next, except where concurrent work is possible.

Ultimately, the user journey map must tell the customer’s story of how their need will be met by creating or modifying a product, process, service, or system feature. New developments must follow through on the formula of “as a…” “I want…” “so that...”

As a new Agile team member, I want to understand my and other team member's roles so that I am clear about my tasks and the responsibilities of other team members.

After generating user stories, team members can break tasks into even smaller parts to facilitate work deliverables and reduce potential churn that negatively impacts customer retention.

As the user journey map progresses, the stories should clearly outline the activities for completion, always linking these back to buyer persona goals. The smaller, granular tasks then relate to user behaviors, and the outcomes link to each step of the process to reinforce what deliverables will meet customer needs within set timeframes.

During the customer journey map, stories can be split further to accomplish greater clarity.

Bottom line: The customer journey map

Through the customer journey mapping process, you should capture the primary epics of the user journey in the story map visualization.

You will need to develop the user story map holistically and interrupt it with additions and subtractions in an iterative fashion. This iterative user story mapping process helps minimize churn as you continue to update your story as you move forward.

Once the project is done, you need to test the product on potential customers, gather customer feedback, and improve the user journey map.

The benefits of carefully planning the customer experience through a visual format are exponential.

Tell your project story with Easy Agile User Story Maps for Jira

The customer journey should highlight the ideal user experience. To do this, the user story map should incorporate the project from user personas to achieve stories with valuable touchpoints as markers along the way.

Once the visual representation is done, it should validate the service blueprint for the customer journey mapping process through the current and future states of the project.

Throughout the project, your team should create a unique user journey that delivers the ultimate customer experience and exceeds customer expectations.

Try Easy Agile TeamRhythm and Personas today to make your customers' stories come alive with magic.

The notable quote from Alistair Cockburn, co-author of the Agile Manifesto, reads, “A user story is to a use case as a gazelle is to a gazebo.” This sheds light on the immense differences between use cases vs. user stories for agile teams. They may sound similar in name, but they are very different and often used in completely different industries.

While both use cases and user stories help teams plan work and determine what’s needed to complete work, the format for how they are used is quite different. User stories are simple, short descriptions from the customer’s perspective. They are the beginning of a larger process that describes a customer's actions as they use or interact with your product. Use cases contain much more context. Creating detailed use cases is a much more in-depth process that’s designed to help teams understand how a user or customer interacts with a system. We’ll dig deeper into both of these processes below.

If you’re in agile software development, chances are you’re more familiar with utilizing user stories. In this post, we’ll dig deeper into use cases vs. user stories differences, including why today’s development teams have migrated towards user stories and why there’s still valid reason for utilizing use cases in the development process.

What’s the difference between use cases vs. user stories?

Use cases vs. user stories: What’s the difference, and how do you decide what’s best for your team and development process?

Use case vs. user story: Past and present

Use cases were the standard for many years, and they were often used in business analysis, systems analysis, software requirements, and iterative development. With the rise of agile, software projects began to favor user stories in place of use cases because they allowed for improved incremental thinking and agility.

What is a use case?

A use case is a description of each of the ways a user may want to interact with a system, a device, or a piece of equipment. They describe how the system design will respond to requests from its end-user, commonly known as an actor. These actors could be human beings or other systems.

Take an online shopping site and a food delivery service, for example. A customer placing an order or checking if a restaurant is open are two different use cases. Or, on the less technical side, consider a toaster. Say someone (the actor) only wants their bagel toasted on one side. Choosing the “bagel” toaster setting is a use case.

Use cases help teams structure all of the different functional requirements and determine the scope of the project — which means they’re full of details.

These details include:

• The goal of the use case
• Whether the actor is a human or another system
• Preconditions, or the state the system has to be in for the use case to occur
• The regular series of steps the system will take
• Alternative paths the system could take
• Postconditions — actions the system takes at the end of the use case or the various states the system could be in after the use case concludes

Take the “bagel” setting on a toaster.

• Use case title/goal: Bagel setting
• Actor/user: This is someone who likes their bagel only toasted on one side.
• Preconditions: There needs to be a “bagel” function/button.
• Regular steps/standard path: The actor cuts their bagel in half and places each half in the toaster. They push the lever down to toast the bagel. Then, they press the button titled “BAGEL” and wait for their bagel to be toasted the way they like.
• Alternative paths: The actor may forget to activate the “bagel” setting, resulting in a poor user experience.
• Postconditions: The toaster returns to its usual state (bagel setting not set).

What is a user story?

A user story is the who, what, and why of a goal or outcome that the user or customer wants to achieve. It’s the smallest piece of work that can give value back to the customer. It’s written from the point of view of the end user, often on an index card.

Here’s an example of how a user story is typically written: “As a [persona type], I want to [action] so that [benefit].”

A user story is designed to be as simple as possible, sparing the team as well as stakeholders from having to decode a lot of technical lingo. But, that doesn’t mean the process for creating a user story is easy. A lot of information is condensed into a single sentence. And before writing a user story, the team first has to identify and create their user persona and assemble all of the product requirements

Easy Agile co-founder Nick Muldoon describes user story mapping as “a facilitated, curated conversation that brings everyone along for the journey.”

A project or product developed in an agile environment will involve a lot of user stories that are each added to the product backlog. There, they can be arranged and prioritized on a user story map according to the scheduled release or sprint.

Use cases vs. user stories: The case for use cases

While use cases are far less common in agile development, they do have some advantages to consider. After all, the true spirit of agile means questioning your assumptions and trying new methods.

1. Use cases provide a summary and planning skeleton

Use cases provide anyone involved, such as managers, leadership, product owners, developers, or stakeholders, with a summary of what the system will offer. What will the system contribute to the users and the overall business? They provide a planning skeleton to help teams prioritize, estimate timing, and execute actions.

2. Use cases provide context for each requirement

The use case provides enough detail and context to ensure everyone is on the same page. It’s an agreement between team members about what the system will and won’t do.

3. Use cases provide a look ahead at what could slow work

The alternative paths portion of use cases provides an advanced look at what could go wrong. Small bottlenecks can take up a huge amount of time and money, so the sooner you can recognize and address these issues, the better.

4. Use cases provide answers for specific issues and scenarios

Use cases answer the specific questions developers or programmers could have along the way. The use case process ensures all questions about issues or possible scenarios are answered at the outset before these questions begin to bog down work or slow down a team’s progress.

5. Use cases provide a model to think through all aspects completely

The use case model ensures developers have fully thought through all aspects of development. Use cases dig into the details of user needs, system goals, possible issues, and various business variants.

Use cases vs. user stories: Bottom line

So, use cases vs. user stories? How do you decide which is better for your team? If you have a lot of experience with agile projects and working on agile teams, you know the undeniable value of user stories. They convey what the user or customer wants to achieve so that teams are always considering the needs of the user.

That said, even though use cases are a bit dated, they can provide much-needed context surrounding how a system is used. They describe how a user interacts with a system, answering many questions in advance to help manage complicated processes. Plus, it wouldn’t be very agile to discount a solution simply because you haven’t tried it before. 😉

Using Easy Agile TeamRhythm

We’re passionate about building tools that help agile teams work better together. Easy Agile TeamRhythm is designed to help product owners and development teams bring value to customers fast and frequently. Supporting user story mapping, backlog refinement, sprint planning, and team retrospectives, you can plan and manage your work right from the user story map, then come together as a team to share actionable insights that will help you work better together each time.

TeamRhythm integrates seamlessly with your agile boards in Jira for both Scrum and Kanban methodologies. Try it yourself in our sandbox demonstration; no need for a login or installation.

Whether you’re planning your first user story mapping session or you’ve got a few under your belt, it can be a little overwhelming 🤯

• What’s the process?
• Who do I need to get involved?
• Why are we even bothering with this when we have a perfectly good backlog? (Okay… it might be slightly dysfunctional, but you know...)
• Why are there sticky notes EVERYWHERE?

Most product managers and Agile teams could benefit from a deeper understanding of user story mapping so they can create a more customer-centered view of the work that needs to be done.

Plus, over the last 15 years (since user story maps started to become a thing thanks to Jeff Patton), some of the processes and terms have evolved and there are new tools and apps that can make your life a whooooole lot easier.

We’ve put together this ultimate guide with all the info you need to get up to speed on the latest user story mapping definitions, techniques, and tools. Let’s start with some basics 👇

What is user story mapping?

Here’s a super simple user story mapping definition:

User story mapping is a visualization of the journey a customer takes with a product, from beginning to end. It includes all the tasks they’d typically complete as part of that journey.

To expand on that, user story mapping takes all your user stories (across all your persona types) and assigns them to epics in the order that delivers the most value to the customer. From there, stories are prioritized and mapped to releases.

“User story mapping is a facilitated, curated conversation that brings everyone along for the journey. It’s an opportunity for the product manager to brain dump their insights (who is deep in this stuff day in, day out) and get it into the minds of the team who are about to deliver on it.”

Nicholas Muldoon, Co-Founder @Easy Agile

What isn’t user story mapping?

While user story mapping might have a few things in common with other methods, it’s not the same as journey mapping or event storming.

User story mapping vs journey mapping

Journey mapping is a UX tool that helps teams visualize the journey a customer needs to take so they can accomplish a goal. Journey maps focus on the journey for a single persona or customer, based on the persona’s specific scenario and expectations. This is useful for aligning the team, getting them focused on the user experience, and basing decisions. Unlike user story mapping, it’s focused on the user experience and the vision for the product.

User story mapping vs event storming

Event storming involves running a workshop with key business stakeholders present. The attendees write down business events (things that happen), commands (things that trigger the events), and reactions (things that happen as a result) on sticky notes. These notes are organized sequentially to map out the business processes. Unlike user story mapping, which is focused on refining the backlog to deliver a working product for the user, event storming is more high-level and done early in the product planning process.

User story mapping for agile teams

User story maps can be useful for all agile teams, whether they’re full SAFe or Kanban, but especially if they’re working on a complex product.

User story mapping is a useful technique for agile software development teams because it can help your team deliver working software and espond to change.

This fits right in with the Agile Manifesto.

And let’s not forget the number one agile principle:

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”

User story mapping puts the focus on the user, ensuring that the backlog contains stories that add real value to the customer by helping them achieve their goals. Plus, story mapping allows your team to plan and order their work so that it delivers the highest value to customers first.

Moreover, because Agile is all about embracing and reacting to change over following a concrete plan, story maps better facilitate efficient adaptation. It’s far easier to swap out sticky notes than it is to revise hefty requirements documents. This flexibility ensures that your team can swiftly adjust priorities and modify plans as new information or changes arise, maintaining alignment with Agile principles.

The anatomy of a user story map

User stories, epics, the backbone and story mapping - oh my! To break down the steps and processes involved in user story mapping down further, let’s define some of its moving parts.

User stories

A user story is a goal, from the user or customer’s perspective. It’s an outcome they want. It’s also the smallest unit of work in an agile framework with the purpose of articulating how a piece of work will deliver value back to the customer.

User stories usually follow the structure:

As a [persona type], I want to [action] so that [benefit].

For example:

Tip: it’s a good idea to focus on just one type of user/persona during your user story mapping session. If it’s your first session, choose your most ideal customer type and write our user stories that will deliver value to them. You can always come back to your other users in future.

Read ➡️ How to write good user stories in agile software development.

Epics

Stories can be associated with epics.

Epics have different meanings depending on who you talk to. But for the sake of this article, we’ll define epics as bigger, overarching stories or steps in the journey that contain user stories. An epic on its own isn’t small enough to become a work item or development task, but the stories it contains probably are.

For example, the epic “Sign up” might contain the following user stories:

• As a customer, I want to read the privacy policy before I sign up for my account so I can decide whether I trust the company with my details
• As a customer, I want to see a list of features and benefits on the sign-up page to remind me about what I’m signing up for
• As a customer, I want to sign up for an account using my Facebook login so I don’t have to remember my username or password
• As a customer, I want to sign up for an account using my email address so I can control access to my information
• And in this example, the next epic might be “Set up and customize my profile”.

The backbone

The backbone is the top row of your user story map. It outlines the essential capabilities the system needs to have.

Your backbone should show the customer journey or process from beginning to end, including all the high level activities the customer will complete while using your product. Depending on how you use your backbone and story map, it could be made up of epics.

The backbone is critical because it gives your team the “why” behind the journey, even if they’re just focused on a single step. It takes away ambiguity around what might lead up to that step and what might follow it, which gives important context for creating a smooth customer journey.

More on: The Anatomy of a User Story Map

Why do user story mapping?

The purpose of user story mapping is to make sure you understand the problem the customer has, and then find a solution to that problem.

You’ll know the answer to:

• Why are we building this?
• Who are we building this for?
• What value will it provide them?
• When do we expect to deliver this?

This will help align your teams, groom the backlog, and more quickly deliver a product that your customers want and need.

John Walpole explains the value of user stories beautifully:

“[There’s] one technique and tool which time and time again I’ve gone back to when I felt like a project maybe isn’t thoroughly understood by the team, or I’m worried that we’re going to end up shipping software that isn’t going to delight customers. This is my go-to technique. I believe it’s going to help you ship software that will delight your customers.”

Without user story mapping, there’s a much greater chance that your team will come up with complicated, non-customer-focused solutions to a problem.

User story mapping helps ensure the team is aligned around what problem the customer has, and how you, as a team, are going to try and solve that problem.

It will keep you focused on delivering the highest impact and greatest value pieces first, enabling you to iterate based on feedback.

Read ➡️ Why User Story Mapping

Benefits of user story mapping

“User story mapping is the best technique I’ve come across to gain shared understanding within an agile team. Alex Hennecke at Atlassian talked about being able to see the forest - instead of just the trees, right in front of him.”

Nicholas Muldoon, Co-Founder @Easy Agile

User-story maps are powerful tools in product development, particularly when it comes to identifying and managing risky assumptions.

Visualizing risk

User-story maps provide a visual framework that highlights potential risks. By mapping out user stories with sticky notes or digital alternatives, it's easy to pinpoint areas where assumptions might not align with real user data or technical feasibility. This visualization helps teams identify elements that could derail a project’s timeline or budget.

Prioritization and resource allocation

Once risky assumptions are identified, user-story maps allow teams to reorganize priorities effectively. Risky elements can be moved to a lower priority, ensuring that resources are allocated to ideas that offer high value with minimized risk. This strategy ensures that projects remain on track, focusing on what's realistically achievable.

Encouraging lean alternatives

Story maps encourage teams to explore lean alternatives first. By testing simpler ideas with similar value propositions, teams can validate concepts without significant investment. This approach allows for learning and iterating, reducing the likelihood of costly failures later in the development process.

Fostering collaborative problem-solving

The process of creating and updating a user-story map is inherently collaborative. It invites diverse team members to contribute insights, leading to more comprehensive risk identification and resolution strategies. By pooling knowledge, teams are better equipped to address assumptions that might otherwise go unnoticed.

Incorporating these practices into your product development cycle can help mitigate risks early, ensuring a smoother path from inception to launch.

There are so many other benefits to user story mapping too, like:

• Plan better - Seeing the user journey mapped out makes it easier for teams to see the big picture of your product and identify any risks, dependencies, and blocks ahead of time
• Greater empathy - It forces your team to see the product from your users’ perspective
• More value sooner - Frequently delivering new value to users is easier when you can order the stories based on value and map them to iterations or releases
• Realistic requirements - By breaking user stories down and visually mapping them, it’s easier to estimate work and see how all the pieces fit together
• Better cross-functional collaboration - With all the upcoming work mapped out, marketing, sales, and other teams can see when you expect to ship new features and updates so they can adjust their marketing communications and sales conversations (without asking you for daily updates)

User story mapping helps your team understand the bigger picture, the why, and the end-to-end customer journey before they dive into the what and how.

Read ➡️ Understand what your customers want with agile user story maps.

‍

The flat backlog vs user story mapping

Before we had user story mapping, we had the flat backlog. Actually, a lot of agile teams still use the flat backlog (no judgement if this is you!). So, let’s talk about what that looks like and how user story mapping has improved this practice.

Read ➡️ DEEP: The 4 Characteristics of a Good Product Backlog

What’s a flat backlog?

Essentially, it’s a to-do list. It includes all the items your team needs to do so they can provide value to your customers, ordered from most valuable to least valuable to the customer. The backlog may be split into current and future sprints to show what outputs are likely to be delivered when.

But I like our backlog!

A simple to do list might be fine if your product is simple, your team is small, and your to-do list is very short. But most products are complex, with multiple teams working on it. And most of the time, the backlog is massive (and constantly growing and changing).

Flat backlogs are complex at scale

If you’ve got hundreds of issues (or more), a flat backlog makes it impossible to see the big picture and surrounding context - which your team needs in order to refine the backlog, find dependencies, and prioritize the work into releases. It can also get pretty overwhelming!

• Specific challenges of using the flat backlog include:
• Arranging user stories in the order you’ll build them doesn’t help you explain to others what the system does
• It provides no context or ‘big picture’ around the work a team is doing
• For a new system, the flat backlog is poor at helping you determine if you’ve identified all the stories
• Release planning is difficult with a flat backlog - how do you prioritize what to build first when you’ve got an endless list?
• It’s virtually impossible to discover the ‘backbone’ of your product

User story maps were designed to overcome these challenges and restructure the backlog to add context, make it easier to prioritize, and put the focus on the customers’ needs. It introduces the X axis, with the backbone at the top to show the customer journey, and the user stories below.

When you go from a flat backlog to multiple axes, your team (and the rest of your organization) can understand what value we intend to deliver to the customer and when.

Read ➡️ The difference between a flat product backlog and a user story map.

When is user story mapping done?

So, when do you actually run a user story mapping session?

Generally, a team will collaboratively create a story map at the start of a project or product. It might be an entirely new product, or the product manager might want to pursue a new idea or feature as part of an existing product.

This involves getting subject matter experts and team members together to run a session where you look at your personas and overarching customer journey, then brainstorm ways you can provide the most value to customers. Then you’ll write user stories for each of your persona types and each step of the journey, based on their needs.

As we’ve already mentioned, it’s best to focus on one persona type per story mapping session to avoid confusion. So, start with the persona who is the best fit for your product or likely represent the largest chunk of your audience first.

Overall, the process could take several days or even several weeks, depending on the complexity of your product (and therefore, the number of steps in the customer journey) and the number of personas.

Getting the most out of User Story Mapping

Who should participate in user story mapping?

Some folks you might invite to your user story mapping party session include your:

• Subject matter experts (whether product owner, product manager, customer support team member, or someone else who interacts with the customer)
• Business owner
• Developers
• Testers
• Marketer
• UX designer
• Facilitator or Scrum Master (it’s useful if you can get another product manager to facilitate the session)

Tip: Try to keep your numbers below 10 participants. Diverse perspectives are useful, but any more than that and it can get tricky to manage and get input from everyone. All the people present should be able to contribute insights into the personas/product/business, or help estimate how long tasks will take to complete.

Mapping the user stories

Once the backbone is established (and your team agrees on the order), you can put the flesh on it. Under each item in the backbone, go the user stories (steps, processes, and details) that support that activity. This involves some brainstorming and creative thinking.

Encourage your team to imagine the different options available to the user, how they might want to experience each step in the backbone, and actions they might take. It can't hurt to do a paper prototyping session alongside your user story map to mock up ideas as you go. Or perhaps that step will come later, depending on the scenario and maturity of your team.

Sequencing

Then you can put your user stories in a sequence to deliver maximum value to the customer as quickly and consistently as possible. So, put the most important user stories at the top, and the least important ones at the bottom.

Cut lines or swimlanes

Your team will get together and discuss and estimate the work involved in each user story. After that, you can add cut lines (usually sprint or version lines) to mark out what your team will deliver and when. At this point, you might shuffle some stories around if it makes sense for the user to get them in the same release.

Read ➡️ Anatomy of an agile user story map.

Tips for successful user story mapping

Involve the right people

It can be tricky to get your team and stakeholders together. They’re busy and probably have a plate full of commitments. But it’s always worth getting everyone to set aside time and step away from the keyboard. User story mapping is important - and you’ll need input from everyone so you can:

• Brainstorm stories then prioritize and estimate them
• Get your team to commit to implementing them

Break it up

“Typically, I’d run these things to try and get as much of the planning, personas, and backbone done on day one as possible. By that point, most people are tapped out because the cognitive load is high. Then the team can go away and sleep on it. Once they’ve had time to reflect on it, they’ll come back with other ideas for user stories and thoughts about how they’d do the work before they start sequencing.”

Nicholas Muldoon, Co-Founder @Easy Agile

You don’t have to do your whole user story mapping session in one go. Depending on the size, complexity, and phase of your product, you might not be able to fit it into one day, either.

Instead, break your session up into 2-3 hour chunks and do it over several days. You might do the first session in the afternoon and the next session the following morning. This comes with a few advantages:

• It means you don’t have to get your stakeholders and teams together for an extended period
• You might find it’s a lot easier to coordinate your calendars when you split your sessions up
• It gives your team time to reflect on the initial story map (they’ll probably think of a million new things to add on day two)
• Your team can get lunch after the session is done and debrief over food and drinks 🍻🍔🍕

A single facilitator

While you DO want all your team and stakeholders at your user story mapping session, you don’t want everybody driving the discussion (too many chefs in the kitchen = not a good idea). Instead choose one person to facilitate the session. Sometimes it even works better if you can choose a product manager from another team to run things.

No phones/laptops

For in-person user story mapping sessions, only your designated facilitator is allowed their device. To avoid distractions, ask folks to leave their phones and laptops in a stack at the door. That way, your team can be fully present for all discussions.

Start with data and evidence

Before you get stuck into user story mapping, bring in relevant data and supporting evidence. All of that is great context for what's to come. And of course, you can’t do user story mapping without a clear understanding of who your users are - and what their goals, objectives, problems, and needs are.

So, create your personas before you build out your customer journeys. That way, you’ll understand how your users will engage with the product, and you’ll be able to write user stories that more accurately reflect reality.

User Story Mapping Approaches

User story mapping example

Let’s go through an example of user story mapping to help you visualize the process for your own product.

• Identify product/outcome

In this example, our product is a free online educational kids game. The outcome is for the user to find and play the game.

• List high level activities (in chronological order):
• Navigate to games website
• Log into account (or sign up if a first-time user)
• Search for game
• Choose game
• Play game
• Share with a friend or on social media
• List user stories under each activity

For example, searching for a game could include the following options:

• Free text search - As a parent, I want to search for a specific keyword so I can quickly navigate to a game
• Browse by category: age group - As a parent, I want to find an age appropriate game that my kids will easily pick up
• Browse by category: type of education - As a parent, I want to find a game that will help my child improve their knowledge and skills in a specific area
• Browse by category: game type - As a parent, I want to find a new game that’s similar to one my child already likes
• Order by top rated - As a parent, I want to find a game that’s likely to keep my kid engaged for a while so I can get some work done
• Order by newest/oldest - As a parent, I want to help my child find a game they haven’t already played, to give them a new experience
• Order by most popular - As a parent, I want to help my child find and play the most popular games
• Order stories from most to least valuable to users

Value is identified from analytics on usage patterns, customer interviews, and other insights.

Your team might check feedback forms to see what parents’ top requested features are, and prioritize these first. That way, they’ll deliver more value, more quickly.

Sequence the work so you know what to deliver and when

Your team will estimate the work involved in each user story and decide what stories you can complete for upcoming sprints or releases. They may group stories that are needed to deliver an MVP, or stories that need to get released together - for example, all the “browse by category” features might go live at the same time.

Split it up over releases or sprints

The team sets your cut lines (for the sprint or version), allowing them to distinguish what they think they can deliver in that sprint/version. This will be based on their capacity and what they need to deliver to users for a minimum viable product (MVP).

A user story mapping… story

During his time at Twitter, our Co-Founder, Nicholas Muldoon, facilitated a session for another team whose goal was to figure out how they should fix an issue with the app. This example (in Nick’s words) shows another interesting application of user story mapping, including the types of issues you might work through and how you can hone in on a particular persona or subsection of your audience.

Step 1: Kick off

We started by getting everyone in the room. Attendees included several subject matter experts - not just the immediate team who were working on the project. This included someone from the user authentication team and a UX designer who had worked on password resets in the past.

The product manager kicked off the session by explaining the situation: “A whole chunk of users are having trouble getting into the app because they can’t remember their password. But in order to get them to go through the tedious password reset process, we want to give them value first to show that it’s worth doing. How?”

Step 2: Persona identification

To figure out the next steps and do user story mapping, we needed to narrow down the audience so we could use it as a framing reference or persona. After all, we were looking at a huge audience of 30 million people, not a single persona.

So we asked: who are we not targeting? Then we were able to take out any pro users and government users, which brought the audience size down to 28 million.

Next we asked: what’s the easiest place to experiment and test this? At the time, there was a feature we couldn’t access on IOS, so we went with Android. Plus, we had great relationships with the US-based phone carrier, AT&T. So we looked at our audience of Android users on AT&T in the US, which left us with a much more reasonable audience size of 3 million people.

We used this persona to experiment with this particular feature without touching all the different use cases.

Step 3: The big steps

Once we’d outlined the persona we were going to focus on, we could talk about what’s in or what’s out. So, we talked about the big steps, like:

• They’re on the Android home screen
• They open up the app
• They see all the features
• They attempt an action (Tweet, like, or retweet)
• They perform a password reset
• These customer-facing epics form the backbone of the user story map.

Plus, in this session, we also included technical epics for stuff we needed from other teams at Twitter. For example, this team didn’t control all the authentication, so they added a technical epic to have a conversation with another team to get that piece on their backlog so they had everything they needed for the experiment.

Step 4: The stories

As we fleshed out the epics, we built out the user stories below each of them.

Step 5: Cut lines

Typically, your team would do estimation and cut lines at this point, but we didn’t need to because timing was less relevant. We had to include all the essential stories to successfully run the experiment.

We did our user story mapping physically on a whiteboard, so we used tape to separate what was in and out of sprint one, two, and three. We had the backlog on the right hand side, which consisted of anything we’d discussed that we couldn’t include this time, but we wanted to come back to later. Maybe some items weren’t applicable to this persona, or we’d come back to it for IOS.

In other scenarios, we’d order the stories based on what we understood would provide the most value, estimate with story points, and then plan the capacity for a week or fortnight of work, based on historical velocity. Then we’d sequence the stories into sprint and versions. Sequencing might involve moving up something of lower customer value because you can fit it in. You might also need to break down a bigger or riskier story and split it into two user stories.

Throughout the process, everyone had the opportunity to voice their opinions (there’s nothing more frustrating than not being heard or listened to) and we’d put it on the board. One of my roles as the facilitator was to manage everyone in the room - from the quietest person to the most outgoing person.

If someone was being quiet, I’d pull them into the discussion and ask them for their thoughts directly. It’s important to pull in from different participants to get a holistic vision or understanding. Because at the end of the day, the purpose of user story mapping is to get the team on the same page. If the team sets off and they haven’t bought into the vision, they’ll soon find that everyone has a different understanding of what’s meant to happen. It’s less about the process, and much more about the alignment of the team.

Results 🏆

As a result of this user story mapping process, the project took a new direction where the app would use the device identifier along with the username to figure out who the user was before they log in. This would allow them to get straight into the timeline so they can get value.

But if they wanted to complete any actions (like Tweet, RT, or like a Tweet), they’d need to put in a password (and would hopefully be engaged enough to complete the process). Overall, it was a very successful user story mapping session!

Physical vs digital user story mapping

So, now that you know the steps in user story mapping, how do you actually implement them?

Traditionally, user story mapping is done physically. You get your team in a room, write out the backbone and user stories on post-it notes, arrange them on a wall, and use a string to represent the cut lines or swimlanes.

It might look a bit like this:

But this process does come with some challenges:

• You’ll have to find and book a room for a day (or longer if you need to map a complex product and user journey)
• We all know that post-it notes have a tendency to lose their stickiness and fall off the wall (even if you totally nail your peeling technique)
• Even if you involve remote team members using video conferencing, it’s tricky for them to read post-its - and of course, much harder for them to contribute
• A team member will still need to enter all the data into Jira once your user story mapping session is done (it’ll look like the below screenshot, which doesn’t resemble your physical story map too much)

“When I worked at Twitter, they tried to do physical user story mapping over video conferencing to include distributed team members. It was challenging. There’d be a lot of ‘Hey Nick, what does this say?’ and I’d need to read it out or type it out on chat.”

Nicholas Muldoon, Co-Founder @Easy Agile

That’s why it’s often better to use a tool or app to do your user story mapping digitally.

While there are a couple of user story mapping apps and software options, the most efficient approach is to use a user mapping tool that integrates directly with Jira.

That way, you don’t have to transfer your work into Jira - your team can move straight into working on their top priority stories as soon as you wrap up your mapping session.

Read ➡️ User Story Mapping for Remote Teams

Jira + Easy Agile TeamRhythm

Jira on its own doesn’t allow you to do user story mapping. It doesn’t replicate the physical session with sticky notes and an X axis. The best it can do is a flat backlog - and hopefully by now, you know that’s not good enough for most teams.

Fortunately, you can run a digital and collaborative story mapping session right inside Jira with Easy Agile TeamRhythm, which is an add-on for Jira.

Here’s how it works:

Add user story mapping capabilities to Jira

Add Easy Agile TeamRhythm to your Jira account. You can get started with a free 30-day trial.

If you open TeamRhythm from an agile board that’s already in use, it’ll automatically get populated with your board’s data, with current issues added to the backlog panel in the right hand panel. But don’t worry - you can easily edit this data. And if it’s a new agile board, you can easily add your backbone, stories, and swimlanes from scratch.

Set up your backbone

Across the top of the board you’ll create a horizontal row of epics (if you already have epics associated with your board, this will be pre-populated). Each epic represents an activity of the users flow through the product. This is often referred to as the 'backbone' of the story map.

These epics can be dragged and dropped and the order of the epics will be reflected on the backlog using Jira ranking.

Creating new epics right inside the story map is simple with Easy Agile. Simply click the “Create Epic” button in the top right of the screen. Add the name and description, then click “Create”. Scroll to the far right of your story map to find your new epic.

Don’t worry about getting everything perfect right away. You have the ability to edit them in-line later.

Add the flesh (or stories!)

Beneath each epic on the backbone, you’ll see any linked User Stories that are ordered by rank. To add a new story, hover over the space where you want to create your story and click “new”. Enter the name of your story and select your issue type from the drop-down (e.g. task, story, or bug). You can also access the Backlog panel to add existing stories or issues - simply click “existing”, search for your issue, and add it.

You can also drag issues in from the backlog panel.

And just like epics, you can edit your stories in-line by clicking on the name of the issue.

Order your epics and stories

Now, put your epics and stories in order. Your epics should reflect your customer’s journey from beginning to end. And your stories should be ordered by the value they deliver to customers.

In Easy Agile apps, you can click and drag to rearrange your stories and epics. And if you move an epic, the associated stories underneath will move with it.

Estimate work

Hover over the estimate field (the gray number on the bottom of each story item). Click to add or edit story points.

Read ➡️ Agile Estimation Techniques

Add and arrange swimlanes (version/sprint)

Now it’s time to decide what issues your team will tackle when by horizontally slicing up the work. Click on the swimlanes button in the top right. You can choose to sequence work by sprints or versions (depending on whether you’re Scrum or Kanban*). Your sprints or versions will appear in chronological order on the story map, and there’s an “add sprint” button at the bottom of the story map where your team can add additional sprints and versions.

* With Kanban, you’d typically sequence work into versions, as there is no sprint. This can help your team whittle down the long list of stories into the 'now' and 'future' buckets.

You can easily drag and drop stories, mapping them to the appropriate swimlane.

Check team velocity to avoid over committing your team during each sprint or version. Hover over the “Not started”, “In progress”, and “Done” indicators on the far right of the sprint or version swimlane to see how your story points are tracking across all the stories and issues. If you have too many story points, you can move some stories to the next sprint or version.

Read ➡️ Agile Story Points: Measure Effort Like a Pro

Try out different views

You can search or create a Quick Filter based on a text search (e.g. contains "As a parent"). Or if you’re using our other product, Easy Agile Personas, we have a tutorial on how you can create a Quick Filter by persona. That way, you can refine your story map and narrow in on what’s really important to you.

Get to work!

All changes made inside the story mapping session are automatically reflected in Jira, so your team can leave the story mapping session ready to start their work.

Get started with Easy Agile TeamRhythm

Easy Agile TeamRhythm works out of the box with your existing backlog (so getting started is super quick and simple). But it gives you that extra dimension to help bring your backlog to life. It’s aliiiiive!

Want to check it out for yourself? We have two options:

Easy Agile TeamRhythm Free Trial

OR play around with our demo (no installation or sign-up needed) :-)

TeamRhythm Highlights Tour

But don’t just listen to us. Here’s what some of our customers have to say:

Jira software is great for following activities and backlogs, but it’s easy to lose the vision of your product without user story mapping. Easy Agile User Story Mapping allows the teams to communicate - not only about activity but also the vision of the product. Some of our teams regularly refer to this tool for retrospectives, and it helps them make the product their product.

- Paul Flye Sainte Marie, Agile and Tools Referent @Kering

We’ve found that Easy Agile User Story Maps brings the team together in one room. As a result, we find ourselves mapping more as a group, which creates a common understanding. Since using the add-on, we’ve been able to speed up planning and more efficiently conduct large story mapping exercises.

- Mike Doolittle, Product Director @Priceline

Since using Easy Agile User Story Maps, we’ve improved our communication and team alignment, which has helped give us faster results.

- Casey Flynn, Distribution Forecast Analyst @adidas

Easy Agile User Story Maps has helped us visualize our workload and goals, as well as speed up our meetings. We love the simplicity!

- Rafal Zydek, Atlassian Jira and Confluence Expert Administrator @ING Tech Poland

See what all the fuss is about

Start your free 30 day trial

Easy Agile TeamRhythm

Psst: It’s the fastest growing and highest-rated story mapping app for Jira! You’re going to love it.

6 ways to keep your story map alive

Speaking of bringing things to life, we’ve got a few final tips...

Your user story map is designed to be a living, breathing thing so that it can help your team continuously deliver value to your customers. But you’ll miss out on these benefits if your team doesn't continually use it, reflect on it, and refine it.

Here are 6 ways you can keep your backlog alive:

1. Progress tracking

As your team delivers releases, they can visually track their progress against the user story map. With Easy Agile User Story Maps, updates in Jira are reflected directly in the user story map so you can check what percentage of work has been completed. This enables you to identify problems early on and adjust your team’s workload (and future versions/sprints) if needed.

2. Backlog grooming

The purpose of backlog grooming is to maintain a healthy, up-to-date product backlog, ready for efficient sprint planning. A few days before your sprint planning meeting, your product manager will:

• Delete user stories that aren’t relevant anymore
• Create new user stories as needs become clearer
• Assign and correct estimates
• Split user stories that are too big
• Rewrite stories to make them clearer
• Ensure stories are ordered by priority
• Make sure stories at the top are ready to be delivered

It’s much easier to do this using Easy Agile User Story Maps (rather than a flat backlog) because your product manager and team can see all the contextual information. They can shuffle the order around by clicking and dragging, and can quickly update issues with in-line editing.

3. Sprint/release planning

Sprint planning is done at the beginning of every sprint. It’s designed to help your team agree on a goal for the next sprint and the set of backlog items that will help them achieve it. This involves prioritizing backlog items (this should be straightforward, thanks to backlog grooming) and agreeing on what items your team has capacity for during the sprint. Sprint planning sessions tend to run a lot more smoothly when you refer to your user story map. With Easy Agile User Story Maps, you can update your story map with backlog items as you go, and all your changes are reflected in Jira so your team can start work on the sprint straight away.

4. Sprint reviews

At the end of each sprint, your team will do a sprint review to see whether the goal was achieved and that your increment led to a working, shippable product release. Your product manager will look at the “Done” items from the backlog, and the development team will demonstrate the work they’ve done.

The team talks about what went well, any problems, and how they were solved or could be solved. They review the timeline, budget, and potential capabilities for the next planned product release, which puts the gears into motion for the next backlog grooming and sprint planning session.

In Easy Agile User Story Maps, you can easily filter your view to show “done” issues, see sprint statistics, and update story point estimates. That way, you can do a quick and collaborative sprint review meeting, right inside Jira.

5. Roadmaps

You can use your story map to communicate your roadmap with stakeholders and share the product vision. With your upcoming releases and sprints mapped out, it’s easy to see which parts of the customer journey are going to see an update or improvement, and when.

6. Retrospectives

Retrospectives are often held at the end of your sprint or release. Or you might hold them after an event, presentation, every month, or every quarter. Retros are used to help your team reflect on what’s gone well, what could have gone better, and what they’d do differently next time. Your user story map can give your team a visual point of reference during retrospectives, and help them stay focused on the user.

How to learn more about user story mapping

We’re almost at the end, but don’t stop here! There’s so much more to learn if you want to go deeper with user story mapping.

Here are some resources worth looking into:

User story mapping books

Jeff Patton wrote THE book on user story mapping, called User Story Mapping: Discover the Whole Story, Build the Right Product. Jeff was the original user story mapper - at least, he’s credited with inventing the concept and practice.

User story mapping articles

Here are some articles written by us over the last few years:

Story maps - A visual tool for customer focused development (this one has a great video)

How to write good user stories in agile software development

The difference between a flat product backlog and a user story map

Anatomy of an agile user story map

That’s it! You’ve finished the user story mapping ultimate guide! 👏

You have all the tools and info you need to…

• Run your first user story mapping session
• Do story mapping more effectively (and confidently)
• Get more from your story map
• Prioritize your work to deliver maximum value to customers, as quickly and as often as possible
• Work more collaboratively
• Accurately schedule your work
• Understand the why behind the work

Go forth and story map! And let us know how you go.

If you have any questions about user story maps, we’d love to hear from you. You can contact us or send us a tweet @EasyAgile. We’ll update this guide as we come across more user story mapping tips, techniques, and frequently asked questions.

This past May John Walpole of Twitter presented Story Maps: A visual tool for customer focused development at the Facebook Technical Program Manager event in Silicon Valley. And our product, Easy Agile User Story Maps for JIRA, got a shoutout — thanks John!

Watch John’s lightning talk now:

John Walpole is a Technical Program Manager at Twitter in San Francisco. Prior to joining Twitter he was an engineer, product and program manager involved in the Xbox, Azure and Windows projects at Microsoft.

In this lightning talk, recorded at Facebook, John explores story maps as a way to figure out what your agile software development team should focus on (in order to satisfy customer needs). Story maps keep the customer journey front and centre during development and make it clear what should be included in a team’s sprint. For more on story mapping see Understand what your customers want with agile user story maps.

It’s time to get things done and hand over the project to the programmers. But before they get their hands dirty, someone must plan the Scrum sprint or iteration. The Sprint Planning meeting is one of Scrum’s ceremonies, and it's the sprint's opening event. 🎬

Let's walk you through the event and explain how to prepare and hold one successfully. You'll also learn who participates in Sprint Planning and why the meeting is so important.

What's a Sprint Planning meeting?

Sprint Planning is a Scrum meeting. It kicks off a sprint, so it occurs on the first day of a new sprint. If applicable, it should occur after the Sprint Review and the Sprint Retrospective from the previous iteration.

Sprint Planning aims to decide the deliverables for the upcoming sprint and define a plan to develop the work.

The entire Scrum Team (the Product Owner, the Scrum Master, and the Development Team) collaborates during Sprint Planning.

Can you imagine a successful project without planning? 🙅 We can't either, so we don’t start a Scrum sprint without planning it.

To plan a Scrum sprint, you need to decide:

• The sprint's duration — remember that a sprint is a timebox
• The sprint goal, which is its purpose and represents the product increment's value to the customer
• The work that the Development Team can complete during the sprint, what work items the team should do first to achieve the sprint goal, and how long they should take considering the team's capacity

Additionally, Sprint Planning should motivate the team and set realistic expectations.

By the end of the Sprint Planning meeting, the team must produce the following outcomes:

• A shared understanding of the sprint goal. This goal is the guideline for evaluating the Development Team's work once the sprint is over.
• The Sprint Backlog. This artifact represents the conversation between the Development Team and the Product Owner on the to-do work. It's the result of a balance between customer value and development effort.

Now, each Sprint Planning meeting requires some preparation. Read on about who should do it and what it entails.

How do you prepare for Sprint Planning?

The Product Owner should follow these steps to set the foundation for successful Sprint Planning:

• Combine the output of the previous Sprint Review, feedback from stakeholders such as management and customers, and the product vision
• Update and, if necessary, refine the product backlog
• Know the customer value that the development team needs to create in an increment

So, once all the preparation is over, it's time for the Sprint Planning meeting to take place.

How should the meeting go?

1. The Product Owner indicates the Product Backlog items — and corresponding priorities — that they consider the next sprint's best candidates. Items can be user stories, tasks, or bugs. The Product Owner proposes those items according to customer value and product vision.
2. Based on effort estimates and the Product Owner's proposal, the development team selects the product backlog items to work on during the current sprint. By promoting those items to sprint backlog items, developers agree on the sprint goal with the Product Owner.
3. Although optional, the team might discuss dependencies between items and who should work on each one of them.

Very few steps, right? However, some practical actions should add on to these steps. Discover what those actions are below.

How do you execute a successful Sprint Planning meeting?

1. Limit the meeting's duration. ⏳ Sprint Planning shouldn't take longer than 1-2 hours per sprint week. That means the meeting shouldn't take more than 2-4 hours for a two-week sprint.

2. Let the Scrum Master be the guardian of time. They're the ones responsible for ensuring that the meeting happens within the defined timebox.

3. Hold the meeting on the same day and at the same time every time. 📅 Team members can be quite busy and have full agendas. That's why reserving a slot in every participant's agenda is a good practice.

4. Define valuable, clear outcomes. 🎁 Those, together with a clear sprint backlog, increase the Development Team's motivation. Producing the right outcomes is pure satisfaction, and a clear work plan is the recipe to achieve that.

5. Make sure that the Scrum Master guarantees these things. First, that the conversation between the Development Team and the Product Owner is fruitful. They should all agree on the sprint goal. Second, that the developers make good choices when moving product backlog items to the sprint backlog. Selecting an item that is feasible for the sprint duration, team capacity, and workload is a good choice.

It might seem easy, but this is not all there is to do during Sprint Planning. There's a bunch of things to avoid.

If we were to give you some advice...

Make effort estimates against the development team's capacity. To decide on the amount of work that the team can accomplish in a sprint, consider the team's capacity. (And remember, estimates are just that — estimates.) Developers consider their previous experience, yet each sprint is unique and might change over its course. However, considering team capacity improves the accuracy of effort estimation. Additionally, story points might help the team with effort estimation.

Consider that the development team's ability to estimate should improve over time. Therefore, the team should not critique less accurate effort estimates after the sprint. Otherwise, the team will take much longer to estimate or provide much bigger estimates next time.

Don't try to plan every single thing during Sprint Planning. Leave the idea of coming up with the most complete, perfect Sprint Backlog ever at the front door. After all, Scrum is all about flexibility, and "Better done than perfect." So, a Sprint Backlog that’s complete enough to get developers started is just what it needs to be. Remember that solving complex problems requires a learn-by-doing approach, which turns planning into an equally complex job.

Figure out a realistic expectation for the sprint's outcome. Setting unrealistic expectations for the increment that the development team can produce over a sprint is not a good idea. It might make developers frustrated that they couldn't deliver, which can seriously affect their motivation and performance. On the other hand, realistic expectations set the team for success and a sense of accomplishment. Besides, they facilitate the conversation between the developers and the Product Owner so they can agree on the sprint goal.

Have a well-refined product backlog. It must be detailed enough to allow the Development Team to understand what the work items are about. You don't want to waste precious Sprint Planning time splitting work items into a maximum of one per day. Define and follow a backlog refinement process and ensure that Product Backlog items meet your definition of ready.

Propose a clear sprint goal. 🎯 The Product Owner must be very clear on the expected customer value for the increment. Otherwise, the development team might choose a set of product backlog items that don’t relate to one another. The result could be unexpected outcomes and a low sense of accomplishment.

Clarify the definition of done with the Development Team. Knowing what work done means in the current sprint helps the developers meet the expectations. That's because they can better understand what to do to create the increment. Also, a clear definition of done makes the Development Team more confident when estimating effort.

Strong Sprint Planning makes your project stronger

If you're following the Scrum framework, Sprint Planning is not a choice. Nevertheless, if you ever feel tempted to skip it, bookmark this article and read the following. 📑

It's easier to understand the sprint goal, to-do work, and sprint outcomes with a successful Sprint Planning meeting. If the team doesn't know where it's heading and how to get there, it gets really tough to satisfy customer needs. It's equally hard to deliver your customers valuable increments if you don't organize work by priorities.

Sprint Planning is about instilling clarity and organizing work before it's too late in the iteration. It's also about involving the whole team in preparing for all the effort that a sprint demands. A note: Keep in mind that a sprint plan must fit into a sprint's timebox and consider the team capacity.

Easy Agile TeamRhythm is perfect for Sprint Planning. It's a fast, straightforward, visual, and collaborative tool that allows you to:

• Drag items directly from the product backlog onto the user story map
• Register effort estimates in user stories
• Edit story point estimates
• Prioritize user stories in each sprint by ordering them inside the respective sprint swimlane
• Analyze sprint statistics to ensure that the planned work doesn't exceed the team's capacity and the sprint goal is realistic
• Visualize what the team will deliver and when by arranging user stories into sprint swimlanes

Let us know if you have any questions about Easy Agile TeamRhythm. We highly recommend it to your Scrum project, and our customers recommend the same.

Get ready for remote user story mapping.

Whether you've done user story mapping before (in person) or you're new to user story mapping, there's a very good chance that you'll need to do remote user story mapping for the first time in 2020.

Even before the pandemic, 4.7 million people in the US worked remote, and an estimated 31% of US workers employed in March 2020 were working from home by April 2020.

And after lockdown ends, it’s likely we’ll see permanent changes to the way we work. Surveys show that 80% of employees are keen to work from home at least some of the time. Plus, more organizations are realizing that offering flexible, remote work options can lead to better work-life balance for employees, lower overheads, lower environmental impacts, and improved productivity.

...which is all to say that remote user story mapping is about to be the norm.

So, what do you need to know before you run your first online user story mapping event? Let's go through 8 things you should consider for successful remote user story mapping.

1. Get the basics right

First thing's first: you need your basics sorted. Make sure your team understands what user story mapping is, why user story mapping is important, and how to do it.

This will help get them onboard - which is critical, because you'll need them to commit two full days to the process.

If anyone on your team is new to user story mapping, send them to our user story mapping ultimate guide. It's got everything they need to know 👌

2. Set your agenda

User story mapping should be a scheduled event. You should know what's happening and when to make sure that your team stays on schedule and completes all the steps required to produce a finished story map. Here's a fairly standard agenda:

Knowing your agenda is especially important for remote story mapping, because it's a lot easier to veer off track when people aren't physically in the room.

Sally might head to the kitchen for a long lunch and miss the most important bit. Or Bob might need to coordinate his schedule so that his partner can mind the kids for a solid hour or so while he's involved in estimating the work.

Setting the agenda ahead of time will also help your team start thinking about the session and user stories before the event. That way, they’ll feel more prepared and ready to participate in discussions.

By the way, if you’re not familiar with all the items in the above agenda, we talk more about the specific steps and how to do user story mapping in our ultimate guide to user story mapping.

3. Plan your session

When are you going to hold your live online user story mapping session? Most teams need a full two days to work through all the steps, so you'll need to find two days (ideally in a row) when everyone is available.

If your team is located across multiple time zones, you'll also need to consider what times give you the best crossover so that team members aren't working at 2 am (unless they want to).

4. Decide on who

Remote user story mapping could present you with a bit of a conundrum. Unlike in-person events where you're limited on space, you could technically have unlimited people chime into your virtual session. But you definitely don't want that - too many people will make you inefficient (and they could use their time to add value to your business in other ways).

It’s a good idea to cap your numbers at around 12 people. Include team members and stakeholders across multiple departments, along with your product manager, UX designer, and developers.

Also decide who is going to lead the session and who will be responsible for creating the story map.

The good news is that online user story mapping makes it easy to record sessions - you'll have a digital record of your conference calls and your story mapping board. So anyone who's curious can easily catch up on the highlights once your event is over.

5. Make some rules

Working and collaborating remotely can feel a bit like the wild, wild west - especially the first few weeks or months. Everyone's still figuring out how to make this thing work - and how to get things done effectively in a new environment.

We've all been to conference calls where somebody didn't know proper etiquette or their audio/video ended up distracting other attendees.

So, with that in mind, here are some rules you might like to share ahead of your remote user story mapping session to make it a little less chaotic and a lot more productive:

• Don’t be late
• Put your camera on
• Save your food for a designated break
• Don’t take your device for a walk
• Close your door, if you can
• Stay focused on the task (no checking emails!)
• One person talks at a time
• Wait until everyone has had a chance to provide input before moving on
• If you’re not talking or participating in the conversion, mute yourself (to avoid interference or background noise that could stop people from focusing)

Of course, be realistic. Your team members are likely working from home in less-than-ideal circumstances, whether they're quarantined with family members, stuck at home with a sick child, or dealing with a bad-mannered house dog.

There will be noise and disruptions - and despite their best efforts, someone will be late. As long as people do their best to hit the mute button at the right time and consider others, your session should run smoothly.

6. Get your tech ready

Previously, you might have been able to show up to a user story mapping session with just your brainy self and a pen 🧠🖊️ You'll still need your brain for remote user story mapping, but you can ditch the pen.

Instead, you'll need to make sure you and your team have access to the technology they need to participate and collaborate online. Things like:

• Zoom, Google Hangouts, or Skype access - Everyone should have their account ready to go, along with some experience using the platform
• Slack or Microsoft Teams - Set up real-time chat for when you’re not in a video conferencing session
• Headphones & Microphone - These should be working well and tested ahead of time
• Webcam - While not strictly necessary, a webcam will help you replicate the feeling of being in the room together
• Internet - Ask your team to test their connection and make sure it's reliable - and ideally, have at least one backup option (like a local cafe, friend's house, or mobile hotspotting)

The right technology will allow you to adapt the user story mapping process to work for your remote team.

7. Get user story mapping software

A physical user story mapping session usually involves a long sheet of paper or cardboard, with hundreds of tiny post-it notes for each story and backbone item, and string to show cut lines.

The good news is, if you're doing remote user story mapping, you won't need to clear out your nearest stationery supply store 🎉 But you will need to equip yourself with some digital tools to replicate the physical story mapping board online.

There are a few user story mapping tools on the market, but we're partial to Easy Agile User Story Maps. It plugs straight into your existing Jira workspace, allowing you to:

• Visually map your customer journey
• Assign stories to epics
• Prioritize and sequence stories
• Arrange stories into sprint and version swimlanes
• Add story point estimates

It’s just like physical user story mapping, but done digitally inside of Jira. That makes it perfect for running a remote user story mapping session.

Okay, so we may be a little biased, but these people aren't:

Want to give it a spin for your upcoming remote user story mapping session? Sign up for our free 30-day trial to see the benefits for you and your team. We’re confident you’ll love what you find!

Try it now

8. Integrate your workflow

Last but not least, make sure that your remote user story mapping session integrates with your workflow

Good news! If you use a digital user story mapping tool (like Easy Agile's), you'll find it much easier to integrate your story map into your workflow. Once your user story mapping session is finished, your user stories are already set up in Jira, and organized into sprints or versions so that your team knows exactly what they need to work on next.

(Although they might want to take a day or two to ease back into it...😴)

Set yourself up for success!

With the right preparation and tools, you'll set yourself up for a relatively smooth remote user story mapping session. And after that? You'll be set to do your future story mapping events in a more streamlined, digital way, whether you're required to work remotely, collaborate with a distributed team, or work from the office.

And based on the way work is changing in 2020 (and beyond), that's a very good skill to have.

A product backlog represents all of the goals and desired outcomes within the development of a product. They are the specific tasks a team hopes to complete when they set out to design or improve upon a product.

What makes a product backlog so effective is its agile nature. Backlogs are in constant evolution, changing and adapting based on the current needs of stakeholders and customers. To keep a backlog up-to-date and in its most effective form, it needs to be continuously refined and adapted. This process takes time, but there are simple, powerful strategies for maintaining a quality backlog.

A good product backlog has four characteristics. It is:

• Detailed appropriately
• Estimated
• Emergent
• Prioritized

We’ll cover all of these attributes in detail, including how you can ensure your product backlog is in good health. But first, let’s get on the same page about product backlogs and the refinement process.

Transform your flat product backlog with

Easy Agile TeamRhythm

Try Now

What is a product backlog?

A product backlog is a prioritized and ordered list that represents the work to be completed by a development team. Backlog items are derived from the product roadmap and are organized based on the tasks that are most vital — the ones that will make the biggest impact at any given time.

Backlog items represent what it will take to develop a new product or improve an existing one with new features. It’s all of the work a team will tackle in the future, but it’s also a flexible, living organism that evolves as a development team learns more about the product and its stakeholders.

The product owner is in charge of ordering and prioritizing backlog items, placing high-priority items at the top. They are also responsible for backlog refinement, which ensures all backlog items are organized, have appropriate details, and are ready for any upcoming sprint planning.

Product backlogs vs. sprint backlogs

Sprint backlogs are quite similar to product backlogs, but they serve a different, more specific purpose. At the beginning of a Scrum, the product owner arranges the product backlog items that are to be completed by the Scrum team in that sprint.

The Scrum product backlog represents a small subset of the overall product backlog. The product backlog is the entire bottle of wine, while the sprint backlog is the glass of wine you’re going to tackle next. In this analogy, the Scrum master is the sommelier, providing guidance, context, and feedback throughout the sprint.

At the end of the sprint, a sprint review is conducted with the stakeholders to better understand what to tackle next. Backlog items that weren’t completed may be pushed back into the larger product backlog to get to at a later date or during the next sprint. Another sprint planning meeting will prepare the team to tackle the next batch of backlog items.

Why does a backlog need refinement?

Backlog refinement isn’t a luxury task reserved for when you get a chance to tidy up. Refinement is a key part of product backlog management that ensures a backlog always has the most recent, up-to-date information.

Refining the backlog prepares it for the development team, saving time in the long-run. The process helps to prioritize items and ensures there’s nothing in your backlog that you no longer need.

As you’re well aware, the agile methodology centers around flexibility and the ability to evolve a plan as new information or roadblocks appear. What you thought was important at the beginning of product development may not be necessary anymore, or your stakeholders may have turned you in a completely different direction.

Product backlog refinement includes:

• Adding detail to high-priority backlog items for greater comprehension.
• Improving and reviewing estimates.
• Removing items that are no longer relevant to the product.
• Adding items based on new stakeholder feedback.
• Making adjustments based on the most recent bug fixes.
• Prioritizing items that bring customer value.
• Ordering backlog items to deliver the most impact over the next sprint.

Backlog refinement takes time, but it’s well worth the effort to have a healthy, up-to-date backlog that’s always ready for the development team.

DEEP: The key attributes of a good product backlog

Roman Pichler, the author of Agile Product Management with Scrum: Creating Products That Customers Love, developed DEEP to describe the key attributes of a good product backlog. The acronym DEEP helps product owners and development teams understand how to make smart decisions while maintaining a successful backlog.

The concept is applied throughout the product backlog refinement process, which is a critical part of backlog management. Backlog refinement, previously called backlog grooming, is an ongoing process that ensures a backlog is in tip-top shape. We like to think of it like trimming the branches of a plant.

To help a plant grow, you need to prune and trim it. The refinement process adds details where needed and prioritizes items based on the current information a product owner has from team members and stakeholders.

DEEP stands for Detailed appropriately, Estimated, Emergent, and Prioritized.

Following these guidelines and best practices will lead to a quality backlog, which will lead to smooth product development and a successful end result. Let’s dig into each attribute. 🔎

Detailed appropriately

Details matter, especially as a user story rises in priority. As a backlog item gets closer to being completed or moved into a sprint backlog, it requires more detail. Upcoming backlog items should be detailed appropriately, so they can be better understood by the development team. The closer an item is to being completed, the more detail it should have.

On the other hand, items that are lower on the priority list don’t require nearly as much detail. It’s a poor use of time to add details to lower priority items since you never know how the backlog is going to evolve. You could waste a lot of time detailing low-priority items when they might be removed or revised later on in the process.

Estimated

Thorough estimation should be focused on high-priority items that will be tackled soon. As you refine your backlog and add more details to top-priority items, you can improve your estimation. A good option is using story points to zoom in on the details. They can help you accurately and practically reflect the reality of an item from the customer’s perspective.

📘 Read our guide to incorporating user story points to start using this technique.

Since not much is known about them, it’s difficult to properly estimate items that are lower in priority. When you are further down the priority list, your estimation will be more of a guess since you don’t have all of the information yet. In these cases, use a simple agile estimation technique, such as t-shirt sizing (labeling work items as XS, S, M, L, XL) to make a guesstimate. Based on the information you have at that moment in time, make an approximate estimate on the exertion required for that backlog item.

Emergent

The more you learn about the product and its customers, the more you can improve your product backlog. The backlog is a living document that represents your plan at any one given time. It’s not set in stone, and it should see revisions and improvements as you go.

With the information gleaned from retrospectives and stakeholder feedback, you can update the backlog to reflect what you’ve learned along the way. Allow your backlog to evolve, adding, removing, and refining items as needed.

Prioritized

A product backlog needs prioritization. Items at the top are a higher priority, and items toward the bottom are a lower priority. When deciding which items should be prioritized, consider the value each item will provide.

Your team can maximize its efforts by prioritizing the backlog items that will provide the most value to customers at any given time. Since this will change depending on the current needs of your customers, you need to continually adjust and refine your priority order.

Achieve a DEEP product backlog with Easy Agile

Easy Agile is dedicated to helping agile teams work more effectively. We have a suite of Jira apps designed for teams that want to develop products that put the customer at the forefront of decision making.

Easy Agile TeamRhythm transform your flat product backlog, prioritizing based on value to the customer and bringing the customer journey to life. They help teams organize and prioritize user stories while visualizing the customer journey. Keeping your customers embedded in your process will help you make refinement decisions that are in the best interest of the customer, no matter what phase of development you’re in.

Learn more about our agile apps and follow our blog for the latest content for Jira teams.

The Atlassian Marketplace is filled with helpful Jira add-ons or plugins. These apps help teams successfully carry on projects and deliver on time. In this article, we’ll go over our selection of Jira gadgets for workflow management, reporting, and project administration.

We'll show you some of the best solutions to:

• Analyze data about Jira issues
• Automate Jira issue workflows
• Migrate projects and their configurations
• Build user story maps in Jira

But now seems like the perfect time to explain why we're such big fans of Jira Software and Jira add-ons. 🙌

Why Jira add-ons are trending right now

Jira is the leading software solution for collaborative teams — developers around the world rely on it to track their tasks and ship value to customers.

One of Jira's major value points is customization. Jira users can customize issue workflows and issue types, for instance, to meet your project requirements. After setting up your Jira process, developers adjust and adapt to the tool. Over time, the number of Jira projects and issues in your company will increase, so you need a system to keep up with the pace of your growth. 📈

Scaling growth brings some challenges. But it doesn’t have to be a big issue! 🙅 Jira add-ons build on Jira's strengths, allowing you to set it up to suit the needs of the team. They allow developers, other team members like Product Owners, and business stakeholders to get the most value out of one shared platform. To choose the best Jira add-ons for you, take a look at what your team most needs help with, pricing, and any available tutorials.

Let's dig into some of the trending Jira plugins.

1. Easy Agile User Story Maps for Jira

Easy Agile User Story Maps for Jira is one of our Jira add-ons and one of the top-selling apps on the Atlassian Marketplace

You may use Easy Agile User Story Maps for Jira to create straightforward user story maps collaboratively. But why do you need user story maps?

Why user story maps are useful

User story maps facilitate agile teams during project inception. Those maps are a visual representation of customer journeys and the activities and tasks that customers execute in the product.

The visualization of the customer journey is the biggest benefit when moving from flat product backlogs into user story maps. Additionally, they can understand and prioritize the work they should do to deliver customer-valuable product releases.

There's more to Easy Agile User Story Maps for Jira, though. The app allows you to:

• Create epics and user stories
• Update and refine user stories
• Break down epics into user stories
• Schedule user stories
• Register effort estimates in user stories
• Edit user story point estimates
• Order user stories by customer value inside the respective Scrum sprint or Kanban version swimlane with the drag-and-drop functionality
• Analyze sprint or version statistics to ensure that the planned work doesn't exceed the team's capacity
• Visualize what the team will deliver and when by arranging user stories into sprint or version swimlanes

2. Pivot Report

If you’re already using Jira, all or most of your project’s software development data is in Jira. That means you should rely on Jira to analyze that data. The Pivot Report Jira add-on is your go-to solution if you need to visualize or present data from Jira issues in the form of a pivot table. It's your way of seeing the big picture of your Jira issues. We'll explain this in detail below, but first, let’s review what pivot tables are.

What's a pivot table?

A pivot table is a data analysis artifact you can use to answer business questions such as the impact of advertising on sales or the relation between product returns and quality assurance procedures. You might know the term from Microsoft Excel. Pivot tables also come in handy for sending condensed and organized business information to stakeholders. They may use that information for decision-making or process improvement, to name a few use cases.

Pivot tables are easy to understand, as they help you visualize data. Since a pivot table stores data, you can use it to play around with those data. For instance, you can filter, sort, group, and perform calculations on data.

Pivot tables for Jira

Jira's default reports, advanced searching, and dashboards are nice enough, but you might also need help viewing overall progress information or totals. Pivot tables help with that.

Often, other reporting solutions require extra set-up to match your Jira settings and project customization. But with Pivot Report for Jira, the tweaks you need only take a couple of clicks.

So, if you need the big picture of your Jira project, you may use the Pivot Report Jira add-on. It can help evaluate your project's status point from these perspectives:

• Overall scope progress
• What Jira issues the team tackled — open and closed issues
• Who exactly resolved each issue
• The amount of work left to do
• Overdue issues and other flaws such as issues without assignee, overdue, or outdated

You can also use the Pivot Report add-on for:

• Time-tracking for team members
• Customized progress visualization by picking the indicators you need and ordering them as you wish
• Getting the big picture of your Jira issues, such as the relation between epics, tasks, and subtasks

3. JMWE (Jira Misc Workflow Extensions)

JMWE (Jira Misc Workflow Extensions) is perhaps the best Jira Cloud app to automate Jira issue workflows. It was born by the need of Jira administrators to customize workflows. As Jira's default capabilities don't include complex workflow templates, the answer was customization...and JMWE.

This Jira add-on extends Jira to help you design and implement complex workflows. And the more you can customize a workflow to meet your project configuration, the more automatized data input gets.

And do you know what's even better than workflow customization in JMWE? If you don't want to code, there's no need to! Nevertheless, if you want to code, you may schedule actions with Jira Query Language (JQL).

Here's a list with some examples of what you can automate in your workflows, under certain conditions, with JMWE:

• Create issues and assign them to members with a specific role
• Link or unlink issues to build their dependencies
• Compute or clear the value of issue fields
• Copy the value of issue fields from one issue to another
• Comment on issues with specific information
• Email all the information that Jira has on issues, whether it includes attachments or not
• Define sequences of actions within the workflow, such as issue status transitions

4. Project Configurator for Jira

You can manually copy projects and their configurations from one Jira instance to another. However, if something could do it for you, that'd be great, right? Well, that’s what Project Configurator for Jira does.

You can export and import full projects — meaning their configuration and data — or just specific project configurations. Those configurations may reference shared objects such as custom fields, workflow schemes, issue type schemes, screen schemes, and workflows. You can also use Project Configurator to export and import other shared objects such as filters, dashboards, and software boards.

If you want to use your project configuration from the development environment to configure the production environment, this Jira add-on is your answer.

There's another advantage to Project Configurator: You can use it to simulate imports. That way, you can spot and solve any problems that might arise if you go ahead with the real import. Later, you can proceed with the import from the simulated import report. This whole import scenario is useful for testing project configuration updates on a staging environment, which precedes the production environment.

Jira add-ons for all purposes and tastes

You may see our selection of Jira add ons as an ecosystem of Jira workflow management, reporting, and project administration tools allows for:

• Easy customization of information extracted from Jira
• Jira data visualization for decision making, process improvement, and progress tracking
• High customization of sophisticated Jira reports
• The automation of Jira manual tasks to save time and reduce manual errors
• Jira work plans for sprints or versions

We can’t let you go before inviting you to try our Jira add-on for yourself. Try out Easy Agile User Story Maps for Jira.

What is a customer persona?

Customer Personas are fictional generalizations of your most valuable customers.

They help teams understand their customers by bringing together demographic information like age, gender, location, and income, alongside psychographic information like interests, frustrations, and personal or professional motivations.

What are user personas?

Now It might seem trivial at first, to come together as a team, mocking up what seems like fake dating profiles for your most important customers.

However, this exercise sets the foundation for other agile practices down the track, and its benefits are often undervalued.

Agile experts have called for more cross-functional teams, which means this knowledge of who the customer is, is no longer the sole responsibility of your Sales and Marketing team. Everyone is responsible for understanding who the customer is.

Teams that have a shared understanding and alignment around who is actually using the solution they are delivering are more likely to succeed.

Building customer personas helps teams to address the following questions:

• Who are our customers?
• What are their common behavioral patterns?
• What are their shared pain points (professional and personal)?
• What are their goals and objectives?
• What general demographic and psychographic information may influence their decisions?
• What drives them to make purchasing decisions?
• Is the customer the buyer or decision maker?
  

There are two steps you can take to answer these questions and start to identify who your customer personas are:

Firstly, broadly define your personas

It’s not crazy to think that most companies will have some broad idea of who at least some of their customer personas are. This knowledge is accumulated over time and is based on customer feedback, support requests, conversations/interviews, and initial market research.

This knowledge is not to be underestimated and is a great starting point before looking towards analytics to flesh these personas out into more specific detail.

Secondly, look towards insights and analytics

Once you’ve come up with a few customer personas, it’s time to flesh them out with qualitative and quantitative data.

So where can we find this information?

Look at sources like:

• Website Analytics
• Facebook Insights
• Customer Surveys & Polls
• Industry reports
• Customer Interviews or
• In-Product Analytics

After looking through all of this information you can map back the data against your original assumptions.

By the end of the exercise, you and your team should have a pretty good idea of who your customers are, and how to best service them, communicate with them and build solutions for them.

Customer personas in Jira

Once these personas have been developed, the challenge is choosing where to store them.

Making the personas highly visible should encourage your team to consider them each time new work enters the backlog. You want them to think, “What would Sam the System Administrator think about this new feature? Would she use it? How would she communicate its benefits to her team? What are some of the problems Sam may encounter on first use?”

That’s why we created an app for Jira - Easy Agile Personas.

Easy Agile Personas enables you to create and keep your user personas in Jira alongside your work, so the entire team can keep the customer in mind.

Whether you choose to use Easy Agile Personas or not, the customer personas you develop are vital to building user story maps.

Try it now