Agile is about empowering teams to take ownership, feel truly engaged, and foster a culture of collaboration. More than ever, teams are required to deliver with greater adaptability, speed, and engagement. The future is more ambiguous and complex, and Agile teams must know how best to respond to these changing conditions.

Agile experts John Walpole, Dean MacNeil, and Nick Muldoon share their success formula behind the high-functioning Agile teams at Lyft, Valiantys, and Easy Agile. You will learn:

• How to create a compelling 'why' that the whole team can get behind
• How to empower your teams
• The qualities of high-performing Agile teams

WATCH NOW

Create a compelling 'why' that the whole team can get behind

‍

I think Agile is not a silver bullet. We have people who look at Agile and say, "Oh, well, this is going to solve all of our woes." And it's not; it's certainly not a turnkey thing.

Nick Muldoon, Co-CEO at Easy Agile

Agile is not a silver bullet. It is not a methodology that will solve leaders, teams and individuals' problems. Agile is a continuous improvement journey of "adaptability in evolutionary theory; it's about responding to either a new environment or changes in your environment to again, not just survive but to thrive," said Dean.

Set your Agile teams up for success by teaching them to thrive by empowering them to lead change, make mistakes, build a solid foundation, and be open to learning, changing, and communicating the meaningful 'why' behind their work. You will see an explosion in Agile team success when you have a "cohesive team aligned to a common mission with a growth mindset."

Motivate your Agile teams by connecting their work with a meaningful 'why.' Schedule a meeting to ensure you constantly discuss their work's more profound purpose. Bring up a real-life customer example. John shared, "At Lyft, we share stories in a fortnightly meeting. We offer free accessible rides to those in wheelchairs or those who struggle to pay for a ride but need access to transportation to get to work or school.

"Bring your personas to life with these real-life examples, so it's front and center in your employee's minds," said John.

‍

Empowering your teams

Culture eats strategy for breakfast

Peter Drucker

Your employees need to lead the change. "If you look at great leaders in recent Agile transformations, you might want to look at a company like Porsche," said Dean. Dean shares how Porsche has inspired Valiantys because "every employee at Porsche is leading the change. So they're all bought into it; they all have that sense of leadership to drive it.". Porsche's employees are leading the change because their leadership communicates the 'why' well. "Fun is number one when their CIO lists off the top three reasons 'why' everyone is so fired up about the Agile transformation. Because you can have fun on the job, your job is not supposed to be a grim duty. It's supposed to be something you look forward to."

"Empower your teams to make mistakes," said John.

Empower your Agile teams to fail and make mistakes through powerful questions. Leaders have to change their tone from "oh no, who do I fire?" to "what's the challenge? What can I do to help?". Express to your team that you're on a journey to learn as much as they are. In doing so, the leader humanizes themselves and becomes more vulnerable.

Leadership sets the tone. As a company scales, the responsibility to create the culture and the risk appetite falls more on leadership.

Qualities of high-performing, Agile teams

1. Create a solid foundation

Set your Agile team up for success with a stable team unit. Don't keep moving teams around; create long-term Agile teams to allow individuals to get to know each other and humanize one another. "I think stability is key to having the tacit knowledge keeping together and this open mindset where they're willing to learn; I love that," said Nick.

2. Open to learning and adapting

For Agile teams to continuously improve, they must constantly be learning and adapting. "You can't get that learning and adaptation if you keep just stirring the pot. Because you're going to keep scattering that knowledge, you want to take hold, and then, of course, you want to spread the knowledge to the organization then," said Dean.

3. Share feedback and do the retrospective

Ensure your Agile teams are demonstrating working product on a regular occurrence. If you're practicing Scrum, make sure you are doing the weekly sprint review. This allows the team to receive feedback from stakeholders and keep iterating and moving forward, ensuring they stay in movement. "Do your retrospective," said Dean." We're looking at what we delivered, and now we're going to look at how we delivered it." It is imperative that Scrum teams gather at the end of each sprint to discuss what went well, what didn’t go so well, and what can be improved on for next time. Otherwise, you invite complacency and stagnation into your Scrum process — the antithesis of Agile.

Using Easy Agile to set your Agile teams up for success

Easy Agile TeamRhythm supports your team's Agile practices in Jira. The user story map format in TeamRhythm transforms your flat product maps into a dynamic and flexible visual representation of work. Watch the highlights tour to see how Easy Agile TeamRhythm makes sprint planning, managing your backlog, and team retrospectives easier. Visit Atlassian Marketplace to start your free, 30-day trial today.

‍

“The people who plan the work do the work” is the unwritten rule of the Scaled Agile Framework.

Yet, this can be easier said than done when we’re looking at multiple teams of people needing to plan together.

Add in the complexities of large enterprises that face their own unique challenges - ranging from product development to budget to implementing feedback to final delivery - and suddenly the idea of how to bring teams together for planning can feel harder again.

If you’re familiar with the Scaled Agile Framework, you will already be aware SAFe is designed to facilitate better collaboration and communication between multiple cross-functional groups. The core way to do this with SAFe is Program Increment or PI Planning (Planning Interval Planning in SAFe 6.0)

A plan can take on so many different forms - even just between teams - but with SAFe it is easier to see what ‘good’ looks like when it comes to efficient PI Planning.

The SAFe program board or ART planning board (SAFe 6.0), is a critical tool and output of PI Planning. It is a visual summary of features or goals, cross-team dependencies, and other factors that impact their delivery. Not only does this help with transparency, but it also increases flexibility that, in turn, helps minimize delays and unhealthy dependencies.

What is often overlooked is that PI Planning plays a crucial role in setting teams or the entire program up for success - including implementing other SAFe ceremonies or events.

In this article, we’ll discuss everything you need to know about program boards, including why they’re important in the planning process and how larger teams can use them in PI Planning and beyond.

We’ll also explore exactly how Easy Agile Programs digitises the SAFe program board, not only allowing the people who plan the work to do the work, but also allowing you to plan the work in the environment where the work gets done - in Jira.

NB: while the program board is referred to as 'ART Planning Board' in the updated 6.0 version of the Scaled Agile Framework, it is the same artefact and plays the same role in PI Planning and beyond.

What is a program board?

What does your teams plan or schedule typically look like?

Would it indicate to you what work was being done? Who was doing it? Perhaps even an indication of when they would and any key deadlines these teams are working towards?

The headline here is that a program board is all of this, but also more.

The program board is a visualization of the work being committed to during the Program Increment / Planning Interval or PI. It is simultaneously the facilitator of planning as well as the plan itself.

A typical idea of a program board - especially for collocated PI Planning sessions - is literally a physical board on a wall.
It would show:

• Columns: marking the iterations for the increment
• Rows: representing different teams within that increment
• Sticky notes: describing the features that teams are working on or used to indicate milestones that they’re working towards
• Strings: between these features to indicate if there are any dependencies

But how does a program board help the planning process?

A program board facilitates better team collaboration because it streamlines project communication and planning, while also ensuring better communication between the involved teams.

Moreover, program boards help define the responsibility of each team involved in making the idea a reality, which in turn, helps to streamline the process as a whole.

During PI Planning, the program board supports teams to visualize and manage dependencies across the PI; giving them greater clarity of the work in detail, how the work relates to what the business is trying to achieve and to each other, what tasks need to be done, and crucially, whether there are any issues that may cause delays.

A program board is simultaneously the facilitator of planning as well as the plan itself.

To understand how program boards help with the planning process, let’s go over the different components found on them.

How to set up your SAFe program board for successful PI planning

According to Scaled Agile, there are two primary outputs of PI Planning:

1. Committed PI Objectives
2. Program board - with new feature delivery dates, dependencies among teams and relevant Milestones

So if you’re following SAFe and doing PI Planning you should finish PI Planning with a program board.

During PI Planning, not only do teams discuss and define the features and dependencies, but they also establish milestones across the PI.

This is where a digitised PI Planning tool can really benefit remote or hybrid teams doing PI Planning - the same information is planned in the same place.

Here are a few tips to help you create a SAFe program board.

1. Setting up the board itself

Not to be underestimated, the bare bones of the program board need to be set up.

There are two key elements here:

• Sprint or iteration columns:
  • The right number based on how many iterations/sprints will be in your PI, including a final one for iteration planning
• Rows or swimlanes:
  • One for milestones/events - typically the first
  • One for each team
  • May also have a swimlane for shared services, suppliers or other teams not in the Agile Release Train (ART)

Here is what this may look like:

If you were at this stage of your program board in Easy Agile Programs, your board would look like this:

In Easy Agile Programs, each team represented in a dedicated swimlane represents an agile board in Jira. So the issues that you will be scheduling for this team in sprints during PI Planning and beyond, will be reflected on their agile board and vice versa.

The start and end date for the PI and the number and length of your sprints can all be edited to suit your organisation’s workflows.

When you are in editing mode and are ready to schedule features, the shared team features swimlane also appears at the top to visually indicate if there is work to be scheduled across multiple teams.

2. Start with features and milestones

During PI Planning, Product Management shares the product/solution vision and this commonly also means the next top 10 upcoming features for the teams to take into the PI from the backlog. (We know from our customers that sometimes this can be a lot more!)

We also want to start by knowing which milestones we are working towards. Often these can represent product release dates, external deliverables or deadlines like preparing a demo or showcase for a trade show, marketing launches or events. Having these visualized on the program board helps teams to easily see what they are working towards, but also to inform prioritization of the specific features needed to help meet delivery of that milestone.

If you are working with a physical or simple digital program board, features and Milestones are represented by ‘sticky notes’ - placed in the appropriate swimlane and/or colour to indicate this information as well as the team responsible for it and the time frame:

So what does this look like in Easy Agile Programs at this point?

Milestones are highly visual

• Milestones can be customised to indicate start/end date and colour. They run across all team swimlanes so teams can easily see how their work relates to an upcoming deliverable or event.
• Milestones still have a dedicated place at the top of the program board but this can be collapsed if desired

Features are native Jira issues

• Features in Easy Agile Programs are native Jira issues, commonly epics. You can easily click on the issue key from the program board to see more information via the issue view.
• Features can be easily scheduled from the backlog into a swimlane through drag and drop, or created via the program board. To indicate when a feature is intended to start and be completed, simply drag and drop the edge of the issue:

Join a product tour to walk through Easy Agile Programs

Want to bring your Program Board into Jira?

Join a demo

3. Identify dependencies

With the features done, the next thing that teams should look for is dependencies. Remember the strings we mentioned before?

Dependencies between features and teams are represented with string on a program board when it’s on a wall or lines between those features in a digital tool.

Sticky notes in a different colour, like red, indicate a significant dependency. For example that feature may have more than one feature relying on it to go to schedule.

To explain this, let’s consider an example.

Imagine Team X realizes they cannot develop a feature until Team Y develops an API thanks to the program board. So, what both teams can do is talk to each other and come up with a solution that works for everybody, leading to better collaboration among the teams.

After an agreement is reached, a dependency will then be placed on the board so everyone has the same understanding about the dependency, and how it’ll be resolved. A piece of string will be attached to each card to demonstrate this:

The nature of dependencies mean that something is required to be completed in order for something else to be done.

To be able to more easily see when dependencies are scheduled, Easy Agile Programs has a traffic light system of red, orange and green dependencies to indicate dependency health.

Dependency health is represented as follows:

• A red line indicates the dependant issue is scheduled in a sprint after the dependency (conflict)
• An orange line indicates the dependant and dependency are scheduled in the same sprint (a risk)
• A green line indicates the dependant issue is scheduled in a sprint before its dependency (healthy)
• A black line indicates the dependency exists with issues outside of the current view. Whether this is the current Agile Release Train / Program, or with a future or past increment.

This easily indicates to a Release Train Engineer or a Program Manager where they ought to focus and to be able to address any scheduling issues during planning.

Easy Agile Programs also allows you to visualize dependencies between issues within and across teams from the Team Planning Board. This provides a really focussed view of the work for a particular team for the PI, and how that work relates to other teams:

Program boards are needed for better collaboration

The power of the program board lies in having a single view of what a collection of teams are committing to - together - and exactly how that work relates to each other. It helps organize planning sessions by summarizing future dependencies across all teams and sprints. As a result, scrum masters, release train engineers, product managers and business owners can easily identify and prioritize cross-team conversations that matter the most.

Running a scaled planning session or PI Planning ceremony, especially for the first time, can be daunting.

But if you’re successful in developing a solid program board as part of your PI planning process, you won't have to worry about chasing down your co-worker or team member to meet deadlines. The key here is to make sure you’ve scheduled the most important features to take into the PI, identified cross-team dependencies, and have visualised any milestones or deadlines to ensure they can be realistically achieved.

The program board can become more impactful though, when it is more than just a plan. Building a program board in an online tool with the added capability of it representing the actual work that’s planned to be done means that it has a life beyond PI Planning; it becomes the living document of the teams progress and a means to identify when there are any blockers to that progress.

In order for agile teams to be agile and continuously and iteratively deliver value, they need to be equipped with a program board that can help them respond to any changes so that they can plan for success but also progress towards it.

Ready to take your Program Board off the wall and into Jira?

You can with Easy Agile Programs

TRY NOW

‍

The most efficient and effective method of conveying information to and within a development team is face-to-face conversations.

Agile Manifesto, 2001

As true as this statement was when it was written, the Covid-19 pandemic irrevocably changed the way we work, live and communicate.

As organisations and individuals we found ourselves quickly needing to adapt to an ever-changing environment. Now that we have survived, we have to lean into this new way of doing things in the workplace so that we can thrive.

But what about our agile ceremonies?

One of the main reasons companies transition to agile is to make business processes and outcomes more efficient. So how do we take those principles and practices and preserve their integrity in a remote environment?

If you’re familiar with the Scaled Agile Framework, you’ll know that PI Planning is an agile ceremony that is at the heart of implementing SAFe.

Traditionally a face-to-face event, PI Planning is a scaled cross-team planning ceremony that aims to bring together multiple teams to plan - aligning them around a shared mission and vision for the upcoming quarter or increment.

SAFe still advises that PI Planning is still collocated where possible, and it does have its benefits.

However many teams, even before the pandemic, used PI Planning software to run their planning process and to make it more efficient and accessible to distributed PI Planning. But as with most things we have taken online since Covid, we are at the mercy of the tools we use to determine how effective we can be.

The truth is, unless you can get all members within an Agile Release Train - Business Owners, stakeholders, product management, Release Train Engineers, Scrum Masters, and teams - physically in the one room at the one time, considering alternatives is necessary.

It’s important that everyone is present during PI Planning, but that doesn’t mean they have to be physically present to make PI Planning a success

Remote PI Planning with Easy Agile Programs

We are now beyond the period where we needed to adapt to remote work. Our own business agility has been tested and we have needed to evolve.

Since we first launched Easy Agile Programs, we have continued to build on the capabilities it has to help teams and organizations around the world thrive in a remote environment.

With a simple but powerful tool seamlessly integrated with Jira, the latest version of Easy Agile Programs has a range of features aimed at helping distributed teams through the PI Planning ceremony and to build out a long-lived but flexible digital Program board in Jira.

Moving to remote or hybrid PI Planning doesn’t need to jeopardize yours or your customer’s success. In fact with the right tool, it can enhance it by saving time on context switching, complex configurations and double-handling.

The PI Planning Agenda

Regardless of whether you are following a more traditional 2-day PI Planning agenda, or need to accommodate a split agenda in a distributed environment, the core agenda items are the same. We’ll walk you through each of those and how Easy Agile Programs supports these key features.

Source: Scaled Agile

Setting the business context

PI Planning kicks off with the Business Owner(s) or senior executives giving a presentation where they describe “the current state of the business, share the Portfolio Vision, and present perspective on how effectively existing solutions are addressing customer needs” (Scaled Agile - PI Planning).

In the Program details section of Easy Agile Programs, Business Owners can share a recorded video presentation with all members of the ART, or a Zoom or video conferencing link.

As a result, the presentation isn’t restricted to team members being physically present for this agenda item, and can be referred to throughout the PI Planning session and beyond.

Setting the Product/Solution Vision

Next in the agenda, Product Management will present the current vision, typically in the form of the top 10 upcoming features.

Rather than presenting the top 10 features in a list on a slide or document, Program Managers can access Jira Features (Epics) right within Easy Agile Programs and can schedule them onto a visual timeline for the duration of the Program Increment (PI).

The Program Roadmap ensures all teams are aligned on the committed features for a PI and provides visibility into the direction of the Program for all stakeholders.

It’s at this point in the PI Planning ceremony that Product Managers may also call out any upcoming milestones.

According to Scaled Agile, ‘Milestones mark specific points on the development timeline, and they can be invaluable in measuring and monitoring the product evolution and risk.’

Easy Agile Programs enable you to create highly visible milestones on the Program Roadmap to highlight key delivery dates, external events, or business milestones. These can also be created on the Program Board, or at the team level on the Team Planning Board. They are represented by colored flags at the top of the Roadmap that spans the team swimlanes that make up the Program.

Team Breakout Sessions

In the team breakout, teams work individually to estimate the capacity for each Sprint in the PI. Teams create new or identify existing issues from their backlog that will help achieve the set features. The draft team plans are visible to all members of the ART.

To make this easier, Easy Agile Programs has dedicated Team Planning Boards accessible to all who have access to the Program. Simply clicking on a team’s name will take you to their team Planning Board where they are able to set capacity for each sprint within the PI:

Teams have the context of their committed features at the top of their Team Planning Board, both those that are shared by more than one team in the ART or are specific to their team.

To plan the work needed to achieve these features, teams are able to drag and drop existing issues from their backlog or quick create new issues right within the planning board.

During this session, teams also create draft PI Objectives. These are a critical part of linking what the team is working on to broader business objectives, and you don’t need to leave the Team Planning Board to create them.

In Easy Agile Programs you can indicate whether the objective is committed or uncommitted, provide a description, and directly link the Jira issues scheduled to achieve this objective with the objective itself:

During PI Planning, Business Owners will have a discussion with teams about their PI Objectives which provides an invaluable opportunity to align. The Team Planning provides the artefact to facilitate those conversations, and allows Business Owners or stakeholders to assign a business value directly within the tool.

An important part of the team breakout sessions is identifying any dependencies or potential risks to scheduling work. Through drag and drop or create dependencies mode, it is very easy to create and visualize dependencies across teams in the Team Planning Board.

Aside from highly visible dependency lines, our customers also appreciate being able to see the health of those dependencies. If a dependency line is green it means the dependency is healthy, if it’s orange it is at risk, and if it is red it means we are blocked i.e. the work needed to be done to achieve an earlier piece of work is scheduled after it.

And the best bit of all? This is visible to all in the ART in a digitized SAFe Program Board.

On the Program Board, we have the option to have a detailed view with team-level issues visible or to hide them so we can just see features.

Wondering whether Easy Agile Programs could support your organization's PI Planning? With a seamless Jira integration, it takes minutes to set up.

Free trial of Easy Agile Programs

Try now

Program Risks

During PI Planning, we need to be able to identify risks and dependencies to assess whether teams in the Agile Release Train are set up for success to reach their PI Objectives.

A digital Program Board provides transparency to all members of the ART during PI Planning and acts as a single source of truth during and beyond planning. A digital artefact enables the Program Board to become more than a plan, and lives longer than the strings and post-it notes on a physical wall.

We know that visualizing feature-level dependencies is crucial to not only understanding but also troubleshooting the health or status of a PI. Not just during PI Planning itself, but also throughout the PI during execution.

The Program Board in Easy Agile Programs is highly visual and also filterable. Colored lines that indicate the health of the dependency ensure we have an at-a-glance view of significant dependencies that pose a risk to our PI.

Additionally, our scheduling conflicts feature surfaces when there is work scheduled outside of its associated feature, to immediately and clearly indicate where there is a risk.

The ability to filter by dependency health and team in Easy Agile Programs helps to focus conversations around risks during PI Planning.

Plan rework

After presenting plans to the ART and discussing scope, cross-team dependencies, required resources, and risks, teams then proceed to a confidence vote.

If needed, a closing part of planning is to rework any plans so that all teams within the Agile Release Train are confident in what they are committing to.

This may involve rescheduling to address dependencies, breaking work down further, adjusting estimations, etc.

Reworking is simple and streamlined within Easy Agile Programs. The ability to inline edit issue estimates and summaries in real time makes any rework fast and simple. Dragging and dropping an issue easily reschedules it and any impact on associated dependencies can be seen all at once.

All changes made to issues in Easy Agile Programs are automatically reflected in Jira.

Find out how Easy Agile Programs can make PI Planning easy for your collocated, hybrid or remote teams.

Join a product tour to walk through Easy Agile Programs

Join a demo

What about beyond planning?

We’ve examined the merits of remote PI Planning using a digital tool like Easy Agile Programs but something that so often gets overlooked is - what happens after planning?

A plan remains just that if it’s not translated into action. A plan isn’t made not to be fulfilled, and this is where a distributed or hybrid environment can be challenging.

Your Program Board may set you up for success, but ask yourself - how will you know if you’re on track to achieve it?

This is where having a digital, user-friendly tool that uses native Jira issues helps. At the end of PI Planning, teams have created a plan in the form of a Program Board in Jira, but they are also ready for sprint one as soon as PI Planning is done.

From there, the Program Board is set up and capable of evolving, not rolled up and stored away. This is what Easy Agile Programs is designed to do - to provide transparency but also flexibility so that the plan can necessarily adapt and be agile while maintaining momentum towards progress.

So what’s up next for Easy Agile Programs? Can you help us improve it? Check out our product roadmap and if there is something missing let us know.

‍

Should you form cross-functional agile teams?

In large, conventional organizations, multiple departments manage specific functions. Marketing, finance, HR and sales teams work in silos, often focused on their own outcomes rather than being primarily driven by the customer and the market.

Yet even before the pandemic hit, organizations recognized the need to manage change and make decisions quicker than ever before to keep up with competitors. Along came covid, and those needs vastly intensified.

To thrive in an uncertain, complex, and ambiguous world, many organizations are moving away from silos and racing towards enterprise agility, forming networks of empowered cross-functional agile teams.

But the change from siloed departments to agile teams means change, and change can be difficult.

In this article we weigh up the pros and cons of each operating model.

Key points

• Communication, collaboration, and employee engagement are often better in cross-functional teams.
• By iteratively testing solutions quickly, cross-functional teams can boost productivity, cut costs, and deliver better results.
• There may be bumps along the road before a newly formed cross-functional team matures and reaches its potential, but you can take steps to help them succeed.

"The two most urgent reasons for adopting Agile are the speed and flexibility required by working environments that continue to be bother unpredictable and volatile." State of Agile Report

What are cross-functional agile teams?

Cross-functional agile teams (sometimes known as cross-functional scrum teams) are a key element in any organization’s agile development.

The team brings together people from across the business with different expertise and skillsets. Together, the team works toward a common goal.

Usually made up of 5 to 11 people, the team defines, builds, tests and delivers projects in sprints or iterations.

"The ability for the team to support each other, collaborate with each other and align to the goal are wonderful ways to measure agile."

William Rojas, Adaptavist

What are the benefits of cross-functional agile teams?

There are many benefits of having cross-functional agile teams in your organization. Here’s our top five.

1. Cross-functional teams communicate and collaborate better

Siloed teams can spend many hours a week in unproductive meetings as they negotiate resources and manage conflicting priorities. On the other hand, Agile teams align on goals and objectives from the beginning of each project. This helps make their subsequent meetings brief, productive and transparent. Each person is accountable and empowered to share progress and solve problems. As a result, agile teams are often more engaged and passionate about their work.

2. Cross-functional teams are responsive

In silos, each team is responsible for an aspect of a project with limited visibility into what other teams are doing. This can lead to blockers or conflicting priorities, creating rework and delays. They may also find they lack specific skills as the project goes on, leaving teams rushing to fill the gaps and causing further delays. Moving to agile teams means having the necessary skills and resources available, as well as identifying conflicting priorities and blockers early. This helps agile teams rapidly iterate, continually improve, and deliver results.

3. Cross-functional teams are innovative

In siloed organizations, employees can get caught up in their departmental group think. The limited exposure to other teams makes employees less likely to question established practises or suggest improvements. In cross-functional agile teams, perspectives from people across multiple teams are shared from the outset. Because people from different skills approach problems in different ways, this can lead to great ideas and business innovation.

4. Cross-functional teams help the business adapt to change

With their iterative approach and frequent communication, cross-functional agile teams can problem solve and change directions fast. They don’t face the renegotiation, reprioritization, and delays that can hold siloed teams back. Instead, businesses with cross-functional teams can better respond to changing market and customer needs.

5. Cross-functional teams consistently focus on the big picture

Cross-functional agile teams understand the ‘why’ behind the work they’re doing, and they come together with a focus on the customer experience. This shared focus dissolves the barriers between the different functions within the team. Deliverables are mapped to high-level business objectives which deliver greater value to the end-user.

What are the downsides of cross-functional agile teams?

If cross-functional teams are done right, there really are no downsides. What organization doesn’t want increased collaboration, innovation, customer focus and faster delivery?

That said, there can be bumps and conflict as people learn to adapt to the agile mindset – and this is where cross-functional teams can fail to deliver. Here are some of the common challenges large organizations face when moving to cross-functional agile teams:

• Cultural resistance with people reluctant to let go of the old way of doing things.
• No clear accountability, leaving teams unable to make quick decisions and people clinging to a sense of ownership over their work.
• Lack of alignment with goals which can lead to misunderstandings, rework, and potential conflict.

With this in mind, it may take a little time and support for a newly formed agile team to find its wings.

"Often the way teams become agile is just by doing it, trying it, and continuing to evolve and committing to that approach. So, if you haven't started - just get started. That's often the biggest struggle."

William Rojas, Adaptavist

The first step is to just get started

Being agile means changing an organization’s processes and people structure, and it can seem like a lot of hard work. But if businesses don’t transform so they can capture the productivity, speed, customer, and employee engagement benefits; they’re at risk of being left behind.

Cross-functional agile teams can be your key adapting fast and getting ahead. There’s no doubt they can deliver outstanding results – if you take the right steps to set them up for success.

For concrete advice on how to drive successful cross-functional agile teams and avoid failure, sign up for our free on-demand webinar - ‘Do’s and Don'ts of Agile Teams with Adaptavist’.

The webinar will take a deep dive into the SAFe agile team together with our partner and SAFe expert Adaptavist.

Keen to scale agile and form successful cross-functional teams?

Come along to a free, 40-minute on-demand webinar to find out how

‍

Success for agile software teams revolves around collaboration, flexibility, and efficiency. Whether you're a coach or Release Train Engineer supporting multiple teams, or a scrum master or engineer aiming for improvement within your team, honing your dependency management skills will boost efficiency and productivity.

While dependencies often seem like hurdles, here's an insight: they can be a powerful strategic tool to enhance your agile team's performance. In this post, we'll explore how you can leverage dependencies to guide your team towards greater efficiency and success.

Agile Team Autonomy

At the heart of agile is the concept of autonomy and self-management. It's all about empowering teams to own the end-to-end delivery of their work with minimal dependencies. This means optimizing their workflow rather than relying on other teams to deliver value to users. When teams need to depend on others, the flow of work becomes less predictable.

In larger, more complex companies, dependencies are often unavoidable due to the sheer size and intricacy of systems. The real challenge is transforming these dependencies into opportunities for improvement rather than roadblocks. By improving the visibility of these dependencies, teams can better understand them, prioritize and sequence work effectively and manage delivery planning and execution more efficiently.

More than one-third of agile teams report that team silos and the delays that result are a problem

17th State of Agile Report, Digital.AI

Dependency visualization

Improving the visibility of dependencies starts with open communication and transparency. When team members are comfortable sharing their tasks and challenges, you create a culture of trust and collaboration. This transparency is critical for identifying dependencies early and managing them effectively.

Software that allows teams to map out dependencies clearly can be a great tool for improving the visibility of work, making it easier to track their status and plan accordingly. Regularly updating and reviewing the dependencies you've mapped keeps everyone on the same page and helps you anticipate potential bottlenecks before they occur.

Easy Agile TeamRhythm is a user-friendly app that integrates seamlessly with Jira to support team planning, which includes visualizing dependencies. You can display dependencies by type and risk, and see dependencies both within your team and with other teams.

Dependency Patterns

Once you're able to see dependencies clearly, you might recognize patterns forming. These dependency patterns can show where a team is relying too heavily or too dependent on another team to deliver work.

Consistent bottlenecks highlight opportunities for improvement, like a change in team composition. When you notice these patterns, it's essential to reassess and implement strategies to become more self-reliant, ensuring a smoother flow of work and improved delivery timelines.

Prioritizing and Sequencing Work

Once dependencies are identified and made visible, you can improve the flow of work by organizing tasks in a sequence that avoids work being delayed by other tasks. Not all tasks carry the same weight or urgency, and understanding the critical path—the sequence of tasks that determines the fastest time to deliver value—can help focus efforts where they are needed most.

Sequencing work thoughtfully ensures that dependent tasks are tackled in the right order, minimizing delays and rework. This strategic approach to task management not only enhances team efficiency but also supports a smoother workflow and avoids delivery being derailed at the last minute.

Better Collaboration

By identifying and visualizing dependencies, you spot bottlenecks early, re-prioritize tasks, and manage delivery plans effectively. More importantly, it empowers your team to take complete ownership of their tasks while constantly improving their workflows.

Remember, every dependency is a piece of a larger puzzle that holds the potential to boost your team's efficiency. By understanding and managing these dependencies proactively, you can ensure smoother workflows, fewer roadblocks, and a highly efficient agile team.

‍

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.

How organized are your Jira boards? On the scale of “well-thought-user-stories-beautifully-prioritized-by-customer-value” to “the-digital-equivalent-of-a-90’s-era-laminate-desk-cluttered-by-sticky-notes-and-old-coffee-cups”, where do yours sit?

It might be time to find a tool to help you whip your Jira issues into shape. And the best way to keep things in shape is to visualize the work in one place.

Read on for tips and to see how Easy Agile TeamRhythm helps you prioritize work effectively.

Visual task management

Put simply, when you can see something clearly, it’s easier to understand and manage. Enter: visual task management.

Visual task management uses boards to display and track work, which can give you a view of complex project tasks that makes it easier to comprehend.

For those of us who work in Jira, well yes we can see our epics, stories and tasks on the screen, but it isn’t always clear how they relate to each other.

That’s where a tool like a User Story Map, such as the one in Easy Agile TeamRhythm, offers so much value.

Get to the benefits

Giving yourself the ability to visualize your work comes with a long list of benefits. When your whole team can see the work laid out before them, communication is easier and teamwork can improve.

1. Consistent communication

Local and remote teams can see the same view of work from any location. Epics across the backbone with linked issues lined up beneath. When work is added or changed, you still have a central source of truth that is shared by everyone, no matter where they’re located.

2. A time-saving tool

Sprint or version planning is quick and easy when team members have all the information they need in a single view. Planning is much easier when initiatives, epics, user stories and subtasks along with story points and goals, can all be seen in one place.

Easy Agile TeamRhythm provides this all-in-one view, along with the ability to create and estimate new issues on the story map, and sequence them with drag and drop. Easy.

3. Avoid unexpected roadblocks

Ever had a release derailed by an unexpected dependency? For a smooth and dependable release, you need visibility of issues that are dependent on others.

We’ve made it easy to visualize the dependencies between issues on the TeamRhythm User Story Map, so you can avoid unexpected delays and keep delivering value to your customers.

You can choose to see dependencies between issues that are on the same board (internal dependencies), and where one issue is on another board (external dependencies). This gives you a clear picture of how work should be prioritized so that you avoid roadblocks and manage delays before they become a problem.

Read more: Dependency lines on the TeamRhythm User Story Map >>

4. Productivity increases

Working life is better when you can see how your contribution makes a difference. When everyone in the team can see how their work is important, and ideas for how to do things better start to flow, that’s when you start smashing your goals.

We’ve designed Easy Agile TeamRhythm to help teams focus on continuous improvement. That is something for everyone to get excited about because the team leads with their ideas for how they can make their working life better. Turn those ideas into Jira issues in just a few clicks so you can put things into action in the very next sprint.

TeamRhythm helps you see what to do first

Laid out clearly in a User Story Map format, with the ability to overlay a map of dependency lines, TeamRhythm makes it really clear which issues need to be tackled first to make sure that you can keep delivering for your customers.

Everyone in the team has an instant view of their priorities. Communication is streamlined. Collaboration is simplified and productivity increases. Doesn’t that sound great?!

Watch a demo, learn about pricing, and try for yourself in our sandbox. Visit the Easy Agile TeamRhythm Features and Pricing page for more.

Easy Agile TeamRhythm

KEY FEATURES

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.

"Bottleneck" is a buzzword you don't want to hear. When it comes to your production process, maximizing your time and budget is all about keeping efficiency high. However, simply cutting the steps in your process may not make your customer any happier. If you want to achieve a high return on investment and increased customer satisfaction, value stream mapping is an ideal way to keep your team on track.

What is value stream mapping?

Value stream mapping (VSM) is a technique from the lean principles methodology that helps you visualize the steps you need to take to deliver a finished product or service. Value stream maps outline the flow of information and the physical materials to see where value is added for the customer. The purpose of VSM is to increase efficiency by reducing waste in the production process.

Widely known as the lean manufacturing method used in the Toyota Production System, VSM is now often used to eliminate bottlenecks in other industries like software development, supply chain, and healthcare. It's a versatile technique that can help many organizations shine. 🌟

Streamline visibility and provide transparency of your Program for all teams

Easy Agile Programs

Join a demo

Why value stream mapping matters

When companies aim for efficiency, they often focus on reducing the total amount of production steps required. But customers don't always see what happens behind the scenes. Decreasing the length of your workflows mainly benefits your process without changing the experience for them. On the flip side, the value stream mapping process keeps your team members aware of customer needs, so your business can stand out.

For teams that use value stream mapping, reducing inefficiencies is all about cutting production process steps that don't add value. Value stream maps are a visualization of where you're wasting effort. They show your team that keeping steps within your process is okay — but each of those steps should help customers in some way. As a result, VSM prevents overproduction while ensuring your customers are happy with your final product or service.

You can achieve better lean agile workflows with value stream mapping and effectively keep up with customer demand. 💪

Value stream mapping terms

A typical value stream map is divided into three key sections — information flow, material flow, and lead time ladder — that help you see where process improvements can occur. To help you complete each part of a value stream map with greater ease, we'll explain a handful of common terms that you'll come across in each section.

As you learn these terms, you can refer to this Microsoft template to see a few VSM symbols that you'll often use.

Information flow

At the top of a standard value stream map is an information flow section that shows how data transmits between your team members, customers, and other stakeholders. Common terms you'll need to know to complete this section include:

• Customer: This is the consumer who will receive your final product. Your customer is represented in the upper right corner of your map.
• Supplier: This is your organization. Suppliers are placed in the upper left side of value stream maps.
• Dedicated process flow: This is a process or department (like "production control") that information flows through.

Material flow

In the middle of a value stream map is a material flow section that shows how you take your product or service to delivery, step by step. Each box represents a unique task, which may be performed by the same team or by another after a material handoff.

To complete the material flow section, you need to know these terms:

• Shipments: On value stream maps, "shipment" arrows point from the supplier to the first step in the material flow, or from the last step to the customer. They show how your information flow is related to the start and end of your production process. For example, an arrow can show how raw materials move between the supplier and factory or how software access is "sent" to a user.
• Cycle time (C/T): This metric represents the amount of time required between shipments.
• Inventory: Inventory is what's produced between each stage of the production process. Your inventory is usually written below a triangle with a "I" within it. 🔺

Lead time ladder

At the bottom of a value stream map is usually a time ladder that helps you visualize your lead time, which is the average time spent on each step of your material flow.

Kaizen burst

Throughout your value stream map, you can include Kaizen bursts. These represent bursts of activity (like a sprint) in which your team focuses on resolving a specific issue — such as processing customer returns — to quickly remove potential bottlenecks. The symbols for Kaizen bursts look like comic book explosions to grab your attention. 💥

How to create a value stream map

When you're ready to get started with value stream mapping, select the specific product or service that you want to create a map for. While all production processes can benefit from continuous improvement, you should ideally start with a product or service that could benefit the most from VSM. Once you've made your selection, follow these steps with your VSM team:

1. Define your objective: Identify what you want to change for the customer as a result of the value stream mapping process. For example, you might want to improve the quality of a product or the speed with which you deliver a service.
2. Clarify your scope: Define the start and end of your value stream map. You can create a map that includes all of the steps between concept and delivery, begin with an inefficient part of your value stream, or end with a contract agreement instead of a traditional delivery.
3. Outline your process: List each step of your production process. Begin by speaking with team members from each department involved in the process to gather any needed insights. Your list should include non-value producing steps. Collect data about cycle times, lead times, inventory, and more to understand each step even further.
4. Create and evaluate your current state map: Using the information you’ve gathered, create a map that reflects the current state of your process. Work with your team to identify which steps are productive and where improvements are needed. This map will allow you to pinpoint areas of waste, like long process times or software downtime.
5. Develop a future state value stream map: Create a second map that illustrates an improved process that eliminates non-valuable steps. This will be the map you'll ultimately follow to reach your objectives.
6. Build an implementation plan: To start moving toward your future state, establish how your team will implement the new process. Include what metrics you'll keep an eye on to ensure you're on track to reach your objectives. You can also establish how frequently you'll review your progress and adjust your future state map (if needed) during the implementation phase.

📣 Achieve team alignment at scale with Easy Agile Programs

Join a demo

Continue adding value for your customers

Learning to see from your customer's perspective is crucial to ensuring you stand out from your competitors. Following the value stream mapping process can help you visualize where your team is producing value and where you're doing extra work that can easily be eliminated.

To continue adding value for customers, learn how Easy Agile Programs can help you dive deeper into your product’s customer's journey.

Try Easy Agile Programs for Jira

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.

Story points can be a little confusing and are often misunderstood. Story points are an important part of user story mapping, and many agile teams use them when planning their work. But they aren't as simple as adding numbers to tasks or estimating how long a job will take.

Even if you’ve been using story points for a while, you’ll find that different teams and organizations will use them differently.  

So, let’s define story points, discuss why they’re so useful for agile teams, and talk about some of the different ways teams implement them in story mapping and sprint planning.

What are user story points?

Story points are a useful unit of measurement in agile, and an important part of the user story mapping process. You assign a number to each user story to estimate the total effort required to bring a feature or function to life.

When to estimate story points

User stories can be estimated during user story mapping, backlog refinement, or during sprint planning.

Once a user story has been defined, mapped to the backbone, and prioritized, it's time to estimate the story points. It is a good idea to work with your team to do this, as each team member plays a different role in different stories, and knows the work involved in UX, design, development, testing, and launching. Collaborating on story point estimation will also help you spot dependencies early.

It is best to assign story points to each user story before you sequence them into releases or sprints. This allows you to assess the complexity, effort, and uncertainty of each user story in comparison to others on their backlog, and to make informed decisions about the work you decide to commit to each sprint or release.

How to estimate user story points

When estimating story points, you're looking at the total effort involved in making that feature or functionality live so that it can deliver value to the customer. Your team will need to discuss questions like:

• How complex is the work?
• How much work is needed?
• What are the technical abilities of the team?
• What are the risks?
• What parts are we unsure about?
• What do we need in place before we can start or finish?
• What could go wrong?

Tip: If you're having trouble estimating a story or the scope of work is overwhelming, you might need to break your story down into smaller parts to make multiple user stories.

What is a story point worth?

This is where story points can get a little confusing, as story points don’t have a set universal value. You kind of have to figure out what they’re worth to you and your team (yep, real deep and meaningful stuff).

Here’s how it works:

• Each story is assigned a certain number of story points
• Points will mean different things to different teams or organizations
• 1 story point for your team might not equal the same amount of effort involved in 1 story point for another team
• The amount of effort involved in 1 story point should remain stable for your team each sprint and it should remain stable from one story to another
• 2 story points should equal double the effort compared to 1 story point
• 3 story points should equal triple the effort compared to 1 story point… and so on

The number you assign doesn't matter - what matters is the ratio. The story points should help you demonstrate relative effort between each story and each sprint.

Estimating story points for the first time

Because story points are relative, you need to give yourself some baseline estimates for the first time you do story point estimation. This will give you a frame of reference for all future stories.

Start by choosing stories of several different sizes:

• One very small story
• One medium sized story
• One big story

...a bit like t-shirt sizes.

Then assign points to each of these baseline stories. Your smallest story might be 1. If your medium story requires 3 times more effort, then it should be 3. If your big story requires 10 times the effort, it should be 10. These numbers will depend on the type of stories your team normally works on, so your baseline story numbers might look different to these.

The important thing is that you’ll be able to use these baseline stories to estimate all your future stories by comparing the relative amount of effort involved.

Over time, you and your team will find estimating user stories becomes easier as your shared understanding of the work develops. This is where story points become most valuable, helping your team align expectations and plan more effectively.

Make estimation easier

An app for Jira like Easy Agile TeamRhythm makes it easy to see team commitment for each sprint or version, with estimate totals on each swimlane.

Using the Fibonacci sequence for story point estimation

Some teams use the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, 34, 55, 89, etc.) for their story point estimates, rather than staying linear or allowing teams to use any number (1, 2, 3, 4, 5, 6, 7, etc.).

This has its benefits. For example, if you're looking at a story and trying to estimate whether it's a 5, 8, or 13, it's much quicker and easier to come up with an answer than trying to land on the right number between, say, 4-15. You'll likely reach a consensus much more quickly.

This also means you won't be able to average the team's story points to finalize the estimation. Instead, you'll need to discuss the work and decide on the best estimate from a limited set of options.

But it does limit your options - if you have a story that’s more effort than 34, but less than 55, your estimate might be less accurate.

Using story points to estimate velocity

After some time working together most teams will have a good idea about how much effort is involved in each story point.

Of course, timing isn't exact - there's a bell curve, and story points are designed to be an estimate of effort, not time.

But story points (and knowing their approximate timing) can be useful when it comes to figuring out how much your team can get done each sprint.

You should be able to estimate about as many story points your team can manage during a two-week sprint, or whatever timeframe you’re working to.

For example, if your team can usually get through 3 story points per day, this might add up to 30 story points across a two-week sprint. This is your velocity.

Velocity is useful for user story mapping and sprint planning. When mapping your user stories to sprints or versions, you can check the total story points and make sure it matches up with your velocity so you’re not over- or under-committed.

As you can see there are a few different methods for estimating work. The best advice is to be conservative and not overload the team.

Over time, your estimations should become more accurate.

Using Story Points in Scrum, Kanban, and Extreme Programming

Story points are central to estimation and planning processes in many agile methodologies. Scrum and Extreme Programming (XP) rely heavily on story points to gauge the effort and complexity of user stories.

Scrum teams use story points during sprint planning to decide which tasks to include in the upcoming sprint, encouraging discussion that leads to shared context and understanding of the work.

Extreme Programming on the other hand, uses story points to assess the size of features, enabling teams to prioritize and allocate resources effectively. Teams using Kanban can benefit from story points by using them to set work-in-progress limits and optimize the flow of tasks across the board.

While the specific practices may differ, story points can help encourage team collaboration and a more predictable flow of work.

Ceremonies are regular events held by Scrum teams. ‘Agile’ is a broad word describing a different way of working with shorter, time-boxed cycles for releases.

Under the broad umbrella of agile, Scrum is one of the most popular approaches that teams use to organise their work and releases.

Each short iteration of work in Scrum is referred to as a sprint. A sprint is normally a 2 week period where the team focuses on a small slice of work.

The idea is that everyone focuses on 1 slice of work. And that slice is to be completed and shipped to the customer within that same sprint.

Scrum can be broken down into a few important elements:

1. Roles
2. Artifacts
3. Ceremonies

This post will focus on the Scrum Ceremonies.

All of the 4 Scrum ceremonies help ensure the Scrum team stay focused on the slice of work they agreed to focus on in that sprint.

It helps the team with transparency about progress on the work they committed to finish and to raise any issues early before they become blockers.

Let’s have a look at each of the four agile ceremonies in Scrum:

1. Stand up (or daily Scrum)

Goal of the stand up: a brief check-in where the team can raise issues or communicate with the whole team face to face.

Who joins the daily stand up: Developers, Scrum Master, Product Owner

Outcome of daily stand up: the team raises any blockers, but doesn’t have to solve them. Ensure each team member is clear about what they are working on. Each team member should be able to answer these three questions:

• What did I complete yesterday?
• What will I work on today?
• Am I blocked by anything?

When to hold a stand up: daily

Tip: stand ups can be done by business teams and don’t always have to be face-to-face. Here’s a photo of Australian bank ANZ’s executive stand up in action:

And another pic from InsideIT’s stand up:

2. Sprint Planning

Goal of sprint planning: sprint planning helps the team prepare for what work is coming up next. The team discusses each item of work which has been prioritised by the Product Owner.

Who does sprint planning: Developers, Product Owner, Scrum Master

Outcome of sprint planning: that everyone knows what the sprint goal is and how they are going to achieve it. Make sure everyone understands what’s the overall vision or objective of the work.

The team will be comfortable with what work is available to be picked up in the next sprint. The team will discuss any impediments or opportunities and how they can optimise the way the work will be completed.

The team will also estimate the work and draw a line when it is estimated that the effort to complete the work exceeds the team’s capacity or historical velocity.

When to hold sprint planning: at the end of a sprint or very beginning of a new sprint.

Bonus: sometimes in sprint planning you will find things you won’t do, and that’s valuable too.

3. Sprint review

Goal of the sprint review: showcase the work completed and receive feedback from the Product Owner and relevant stakeholders.

Who joins the sprint review: Executive Sponsors, Developers, Scrum Master, Product Owner

Outcome of the sprint review: each team member feels empowered by showcasing their work to the team. The team can celebrate their achievements. Executive team can ask questions. Product owner can provide feedback and check the work is of high quality and satisfies the user story. Works best with drinks and cake.

When to hold a sprint review: at the end of each sprint.

4. Retrospective

Goal of the retrospective: honest discussion about what worked well and didn’t work well. Encourage self-improvement and transparency.

Who joins the retrospective: Developers, Scrum Master, Product Owner

Outcome of a retrospective: receive feedback from the team and seek to improve in the following sprint. The beauty of agile and Scrum is the fast feedback loop.

If something isn’t working well, it only hurts the team for a maximum of 2 weeks. It can then be addressed at the retrospective and action can be taken to address the issue before it gets out of hand.

The outcome should be a commitment from the team to focus on addressing areas that need improvement or continuing behaviours that benefit team health and/or velocity.

When to hold a retrospective: at the beginning of a new sprint, reflecting on a sprint that has just ended.

---

The common theme across these Scrum ceremonies is that they encourage team collaboration, transparency and communication.

In my experience, this is what truly makes agile a better way of working.

It’s not the story points or even the way the backlog is prioritised that makes a difference. The true game-changer of agile is that it helps teams with open and honest communication.

These agile/Scrum ceremonies won’t always work the same for every team.

However, they are a great way to facilitate conversation and encourage continuous improvement.

You may be just starting out, or you may have worked with agile methodologies for a while, but we’re sure you can agree that scaling agile in a large organization can be daunting. PI Planning is key to scaling agile, so we’ve developed this guide to help you run successful planning sessions, and build your confidence for your next scaled planning event.

We'll cover:

• What is PI Planning?
• Why do PI Planning?
• What is the goal of PI Planning?
• What should be included in the PI Planning agenda?
• What happens in the first part of the PI Planning meeting?
• Why is a confidence vote held at the end of PI Planning?
• When is PI Planning held?
• What is a pre-PI Planning event and when is it needed?
• PI Planning in SAFe
• PI Planning in Scrum
• What is the difference between a PI Roadmap and a Solution Roadmap?
• What is a program?
• What is a program board?
• Who should be involved in PI Planning?
• How to prepare for PI Planning
• What happens after PI Planning?
• What is a post-PI Planning event?
• Remote or hybrid PI Planning
• Common PI Planning mistakes
• Using Jira for PI Planning

Let’s start with the basics…

What is PI Planning?

PI Planning stands for Program Increment Planning.

PI Planning sessions are regularly scheduled events where teams within the same Agile Release Train (ART) meet to align and agree on what comes next. Teams will aim to align on goals and priorities, discuss features, plan the roadmap, and identify cross-team dependencies.

The goal is to align the teams to the mission and each other. Here are the essential elements of PI Planning:

• 2 full day events run every 8-12 weeks (depending on the length of your increments)
• Product Managers work to prioritize the planned features for the increment beforehand
• Development teams own user story planning and estimation
• Engineers and UX teams work to validate the planning

Why do PI Planning?

PI Planning is incredibly beneficial for large-scale agile organizations. PI Planning enables:

• Communication
• Visibility
• Collaboration

To understand the impact, let’s look at an example of a large organization that hasn’t yet implemented PI Planning. This organization has 250 teams and 6,500 team members. These teams rarely speak to each other, outside of dealing with a critical issue that has forced them to collaborate.

Alignment across these teams happens at the leadership team level, and they have multiple levels of managers in between who cascade information down with varying success. There is a constant battle for resources, budget, and opportunities to work on the most exciting projects.

Their projects have a habit of conflicting - one team would release something and then it would break something in another team’s project.

PI Planning is the first time many big companies get their teams together in a room or on the same call to talk to each other. This is a chance to have important conversations about who is working on what.

Why is this important?

1. When you’re touching a system or a code repository, you need to know how it’s going to impact another team
2. You might need to do some work to enable another team to work on their feature first (and vice versa)

With proper planning and collaboration, teams can get things done more effectively, release with more predictability, and stay on budget.

All very good reasons to do PI Planning.

What is the goal of PI Planning?

PI Planning is an essential part of the Scaled Agile Framework, a framework that’s designed to bring agile to large companies with multiple teams.

SAFe PI Planning helps teams in the Agile Release Train (ART) synchronize, collaborate, and align on workflows, objectives, releases, and more.

Without PI Planning, teams don’t have structured communication. They may not know what the other teams are working on, which can cause a lot of problems. For example, two teams might be working on different features without realizing there’s a dependency, which could hold up the release or require a significant rework of the code.

The goal of PI Planning is to have all your teams aligned strategically and enable cross-team collaboration to avoid these potential problems.

Now that we’ve covered off the “why”, let’s dig a bit deeper into the “what”. The best way to get a picture of what happens during PI Planning is to take a look at an agenda.

What should be included in the PI Planning agenda?

Here’s a standard PI Planning agenda template:

Day 1 AgendaDay 2 Agenda8:00 - 9:00 | Business Context8:00 - 9:00 | Planning Adjustments9:00 - 10:30 | Product/Solution Vision9:00 - 11:00 | Team Breakouts10:30 - 11:30 | Architecture Vision and Development Practices11:00 - 13:00 | Final Plan Review and Lunch11:30 - 13:00 | Planning Context and Lunch13:00 - 14:00 | ART Risks13:00 - 16:00 | Team Breakouts14:00 - 14:15 | Confidence Vote16:00 - 17:00 | Draft Plan Review14:15 - ??  |Plan Rework?17:00 - 18:00 | Management Review and Problem Solving?? | Planning Retrospective and Moving Forward

Source: scaledagileframework.com/pi-planning

This agenda might be perfect for you, or you might make changes based on the needs of your teams.

Distributed teams, very large ARTs, and other factors might require you to be creative with the schedule. Some sessions may need more time, while others can be shortened. If you have teams in multiple time zones, your PI Planning agenda may need to go over 3-4 days. If it’s your first PI Planning event, try the standard agenda, get feedback from your teams, and experiment with different formats next time.

What happens in the first part of the PI Planning meeting?

The first part of the PI Planning meeting is designed to set the context for the planning that happen next.

Day 1 usually kicks off with a presentation from a Senior Executive or Business Owner. The agenda allows an hour to talk about the current state of the business. They highlight specific customer needs, how the current products address these needs, and potential gaps.

After that, the Product Management team will share the current vision for your product or solution. They’ll talk about any changes that have occurred since the last PI Planning session (usually around 3 months prior). They’ll describe what’s coming up, including milestones and the next 10 features that are planned. This session should take around 1.5 hours.

Why is a confidence vote held at the end of PI Planning?

The confidence vote is a seemingly small but very important part of PI Planning towards the end of the event.

It is important the team is confident in committing to the objectives and work that is planned. The Release Train Engineer will ask teams to vote on this.

Everyone participating in planning needs to vote. This could be via a raise of hands (and fingers) or it could be via the tool you’re using. For example, the Team Planning board in Easy Agile Programs allows each team member to enter their confidence vote.

If the average vote across the room is at least three out of five, the plan is a go-ahead. If it’s less it’ll need reworking (until it reaches a high confidence level). If anyone votes just one or two, they’ll have the chance to share their reasoning.

The confidence vote is all about making sure that the attendees are in alignment and that they agree that the plan in its current form is possible within the given timeframe. Speaking of timing, let’s talk about how and where PI Planning actually fits into your company calendar.

When is PI Planning held?

Many companies find that 8-12 weeks (which adds up to 4-6 x 2-week iterations) is the right amount of time for an increment.

Some companies hold quarterly PI Planning, for example:

• Q1 PI Planning: December
• Q2 PI Planning: March
• Q3 PI Planning: June
• Q4 PI Planning: September

However, the timing and frequency will depend on how long each program increment is scheduled to last and may need to accommodate holidays.

The good thing about PI Planning events is that they happen regularly on a fixed schedule, which means you can plan for them well ahead of time. That means teams and Business Owners have plenty of notice to ensure they can show up for the event.

This means that what happens in preparation for PI Planning can be just as important as the event itself.

What is a pre-PI Planning event and when is it needed?

A pre-planning event - separate to PI Planning - is to make sure that the ART is aligned within the broader Solution Train before they do PI Planning. It’s all about synchronizing with the other ARTs to ensure the solution and organization are heading in the right direction, together.

You’ll need to organize a pre-PI Planning event if you’re operating at the Large Solution, Portfolio, or Full SAFe levels. Essential SAFe is more basic and does not have a Solution Train, so if you’re operating at this level, you won’t need pre-PI Planning so formally.

Here are a few of the roles that should be invited to the pre-planning event:

• Solution Train Engineer
• Solution Management
• Solution Architect/Engineering
• Solution System Team
• Release Train Engineers
• Product Management
• System Architects/Engineers
• Customers

They’ll look at the top capabilities from the Solution Backlog, Solution Intent, Vision, and Solution Roadmap. It’s really a lot like PI Planning but at a higher level, across the overall solution and not just the individual ART.

The event starts with each ART summing up their previous program increment and accomplishments to set the context. Next, a senior executive will brief the attendees on the current situation before Solution Management discusses the current solution vision and any changes from what was shared previously. Other things that are often discussed or finalized include:

• Roadmaps
• Milestones
• Solution backlogs
• Upcoming PI features from the Program Backlog

In the next section, we'll help to define a few key terms that have been touched on.

PI Planning in SAFe

If you’re adopting SAFe for the first time, chances are it will start with PI Planning. That’s because it forms the foundation of the Scaled Agile Framework.

As Scaled Agile says, "if you are not doing it, you are not doing SAFe."

Definition:

SAFe or the Scaled Agile Framework™ is a series of guidelines and practices designed to help bring agility into larger organizations, across all teams and levels of the business. The framework is geared at improving visibility, alignment, and collaboration and should lead to greater productivity, better results, and faster delivery.

Whether you’re adopting all 5 levels or just essential SAFe, the foundation of your transformation and the driver for everything is the PI Planning ceremony.

Scrum and Kanban are also agile frameworks (that you may be more familiar with), and these have historically been very effective at the individual team level. SAFe helps to scale agility across teams; to have multiple teams come together to work on the same products, objectives, and outcomes. It goes beyond the team level to include every stakeholder, outlining what should happen at each level of the organization to ensure that scaled planning is successful.

The purpose of SAFe is to improve the visibility of work and alignment across teams, which will lead to more predictable business results.

This is increasingly important for organizations as they respond to changing circumstances and customer expectations. The traditional waterfall approaches fall short because they’re slow and inefficient.

Bigger companies (often with thousands of developers) can’t keep up with the innovation of smaller, more nimble startups. Along with bigger teams, larger organizations often have stricter requirements around governance and compliance, making it more complex to launch a new feature and deliver new value to customers.

These companies are looking for new ways to organize people into projects and introduce more effective ways of working that use resources more effectively and provide more predictable delivery. If they don’t, they may not survive.

SAFe is a way for these companies to start moving in a more agile direction.

PI Planning is a vital element of SAFe. It’s a ceremony that brings together representatives from every team to help them work together, decide on top features to work on next, identify dependencies, and make a plan for the next Program Increment. As a result, there’s greater visibility across all the teams, changes are made more frequently, and teams work with each other - not against each other. From there, these massive companies can speed up their processes, work more efficiently, compete with newer and more nimble companies, and stay viable.

SAFe and PI Planning are powerful enablers for organizational agility.

While SAFe is a framework designed for larger organizations, there isn't a reason stopping smaller companies from doing a version of PI Planning, too. All you need is more than one agile team to make it worthwhile.

PI Planning in Scrum

You can also use PI Planning as part of a simple Scrum approach.

Scrum Framework diagram shows when and how scrum teams can implement PI Planning

Source: Scrum.org

Scrum is an agile framework that helps teams get things done. It’s a way for teams to plan and organize their own work and tackle user stories and tasks in smaller time boxes. This is often referred to as a sprint.

If multiple scrum teams want to work better together (but aren’t necessarily operating within SAFe), they could adopt a version of PI Planning.

For example, these scrum teams could:

• Meet every 10 weeks and discuss the features they are planning to work on
• Get product managers to combine backlogs and prioritize together
• Share resources across the teams, as needed
• Map dependencies and coordinate joint releases

The good news here is that there’s no “one size fits all” approach to PI Planning, so think about how you could adopt the ideas and principles and make it work for your organization and context.

What is the difference between a PI Roadmap and a Solution Roadmap?

There are different types of roadmaps in SAFe, so it’s important to understand the differences and what each roadmap is meant to do.

PI Roadmap

A PI Roadmap is created before your PI Planning event and also reviewed and updated by Product Management after the event is finished. It will usually cover three Program Increments:

1. The current increment (work that’s committed)
2. The next forecasted increment (planned work based on forecasted objectives)
3. The increment after that (further planned work based on forecasted objectives)

Quarterly PI Planning will outline around 9 months of work. The second and third increments on your PI Roadmap will likely change as priorities shift, but they’re still an important part of the roadmap as they forecast where the product is headed next.

Solution Roadmap

The Solution Roadmap is a longer-term forecasting and planning tool for a specific product or service.

It will usually cover a few years at a time, with more specific details available for year one (like quarterly features and capabilities), and more general information (like objectives) for year two and beyond.

What is a program?

A program is where agile teams are grouped together to form a larger group. This is often referred to as the “team-of-teams” level. In simple terms, a program is a group of agile teams.

When you hear people talking about “team-of-teams” or “scaled agile”, they mean taking agile beyond a single team, and asking more teams to join in.

For example, there might be 4 teams working on a NASA spaceship mission to Mars.

NASA decides they want to see if agile can help these teams do better work. So, to start with, the Oxygen team switches from working with traditional Waterfall project management methods to embracing agile principles.

1. Launch team
2. Food team
3. Oxygen team (Agile)
4. Landing team

After a few months, NASA decides that the way the oxygen team is working is going well, so the remaining three teams similarly adopt more agile methodologies:

1. Launch team (Agile)
2. Food team (Agile)
3. Oxygen team (Agile)
4. Landing team (Agile)

Each of these 4 teams are self-organizing, meaning they’re responsible for their own work.

However, now that these teams are all working in the same way, they can be grouped together as a program.

Once you add in the business owners, product management team, systems architect/engineer, and release train engineer, you have all the roles needed to continuously deliver systems or solutions through the Agile Release Train (ART).

What is a program board?

Program Boards are a key output of PI Planning.

Traditionally, they’re a physical board that’s mounted on the wall, with columns drawn up to mark the iterations for the increment, and a row for each team. Teams add sticky notes that describe features they’ll be working on.

• Feature 1
• Feature 2
• Feature 3

Once all the features are added, they work to identify dependencies (features that’ll affect other features) and mark this up by connecting them with red string.

SAFe program boards don’t have to be physical, though. There are a lot of advantages to using a digital program board like Easy Agile Programs, which integrates directly with Jira. We’ll talk more about how you can use Jira for PI Planning towards the end of this guide.

Equip your remote, distributed or co-located teams for success with a digital tool for PI Planning.

Easy Agile Programs

Free Trial

Who is involved in PI Planning?

There are 5 key roles in a PI Planning event:

1. Release Train Engineers
2. Product Managers
3. Product Owners
4. Scrum Masters
5. Developers

Here are the responsibilities for each of these roles during PI Planning:

Release Train Engineer

The Release Train Engineer is a servant leader and coach for the ART. Their role focuses mainly on planning and facilitating the PI Planning event. This means they help:

• Establish and communicate the annual calendars
• Get everything ready (including pre and post-PI Planning meetings)
• Manage risks and dependencies
• Create Program PI Objectives from Team PI Objectives and publish them
• Track progress towards expected goals
• Ensure strategy and execution alignment
• Facilitate System Demos

As the facilitator for the 2-day event, the Release Train Engineer presents the planning process and expected outcomes for the event, plus facilitates the Management Review and Problem Solving session and retrospective.

Product Manager

A Product Manager’s job is to understand the customers’ needs and validate solutions, while understanding and supporting portfolio work.

Before PI Planning happens, Product Managers take part in the pre-PI Planning meeting, where they discuss and define inputs, objectives, and milestones for their next PI Planning events.

In PI Planning, the Product Managers present the Program vision and upcoming milestones. So that they can manage and prioritize the flow of work, they review the Draft plan and describe any changes to the planning and scope based on the Management Review & Problem Solving session. Once the PI Planning event is over, they use the Program Objectives from the Release Train Engineer to update the roadmap.

Following PI Planning, Product Managers play a critical role in communicating findings and creating Solution PI Objectives.

Product Owner

The Product Owners are responsible for maintaining and prioritizing the Team Backlog, as well as Iteration Planning. They have content authority to make decisions at the User Story level during PI Planning Team Breakout sessions.

Product Owners help the Team with defining stories, estimating, and sequencing, as well as drafting the Team’s PI Objectives and participating in the Team Confidence Vote. They’re also responsible for conveying visions and goals from upper management to the team, as well as:

• Reporting on key performance metrics
• Evaluating progress, and
• Communicating the status to stakeholders

Scrum Master

The Scrum Master is a servant leader to the Product Owner and Development team, which means they manage and lead processes while helping the team in practical ways to get things done.

They facilitate preparation for events (including PI Planning) and prepare System Demos. They help the team estimate their capacity for Iterations, finalize Team PI Objectives, and manage the timebox, dependencies, and ambiguities during Team Breakout sessions. The Scrum Master also participates in the Confidence Vote to help the team reach a consensus.

Developer

Developers are responsible for researching, designing, implementing, testing, maintaining, and managing software systems.

During PI Planning, they participate in Breakout sessions to create and refine user stories and acceptance criteria (alongside their Product Owner) and adjust the working plan. Developers help to identify risks and dependencies and to support the team in drafting and finalizing Team PI Objectives, before participating in the Team Confidence Vote.

Do you have a key role in PI Planning? See how the right tool can help you manage your release train or program better.

Watch an Easy Agile Programs product demo

How to prepare for PI Planning

If you want to succeed at PI Planning, you need to prepare.

Every PI Planning event relies on good preparation so that your organization and attendees get the most out of the event and achieve your planning objectives.

The first step is to ensure that everyone involved properly understands the planning process. All people participating in PI Planning (along with key stakeholders and Business Owners) must be clear on their role and aligned on strategy.

Any presenters will also need to get content ready for their presentations.

To ensure that the PI Planning event runs smoothly, make sure that the tools you need to facilitate planning are available and working properly. Be sure to test any tech that you are relying on ahead of time (including audio, video, internet connectivity, and access to PI Planning applications), to ensure that your distributed teams can participate in the PI Planning event. Don’t forget to plan for enough food for everyone, too (planning is hungry work).

What happens after PI Planning?

After PI Planning, teams do a planning retrospective to discuss:

• What went well
• What went not-so-well
• What could be better for next time
• There will also be a discussion of what happens next, which can include things like:
• Transcribing the objectives, user stories, and program board into your work management tool (like Jira)
• Agreeing on meeting times and locations for daily stand-ups and iteration planning
• Making sure that everyone has their belongings and leaves the event rooms clean when they go

The other thing that usually happens after PI Planning events is a post-PI Planning event.

What is a post-PI Planning event?

These are similar to the pre-PI Planning events we looked at earlier. A post-PI Planning event brings together stakeholders from all ARTs within the Solution Train to ensure they’re synchronized and aligned.

Post-PI Planning happens after all the ARTs have completed their PI Planning for the next increment. They present the plans, explain their objectives, and share milestones and expected timelines.

Like PI Planning events, post-PI Planning involves using a planning board, but rather than features, it outlines capabilities, dependencies, and milestones for each iteration and ART. Potential issues and risks are identified, discussed, and either owned, resolved, accepted, or mitigated. And similar to regular PI Planning events, plans go through a confidence vote to ensure they meet the solution’s objectives, and are reworked until the attendees average a vote of 3 or more.

Remote or hybrid PI Planning

PI Planning in person was once standard, but with teams more likely to be distributed, gathering everyone at the office isn't always feasible. This doesn't have to be a barrier.

The most important principle is to ensure that the teams who are doing the work are able to be 'present' in the planning in real-time, if not in person.

This may require some adjustments to the agenda and timing of your planning, but with forethought and support from the right technology, your PI Planning will still be effective.

Tips for remote PI Planning

Remote PI Planning is ideal for organizations with distributed teams or flexible work arrangements. It’s also a lot cheaper and less disruptive than flying folks in to do PI Planning every few months. If you have the right tools and technology, you can run PI Planning and allow everyone to participate, whether they’re in the same room or on the other side of the world.

Here are a few tips for remote PI Planning:

Embrace the cloud

Use online shared planning tools to allow your team to access and interact with information as soon as possible - ideally in real-time. Ensuring that all participants have instant access to the information simplifies the process of identifying dependencies and maintaining a centralized point of reference for your planning. This helps prevent errors that arise from working with different versions and transferring data between sources.

Livestream the event

Live-streaming audio and video from the PI Planning event is a viable alternative to in-person planning. Actively encourage your remote team members to use their cameras and microphones during the event. While it may not fully replicate the experience of having them physically present, it does come remarkably close.

Record the PI Planning event

Ideally, everyone will participate in the PI Planning live. But if your teams are distributed across multiple time zones or some team members are ill, it’s a good idea to record the event. Having a recording to refer back to could also be useful for attendees who want a refresher on anything that has been discussed.

Be ready to adapt

Some teams will change the standard PI Planning agenda to fit multiple time zones, which could mean starting the event earlier or later for some, or even running it across 3 days instead of 2.

Set expectations

A common issue that can arise from having distributed teams tune in remotely is too much noise and interference. Before your first session kicks off, communicate about when it’s acceptable to talk and when teams need to use the mute button. That way, your teams will avoid getting distracted, while still ensuring everyone can participate.

For more tips, check out our blog on how to prepare for distributed PI Planning.

Whether distributed or in person, if your team gets PI Planning right, it makes everything in the upcoming increment so much easier.

📣 Hear how PNI media have embraced virtual PI planning

Common PI Planning mistakes

PI Planning doesn’t always run smoothly, especially the first time. And the framework itself may present a challenge to some organizations. Here are some common mistakes and challenges to keep in mind (and avoid):

Long, boring sessions

Avoid starting your PI Planning event with long sessions filled with dense content. Think of creative ways to make these sessions more engaging, or break them into shorter sessions. Consider different formats that help to involve and engage participants. And be sure to make room for team planning and collaboration.

Tech issues

Any event is vulnerable to technical mishaps, but if you’re streaming audio and video to a distributed team, this can really impact the flow of the event. It’s a good idea to carefully test all the equipment and connections ahead of time to minimize potential problems.

Confidence vote

Some PI Planning participants struggle with the confidence vote concept. People may feel pressure from the room to vote for a plan to go ahead, rather than speaking up about their concerns. Failing to address issues early only increases the risk of something going wrong during the increment.

Time constraints

When you have a large ART of 10 or more teams, there are a lot of draft plans to present and review, so less time is allocated to each team. Chances are that the feedback will be of poorer quality than a smaller ART with 8 teams.

Not committing to the process

PI Planning isn’t perfect and neither is SAFe. However, the process has been proven to work for many organizations, when the organization is committed. Start with the full framework as recommended; you can adapt the framework and your PI Planning event to suit your organization, but be sure to commit to the process that follows. Anything that is half-done will not deliver full results.

Sticking with the same old tools

If something is not working, fix it. For example, too many teams stick with traditional SAFe Program Boards even though they’re not always practical. If the post-it notes keep escaping, the data entered into Jira seems incorrect, or you have a distributed team who want a digital way to be part of your PI Planning event… it’s time to upgrade to a digital program board like Easy Agile Programs.

Using Jira for PI Planning

Jira is the most popular project management tool for agile teams, so chances are you're already using it at the team level.

When you need to scale team agility as part of an ART, it can be difficult to properly visualize the work of multiple teams in Jira. The only way you can do that in the native app is by creating a multi-project board, which is rather clunky.

Traditional PI Planning on a physical board using sticky notes and string may achieve planning objectives for co-located teams, but what happens next? After the session is over, the notes and string need to be recreated in Jira for the whole team so that work can be tracked throughout the increment. This is a cumbersome and time-consuming process that is open to error as sticky notes are transcribed incorrectly, or go missing.

The best way to use Jira for PI Planning is to use an app like Easy Agile Programs to help you run your PI Planning sessions. The integrated features mean you can:

• Set up a digital Program Board (no more string and sticky notes!)
• Do cross-team planning
• Visualize and manage cross-team dependencies, create milestones
• Identify scheduling conflicts to mitigate risks
• Get aligned on committed objectives for the Program Increment
• Visualize an Increment Feature Roadmap
• Conduct confidence voting
• Transform Jira from a team-level tool to something that’s useful for the whole ART

Join companies like Bell, Cisco, and Deutsche Bahn who use Jira to do PI Planning with Easy Agile Programs (from the Atlassian Marketplace).

Looking for a PI Planning tool for Jira?

We’ll continue to revisit this guide in the future. If you have any questions about PI Planning or you notice there’s an aspect we haven’t covered yet, send us an email 📫

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 respond 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.

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

There are so many benefits to user story mapping, 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
• Better prioritization - Organize work into releases based on what’s most important to users and what will deliver a new or complete experience for users
• 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 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 be involved 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

If the last year is anything to go by, read more on: 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.

Introduction to Sprint Reviews PDF

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.

It’s one of the most common practices in agile software development; the flat product backlog. We’ve all seen them, we’ve all contributed to them, and we’ve all inevitably drowned in them.

In its simplest form, a flat product backlog is a laundry list of ‘stuff to do’ that will ultimately provide value to the customer. These actionable items are prioritised (top to bottom) in the order the value will be delivered. If a team is adopting the Scrum method the backlog is split into future sprints to provide an indication of what will be delivered and when.

Depending on the size and requirements of the organisation, the list of things to be done could be 10, 100 or 1,000 actionable items. It’s easy to see how managing the latter comes with the challenges of updating, assigning, grooming and scheduling these items.

What’s Wrong With Flat User Story Backlogs?

So far we know that flat backlogs represent a list of things to be done. This comes with its challenges, and its shortcomings were best described by Jeff Patton when he said;

We spend lots of time working with our customers. We work hard to understand their goals, their users, and the major parts of the system we could build. Then we finally get down to the details — the pieces of functionality we’d like to build. In my head I see a tree where the trunk is built from the goals or desired benefits that drive the system; big branches are users; the small branches and twigs are the capabilities they need; then finally the leaves are the user stories small enough to place into development iterations.



After all that work, after establishing all that shared understanding, I feel like we pull all the leaves off the tree and load them into a leaf bag — then cut down the tree.



That’s what a flat backlog is to me. A bag of context-free mulch

How do you pick an item from a list, and deem it the thing that’s going to provide the most value to your customers, without that additional context?

Shortcomings of a Flat Product Backlog

• The flat backlog makes it impossible to discover the ‘backbone’ of your product — the customers interaction experience with the product
• Arranging user stories in the order they’ll be delivered doesn’t help a product manager explain to others what the system does
• The flat backlog provides no context or ‘big picture’ around the work a team is doing
• A flat backlog makes it hard for the product manager to determine if they’ve identified the relevant user stories
• Release planning is difficult with a flat backlog. How do you prioritise what to build first in an endless laundry list?

User Story Maps

A story map is a visual representation of the journey a customer takes with a product, including the activities and tasks they complete. This visualisation helps the team to focus development on providing the most value to customers and their desired outcomes.

It provides context for teams by answering the following questions:

• Why are we building this?
• Who are we building this for?
• What value will the solution provide for the customer and when?

The story map still showcases the ‘stuff to be done’, the difference here though, is the way in which this information is visualised. As you can see, rather than listing these items out, each item is contextualised under a bigger piece of work. Besides the way the information is visualised, the key difference between a flat product backlog and a user story map, is the focus on the customer journey. Let’s unpack this by breaking down the anatomy of the user story map.

What A User Story Map Achieves that a Flat Product Backlog Can’t

• Focus on Desired Customer Outcomes: the visualisation of the customer journey allows teams to identify and implement features based on customer outcomes, and track progress at a glance against a story map
• Bring the Customer Journey to Life: the transformation of the flat product backlog to a customer centric story map means teams have a better understanding of their customer journey and what their customers want and value
• Prioritising Actions Based on Value to the Customer: visualisation of the customer journey allows teams to prioritise work based on “value to customer”, resulting in better outcomes and less waste

Are you getting lost in your flat product backlog? Are you stuck in an endless development cycle, but not really sure for who or why your building features?

Easy Agile TeamRhythm

Easy Agile TeamRhythm supports User Story Mapping, sprint or version planning, backlog refinement, and team retrospectives.

A couple of weeks ago, our partner Adaptavist released their State of the Atlassian Ecosystem Report which surveyed approximately 1,000 users of Atlassian tools and services. After reading the 50+ page document, I decided that the reports' insights were extremely valuable and worth sharing.

You can also download the full report here. It is a fantastic read and incredibly interesting for anyone working within the Atlassian ecosystem.

Key take-aways from Chief Information Officer at Adaptavist

• Despite a turbulent year, Atlassian ecosystem continues to grow and evolve. This year the company surpassed $US500 million in quarterly revenue for the first time
• For those who rely on Atlassian Server, the company’s decision to sunset its Server products has forced some soul searching and tough decision-making
• Atlassian continues to focus on driving improvements around security, customisation, and feature parity
• Let's open up collaboration across the ecosystem and find new ways to tackle the challenges that lie ahead.

Key findings

• Usage Up: Atlassian usage up despite decrease in IT spend overall. Including Jira, Access, Trello, Align and Advanced Roadmaps
• Non Tech User Up: Increase in non-technical teams using Atlassian tools including Operations and Marketing.
• Challenge: The biggest integration challenge organisations face is connecting Atlassian with other third-party apps such as Zoom, MS Office, Slack, Gitlab, Github, Salesforce.
• Cloud: Atlassian Cloud adoption is increasing slowly but surely, 28% 2020 to 34% 2021. Server represents the majority of deployment followed by DC
• Challenge: Customisation (57% concerned), app integration (48% concerned), cost, and feature functionality (43% concerned) are the main concerns about migrating to Atlassian Cloud
• Changing deployment: 65% of respondents are expecting to change how they deploy Atlassian products in the next three years. Sunset of Server spurring this.
• What people want more Automation - drives business processes, reduce operational costs and improve integration with tools
• DevOps is Up: 27% of respondents developing a DevOps strategy in next 3 years. Adoption across verticals. Why? Automates workflows, faster development cycles, better coordination across teams, improved time to market. Why not? Lack of capability, inadequate training, budget (Same as the benefits that org’s can expect from DevOps!)
• Agile Adoption Up, barriers to scaling efforts though: 67% of large enterprises (>5,000 employees) have high agile adoption intentions. Agile at scale adoption has increased from 10% in 2020 to 49% in 2021. Biggest barriers to agile at scale adoption: other priorities, current method working fine, unclear ROI. Why do org’s want to adopt agile at scale? Better team coordination, align strategy with delivery, increased visibility.

Keeping stakeholders in the loop is one of the key responsibilities of a product owner. A ton of work goes on behind the scenes before stakeholders can be presented with information about a product's deliverables and timeline. If sprints are your framework for getting work done and projecting delivery dates, the agile development team needs a way to make sure it's working through the product backlog at the right pace. The sprint burndown chart can show you the way.

In this post, we’ll talk about how to use a sprint burndown chart to monitor if your team is on track to complete its work and how putting user stories into sprints and epics generates even greater insights via user story maps.

What is a sprint burndown chart?

Image credit: Atlassian

First, a review: A sprint is a fixed period of time — typically between two and four weeks — that an agile software development team uses to complete a defined set of work.

A sprint burndown chart is a visual comparison of how much work has been completed during a sprint and the total amount of work remaining. It helps measure a Scrum team's progress, and it provides an easy view of whether the team needs to make any adjustments to complete its work for the current sprint iteration.

A burndown chart is a graph with a y-axis and x-axis 📉. The vertical axis measures the total amount of work that the team estimates it will complete during its current sprint. The horizontal axis shows the number of days remaining until the end of the sprint. On the chart are two lines: the actual work line (a line that represents the team's progress) and the ideal work line (a straight line from the top of the y-axis to the end of the x-axis).

You want your actual work line to follow your ideal work line as closely as possible. This would mean that work is being completed incrementally and at such a rate that it can be completed by the end of the sprint. Sprint goal achieved. 👍

A good practice for a team's product owner is to review the burndown chart on a daily basis. Doing so will allow you to detect if there are any progress issues happening in the sprint. For example, if your actual work line is trending above the ideal work line, then too much work remains to be completed by the end of the sprint at the current pace. We'll break down a few reasons why this may be happening later in the post. 😉

The sprint burndown chart is also a great tool to use during a sprint retrospective. Looking at this as a team can help generate talking points to discuss around the sprint retrospective's three key questions: What went well in the sprint? What didn't go as well as we hoped? How can we get better in the next sprint?

A primer on estimation methods

To measure effort on the vertical axis, we need to choose a metric.

Historically, traditional software teams used time to estimate the effort needed to complete a task or a project. For example, "I think it will take me three days to finish that user story." However, this approach can be risky because people tend to underestimate the amount of time it will take to finish a project.

The unit of measure on your sprint burndown chart's y-axis will depend on your estimation metric of choice. Let's review two common ones employed by agile sprint teams.

Ideal days

An ideal day is an estimate by a software developer of how many uninterrupted days it will take to complete a task. Assuming an ideal workday is eight hours of interruption-free work, the estimate could be stated as, "That user story will take me two ideal days." A benefit of this approach is that it accounts for work disruptions; however, it can be problematic because it often positions estimates as best-case scenarios.

Story points

Agile teams use story points as a relative estimate of effort as opposed to a time-based approach. Instead of saying, "I think this task will take me two days to finish," you would state, "I think this task is worth two story points." In this estimation technique, two story points are twice the effort than one story point.

Teams can use ideal days as a baseline to calibrate their story point estimates. For example, one ideal day can be equivalent to one story point, two ideal days to two story points, and so on.

A main benefit of using story points to estimate is that it allows teams to focus on relative measures of effort instead of thinking about how long it will take to finish a task.

Why your sprint burndown might be off track

A perfect actual burndown line is like Bigfoot — if it's been witnessed, it's probably a hoax. 😂

No team can perfectly estimate its work and develop at the exact pace represented by the ideal line. That said, if you notice large differences between your actual line and the ideal line (i.e., your actual line is much higher or lower than the ideal line), a number of things might be occurring:

• The team over- or under-committed to the amount of work at sprint planning
• Story points were added to or removed from the sprint after it started (scope creep)
• The estimated effort for some user stories is off

As a product owner, when you notice something that's off about your line after your daily review of your chart, you should mention that to your team members. The daily stand up is a perfect time to do so.

User stories and epics provide the big picture

User stories describe how a functional part of a product will work from a user's perspective. The common format of a user story reads, “As a [user role], I want to [user activity] so that I can [user goal].” For example, one might read, “As a new customer, I want to sign up for this product so that I can create my profile.”

User stories are placed in sprints to show what work (from the user's perspective) will be finished and by when. They can also be placed in epics to group them into themes within a product. Epics are widely used by agile teams to represent the high-level activity users will accomplish while using a product.

In our example above, an epic can capture all of the user stories that center around user signup, such as signing up, adding payment information, creating a user profile, and configuring notification settings.

If the sprint burndown indicates that the team is off track for a given sprint, then a combined view of sprints and epics can help you determine what impact that might have in the big picture. And, as we’ll see next, an interactive user story map can fix the problem.

User story maps: A view of epics and sprints

A sprint burndown chart is one of the handiest tools an agile software development team can use to make sure they're working and delivering at a solid pace. The burndown chart shows if any adjustments need to be made to your sprint.

User story maps provide another level of insights into team progress by:

• Showing sprints as vertical swimlanes
• Displaying epics as columns that represent the user journey through the product

This combination of swimlanes and columns unflattens your sprint backlog. It visualizes what the team will deliver and by when.

With Easy Agile User Story Maps for Jira, you can supercharge your ability to make adjustments to your sprint. It can help you:

• Create new user stories
• Edit story points on a user story
• Assign items in the backlog to an epic and a sprint

With this tool, teams can view their sprint statistics at a glance and take action. They can ensure they don't overcommit and that they're on track to achieving their sprint goals. It’s the most comprehensive user story map solution in the Jira marketplace for taking action to adjust your sprints from a big-picture viewpoint.

The sprint goal is a key aspect of any sprint, and it should be front and center throughout your two-week process. The goal ensures the team is aligned on a clear purpose for the sprint, and, if done well, the goal inspires the team to stay on track throughout the entirety of the sprint.

So, what makes a good sprint goal, and how does the sprint goal fit within the framework of a sprint? In this post, we’re going to race (or should we say sprint 😉 ) through a recap of the Scrum process, followed by a list of five critical elements of an effective sprint goal. You’ll learn how to best create, manage, and follow through on your sprint goals for a successful sprint every two weeks.

An overview of the Scrum process

We’re big fans of Scrum! Need a little refresher? Here’s how the Scrum process works and where the sprint goal fits into the whole picture.

Scrum is an agile framework used primarily by software development teams that provides team members with a streamlined workflow to meet stakeholder and customer needs. The Scrum workflow has four meetings (also known as ceremonies), which all have a distinct purpose. This structure means team members can easily support each other by sharing, tracking, and enhancing deliverables.

The Scrum framework divides work into repeating two-week sprints where a set amount of work — the sprint goal — is completed. Each Scrum begins with a sprint planning meeting, and during this time, the product owner defines the sprint goal. They choose which tasks will move from the product backlog to the sprint backlog to be completed over the following two-week sprint.

Product backlog items represent the whole picture of what needs to be accomplished before completing or releasing a product. Sprint backlog items are what the team will (hopefully) accomplish over the course of the sprint.

The Scrum Master acts as a Scrum guide who leads the team through the meetings and steps of the Scrum process. Throughout the sprint, the Scrum team meets for a daily Scrum to check in with one another and report on what work was completed over the previous 24 hours.

At the end of the sprint, a sprint review and sprint retrospective help the team gather feedback from stakeholders and improve upon their processes before the next sprint begins. The entire process repeats again with sprint planning and continues to repeat until the product or project is complete.

Easy Sprint Planning:

Drag items directly from your backlog onto your TeamRhythm User Story Map. Inline edit story summaries and story point estimates. Display your sprint goal on each sprint swimlane.

TRY: TEAMRHYTHM SANDBOX DEMO

What makes a good sprint goal?

The sprint goal keeps the team focused and aligned on what everyone is trying to accomplish for each sprint. It’s an extension of the overall product or project goals, but the sprint goal can zero in on key components the team wants to tackle for that specific sprint.

What makes a good sprint goal? Let’s find out.

1. The goal is achievable

The objective of the sprint needs to be achievable within the sprint’s allotted time frame. Generally, in a Scrum framework, the team is time-bound to two weeks.

As new information is gained and other impediments occur, there’s always a chance the sprint goal won’t be met. But that shouldn’t stop you from setting achievable goals. When a team continually fails to meet the goals of the sprint and the project, morale and enthusiasm will decline.

It’s crucial that sprint goals are manageable within the allotted time of the sprint. Sprint goals can become too large when a team tries to accomplish too many different components at once or if too much of the product backlog makes it into the sprint backlog. Rather, take a reasonably achievable workload out of the product backlog to form the sprint backlog. Otherwise, you’ll end up with one daunting overall list and no clear direction for each sprint.

2. The team understands the definition of done

The clearer the sprint goal, the better. You need to clearly define the goals of the sprint and what it means to be done. How will the team know if they achieved the desired outcomes? What does “done” look like? Does everyone agree on this definition for every given task and the overall goals of the sprint?

Your goals need to be measurable to limit ambiguity, subjectivity, or conflicting opinions around the success of the sprint.

When a team is aligned, and everyone understands what needs to be accomplished, decision-making improves, and each aspect of the Scrum team can work harmoniously toward the same aims.

3. The sprint goal is meaningful to the team

Beyond knowing what the team hopes to accomplish over the course of each sprint, the team needs to understand the reasoning behind the sprint goal.

Make sure everyone understands why they are working towards a specific sprint goal. What meaning does the sprint goal have? Ideally, the meaning of the sprint goal will relate back to stakeholder needs, the customer journey, or the user experience of your product.

Visualize and prioritize the work that will deliver the most value to your customers

Easy Agile TeamRhythm

TRY NOW

4. The sprint goal aligns with the overall product goals

The sprint goal can zero in on a specific aspect of product development, but it should still connect to the overall product goals.

While creating sprint goals, ensure the overarching product vision isn’t lost or ignored. Every sprint, while specific to its own set of goals, should work toward accomplishing your product goals.

5. The sprint goal is visible throughout the sprint

The sprint goal can’t be a “set it and forget it” aspect of your sprint. It should be visible to the team the entire time, and the team needs to continually check in on the goal to ensure they’re on track to achieve it.

The shared goal should be front and center of daily Scrum meetings. If possible, display the sprint goal for everyone to see. As you accomplish backlog items and work through the sprint, continually reference the sprint goal and the progress you are making toward it. How likely are you to achieve the sprint goal considering the time you have remaining in the sprint? What might be standing in the way of achieving this goal?

During the sprint retrospective, you should discuss the success or lack of success the team made on the sprint goal. What went well and contributed to your success? What didn’t go so well that you could change or do differently for the next sprint?

With Easy Agile TeamRhythm, each scrum board in Jira will have an associated User Story Map.

Throughout the sprint, the team can refer to the User Story Map to make sure they’re on schedule, coordinate dependencies, and keep sight of the big picture.

TAKE A PRODUCT TOUR

A customer-centric approach

Let’s recap a few of the most important factors to remember when establishing and following through on your sprint goal:

✅ Ensure the goal is achievable.

✅ Ensure the team understands the definition of done.

✅ Ensure the sprint goal is meaningful for the team.

✅ Ensure the sprint goal aligns with the overall product goals.

✅ Ensure the sprint goal is visible throughout the sprint.

Thanks for sticking with us and utilizing the Easy Agile blog. We’re passionate about helping teams work better with agile. We have a suite of Jira apps designed to keep the customer top-of-mind through every step of the development process.

Looking for a tool to streamline your sprint planning sessions? Check out Easy Agile TeamRhythm, which transforms the flat product backlog into a meaningful picture of work.

The retrospective is a critical part of the agile process, providing an outlet for teams to discuss how they can improve. A sprint retrospective comes at the end of each sprint and offers the team an opportunity to assess their processes.

What went well? What didn’t go so well? What does the team need to do to improve next time? Agile is all about learning and iterating. Every time you complete a sprint, there are lessons to be learned. Agile continually takes what a team learns — the good, the bad, and the bland — and turns those experiences into actionable improvements.

This post will dig into sprint retrospectives, including the benefits, how they fit within the Scrum process, how to run an effective sprint retrospective meeting, and common mistakes to avoid.

The purpose of the sprint retrospective

The sprint retrospective is a dedicated time for team discussion. The time is allotted at the end of each sprint so that all team members can examine what went well and what needs to change. It’s all part of the greater agile methodology of continually improving your processes as you learn more. There’s no one set way of doing things, and there’s always room to become more efficient and effective.

A sprint retrospective:

• Encourages a continuous improvement mindset
• Creates a safe space for sharing positive and constructive feedback
• Gives everyone on the team an opportunity to express thoughts, ideas, and experiences
• Provides feedback in real-time after each sprint
• Brings the team together around common goals
• Exposes any issues from the previous sprint that are holding the team back
• Informs leadership of success and potential roadblocks
• Helps product owners make decisions for the next sprint planning
• Sets the team on a positive path for moving into the next sprint

How the sprint retrospective fits within the Scrum process

The type of retrospective you hold depends on the type of sprint or agile methodology your team practices. One of the most common methodologies in software development is the Scrum framework.

A Scrum team has three types of roles:

• Product Owner
• Scrum Master
• Development team

At the beginning of each Scrum, the product owner decides which items from the overall product backlog are moved to the sprint backlog to be completed over the upcoming 2-4 week sprint. The exact sprint timeframe is set in advance.

The Scrum is made up of four distinct ceremonies or events:

• Sprint planning
• Daily Scrum or stand-ups
• Sprint review
• Sprint retrospective

After planning is complete and the team knows which backlog items they are going to tackle for the current sprint, the work begins. The team checks in throughout the sprint via a daily scrum or stand-up meeting. This quick but essential check-in allows the Scrum team to discuss their progress and address any potential roadblocks on a daily basis.

The sprint review meeting takes place at the end of the sprint; it’s an opportunity for Scrum team members to showcase the work accomplished during the sprint. This could be an internal presentation or a more formal demo to stakeholders.

Last comes the incredibly important Scrum retrospective. During this time, the team can discuss what went well and what could be improved so the upcoming sprint can run more efficiently. Anything that’s learned along the way or discovered in the retrospective is brought into the next sprint planning session. This Scrum process repeats until there are no more product backlog items or the product is complete.

How to run an effective sprint retrospective meeting

The retrospective is a critical part of the agile process that should be treated with care and respect. Go in with a plan. Winging it might get you by, but everyone will get more out of the process if the person or people leading the retrospective is prepared.

Use our strategies below to run effective retrospectives that everyone looks forward to.

1. Ensure everyone’s voice is heard

The loudest voices in a sprint retrospective often get the most attention and speaking time, but they don’t necessarily have better insights than anyone else. Each person involved in the sprint process should be given an opportunity to speak.

If you find a few people are dominating the conversation or that some people never contribute, switch up your strategy to include everyone. Go around the room one by one with a question that each person needs to answer, such as “What do you think went well in this sprint?” or “What was your biggest challenge?”

2. Start, stop, continue

The 'Start, Stop, Continue' retrospective format can be expressed in many forms, but the general practice is the same. At the end of a sprint, you decide what you want to start doing, what you want to stop doing, and what you want to continue doing as you move into your next sprint. It’s a simple format that covers both what went well and what didn’t go so well.

Other versions of this exercise include the Rose Bud Thorn exercise, where participants share something positive, a budding opportunity, and a negative to improve upon. There’s also the Anchors and Sails exercise, where participants share what put wind in their sails (went well) and what anchored them down.

3. Establish specific action items

The retrospective is a waste of time if you don’t leave with specific action items. What is your team going to do about the issues brought up in the meeting? Ensure you keep track of the issues and the positive feedback people provide so that you can turn them into actionable tasks or goals before the meeting is complete.

You can’t implement absolutely every change that is brought up, but the discussion should give you a place to start. Work with the team to figure out what changes will provide the most impact. You can use an impact effort matrix or similar agile tools to make informed choices.

4. Retrospective the retrospective

Every now and again, take the time to review your retrospective. Ask for feedback from all team members on how the process could improve. What would make the experience easier on the team? What would they like to see implemented? What hasn’t been working during your recurring retros?

Wow, that’s getting a little meta, but it’s an important step. You need to continually assess your retrospective as well to make sure you’re getting the most out of the experience.

One thing to watch for: When people are bored, they engage less, which means it’s important to switch things up. You don’t want your retrospective process to run stagnant or lose its effectiveness.

5. Review action items at the next sprint retrospective

Make sure the hard work of your retrospective pays off. At the beginning of the next retrospective, take a small bit of time to review your previous action items. What goals and action items did you leave the last retrospective with? Did you accomplish what you set out to do, or do you still need to work at it?

Common retrospective mistakes to avoid

Avoid these common mistakes when running sprint retrospective meetings:

❌ Allowing a few people to dominate the conversation

❌ Not empowering softer voices

❌ Jumping to conclusions without a thorough discussion

❌ Asking the same questions over and over without mixing things up

❌ Forgetting about or not implementing the action items of the previous retrospective

❌ Skipping a retrospective due to lack of time or resources

❌ Forgetting about stakeholder and customer needs

❌ Failing to improve upon your retrospective process

Put your retrospective ideas into action with Easy Agile TeamRhythm

Sprint retrospectives help the entire team learn from each experience and improve. Doing them effectively means evaluating the retrospective itself, empowering voices, and listening to them.

We’re passionate about putting the needs of the customer first and foremost. Easy Agile builds products specifically designed for Jira users to help agile teams work more efficiently and effectively.

Easy Agile TeamRhythm supports the work of your agile team from planning right through to retrospective, encouraging continuous improvement so you're always getting better at what you do, and delivering better for your customers.

TRY EASY AGILE TEAMRHYTHM FOR FREE

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.