At Easy Agile, we’re constantly looking for new ways to improve our products, and one of the ways we foster innovation is through Dash Days—a focused period where our team steps away from daily tasks to experiment, explore, and reimagine how our tools can better serve customers.

During our most recent Dash Days, we took a fresh look at the user interface of two of our flagship products, Easy Agile TeamRhythym and Easy Agile Programs. The goal was to enhance interaction and discoverability, so users can experience the full value of our tools without unnecessary complexity.

Here’s a glimpse into our thought process, challenges, and the exciting solutions we explored.

The challenge

As Easy Agile TeamRhythym and Easy Agile Programs have evolved, we’ve introduced powerful features designed to give users more control and flexibility. However, as new capabilities have been added, the interface has become more elaborate. For us, this presents an opportunity—an opportunity to take a step back, simplify the experience, and help users unlock more of what our products offer.

To address this, we brought people from across the business together to brainstorm how we could improve the experience in both products. Through these sessions, we identified a few core opportunities:

• Discoverability: How do we make it easier for users to find and use the powerful features built into our tools?
• Visibility: What’s the best way to surface the right information and features when users need them? 
• Consistency: How do we create a more uniform experience within and across our products to make navigation intuitive?

Armed with these insights, we then set out to explore solutions tailored to each product’s unique challenges. 

A more personalized experience with Easy Agile Programs

For Programs, we focused on three “how might we” questions to reframe our challenges into opportunities: 

1. How might we create more focus on the actions users are trying to complete?
2. How might we make navigation more intuitive and easy?
3. How might we help users with more context about where they are in the app at any given screen? 

Out of the many solutions we explored, the one that got us the most excited was the idea of an Easy Agile Programs Home Screen—a personalized dashboard designed to guide users based on where they are in their planning cycle. 

This home screen could adapt based on where users are in their journey, offering relevant guidance and actions.

• For new users, the home screen could provide clear onboarding steps and easy access to help, so they can get started quickly and confidently.
• For experienced users, it could offer insights and key actions related to their progress, so they can stay focused on what matters most. Users might even see data summarizing their accomplishments, which makes it easier to share successes with their teams.

Whether someone’s brand new to the product or deep into execution, the home screen could be a great way to guide and coach our users—helping them answer questions like, "What should I be doing next?" or "What extra value am I missing out on?". 

A more focused interface for Easy Agile TeamRhythm

For TeamRhythym, our three key “how might we” questions were:

• How might we provide more focus within the User Story Map during sprint planning?
• How might we improve the discoverability of issues without epics?
• How might we enhance the layout to highlight key features and improve overall usability? 

With these questions in mind, we explored a range of ideas to simplify sprint planning and make it easier for users to prep, plan, and review their work, whether they’re using Scrum or Kanban.

Sprint planning can sometimes feel overwhelming when you have multiple sprints competing for attention. To help users focus, so we explored the idea of introducing a focused view during sprint planning. 

• This would allow users to zoom in on a specific sprint and the backlog alone, while collapsing others. 
• Each issue would have its own row in the detailed view, and users can drag and drop either an entire row or drag individual issues to quickly rank them based on priorities.
• The sprint view will also hide epics that don’t have linked issues in the current sprint, giving users a cleaner view of what’s relevant to their current work.

We also looked at ways to enhance the User Story Map interface to bring the most useful tools and features to the forefront. By improving how key functionality is presented, we’re helping teams quickly access what they need, when they need it, enabling them to stay productive without interruption.

This way, we can create a smoother, more focused experience for teams using TeamRhythm, so they can focus on what’s in front of them without being distracted by everything else.

Your turn. What do you think?

At Easy Agile, we’re always thinking about what comes next. 

These ideas aren’t on our official roadmap just yet, but they’re the kind of innovations we’re excited to explore.

If you think these changes would improve your experience with Easy Agile TeamRhythm and Easy Agile Programs, let us know! Your feedback helps us decide what to prioritize, so we can continue building tools that truly make a difference for your teams.

‍

The 17th State of Agile Report shared that 93% of executives thought that their teams could do the same amount of work in half the time, if their teams collaborated better.

That's quite a statistic. We’ll leave it up to you to decide whether this reflects a lack of efficiency due to poor collaboration, or a disconnect between leadership expectations and the realities faced by development teams.

What we do know is that improving team collaboration has benefits and that improved collaboration is a key benefit of effective agile practices.

So if you think your team could work more effectively, here are six tips for improving team collaboration that we think will make your working life better, and help you deliver for your customers.

1. Agile Teams Are Cross-Functional

Cross-functional teams are the backbone of agile collaboration. It's Agile 101:

The best architectures, requirements, and designs emerge from self-organizing teams.

Manifesto for Agile Software Development

Ideally, your agile team should be able to deliver work independently. The skills and expertise of your team should allow you to handle diverse tasks without creating dependencies on other teams. You can take ownership of the software you're delivering.

The benefit of organizing into cross-functional teams is a greater shared understanding of your project, where you can each see how the pieces fit together. This type of collaboration supports the efficient flow of work and ensures that knowledge and skills are consistently shared.

2. Take an Iterative Approach

Or to put it another way, make it easier to fail fast, so your team can learn why, and correct your course. By breaking down large projects into manageable increments, your team can focus on delivering small, functional parts of working software at regular intervals. This approach goes hand-in-hand with continual feedback from users, ensuring that issues are uncovered quickly and dealt with just as fast. This shared team focus on user feedback, and the shared purpose and collaboration that comes with it, is a key benefit of agile development.

3. Maintain Regular and Transparent Communication

Daily stand-ups, sprint reviews, and planning meetings are all designed to foster regular and clear communication. You and your team should see these meetings as an opportunity to share ideas, discuss progress and blockers, and collaborate. If your daily stand-up is nothing more than a shopping list of tasks, then you're doing it wrong.

If your daily stand-up is nothing more than a shopping list of tasks, then you're doing it wrong.

Someone who has wasted too much time in shopping-list meetings.

Beyond team meetings, clear communication is important anywhere the details of your work are shared. Agile tools like Easy Agile TeamRhythm provide a central platform for prioritizing work and tracking progress. With a central source of truth that everyone can access to understand goals, priorities, and team commitment, collaboration can be more effective, keeping the team aligned and focused.

4. Conduct Team Retrospectives

Hot take: regular retrospectives are the most important agile practice your team can adopt.

Team retrospectives provide a structured opportunity to reflect on your work and discuss how it can be done better next time. This is team-led improvement because you and your team are in the driver's seat. Encouraging honest and open discussions during retrospectives helps build trust among team members and fosters a collaborative mindset. By continuing to work on processes and behaviors, you and your team can improve your performance over time and make your working life better.

5. Use Collaboration Tools

The right tools can make a big difference in team collaboration. The best tools provide a reliable source of truth that the whole team can access, in a place where the whole team will access it. It's a simple concept; a shared understanding of the work is supported by shared and willing access to the same information.

Choose a tool that makes it easy for you and your team to access information and keep it updated. If you're already working in Jira, an integration like Easy Agile TeamRhythm provides a better view of your work in a story map format, with goals, objectives, and team commitment all made clear. Team retrospective boards are attached to each sprint (or spun up as required for Kanban teams) so you have your team-led ideas for improvement tightly connected to the work in Jira.

No matter which tool you choose, make sure it will facilitate better alignment, streamline your workflows, and provide a clear picture of roadblocks and progress. By using collaboration tools effectively, your team stays organized, focused, and connected, no matter where each member is located.

6. Build a Positive Team Culture

It may sound obvious, but a positive team culture is essential for effective collaboration. Creating an environment where team members feel valued, respected, and motivated, encourages the psychological safety they need to share their great ideas, learn from missteps, and collaborate more effectively with their colleagues.

High-performing teams recognize the achievements of others, share constructive feedback, and support practices that lead to a healthy work-life balance. Make it regular, and keep it authentic. A positive culture not only improves team dynamics but also boosts overall productivity and job satisfaction.

Successful Team Collaboration

Effective collaboration can be the difference between your team achieving their goals, or falling short. By embracing agile practices like the regular communication that comes from agile planning meetings, to the learnings that come from taking an interactive approach to development, and creating time for team-led improvement with retrospectives, you can seriously boost your team dynamics.

Easy Agile TeamRhythm Supports Team Collaboration

Easy Agile TeamRhythm is designed to make your agile practices more accessible and effective, helping your team plan, prioritize, and deliver work with better alignment and clarity.

Built around a story map for visualizing work and retrospective boards that encourage team-led improvement, TeamRhythm facilitates sprint and release planning, dependency management, backlog management, user story mapping, and retrospectives.

Tight integration with Jira makes Easy Agile TeamRhythm a reliable source of truth, no matter where you and your team members are located.

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

‍

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

‍

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.

What is a Scrum Master? The Scrum Master guides the daily Scrum in projects or software development to streamline processes as much as possible. This person applies agile methodologies to guide successful project outcomes.

If you want to become a Scrum Master, learn what defines this role. Explore its duties and how the servant leadership style supports carrying out the various responsibilities it involves.

Find out how the Scrum Master's role benefits product or project development. Finally, discover what qualifications you need to become a Scrum Master and what job types you can apply to complete your studies.

What is a Scrum Master’s role?

A Scrum Master's role is dynamic. They must be flexible and adapt to various circumstances, because the Scrum Master serves a vital role in managing projects.

Every product development project needs a different approach. The Scrum Master must adapt their approach to each position and even play the role of an agile coach at times.

Whatever role the Scrum Master takes on, they play a servant leader role (we’ll review what this is later). So, their responsibilities vary when guiding the team's progress.

Some ways that the Scrum Master works with team members and product owners include:

• Sprint planning with team members and product owners to check that everyone understands what needs to be done
• Solving issues such as work estimation, scope creep and over-committing to work volumes
• Holding daily standup meetings to discuss product issues, backlogs, and any other team member concerns
• Acting as a facilitator to limit blockers that hold the team back from completing iterations on time. The Scrum Master also handles any roadblocks by improving workflows
• Having sprint reviews that ensure team collaboration and helpful feedback
• Holding retrospectives to see how team members can improve
• Monitoring the Scrum board to ensure that all cards are current and that Jira and other software works properly
• Hosting individual meetings to get to know and help team members one-on-one
• Handling portfolio planning tools such as analyzing burndown charts. They use burndown charts and other tools as inputs into what the team needs to build and the cadence levels for their work.
• Making sure that the team members use agile guidelines in their projects. These guidelines help team members meet stakeholder needs.

At the end of the day, the Scrum Master champions the Scrum process for successful project outcomes.

Servant leadership

Part of answering the question, “What is a Scrum Master”? involves looking at leadership styles. These styles include bureaucratic, democratic, transactional, and many others. One style that fits well with the role of the Scrum Master is to be a servant leader, an approach that works well with small teams.

Servant leaders:

• Support a team spirit
• Share responsibility
• Share decision-making
• Focus on achievements instead of faults

Servant leaders find solutions which promote workflows and stakeholder satisfaction.

Scrum Master according to Scrum methodology

The Scrum Guide, written by Ken Schwaber, provides an excellent outline of the diverse responsibilities of the Scrum Master. Here are some of this person’s roles:

• Adopting the role of an agile coach to lead organizational transformation using the Scrum methodology
• Planning Scrum applications to help the organization understand how the new iterative workflow process works and adapt to changes
• Guiding leaders, managers, and other stakeholders in understanding the benefits and applications of the Scrum product development methodology
• Helping increase the Scrum team's productivity
• Collaborating with other organizational Scrum Masters within the organization to help team members adopt agile principles
• Promoting positive working relationships between team members, product owners, and other stakeholders
• Guiding sprint planning, daily stand-up meetings, sprint reviews, and product backlog items

Scrum Master challenges

While the Scrum Master supports a streamlined workflow, their job is not always as simple as it sounds. Here are some challenges they may encounter:

1. Change resistance

Scrum Masters’ concepts may be new to employees, so Scrum Masters can encounter resistance. Either way, the Scrum Master must create solutions to dealing with any resistance to change.

2. Lack of understanding

Not everyone will understand or even like agile processes. A good Scrum Master must overcome this and to help teams connect principles with practical implementation to assimilate agile practices.

3. Gaining leadership support

Scrum Masters can only do their work effectively if they have the full support of leadership. Scrum processes can be pretty challenging, which initially disrupts old processes, making transformation difficult.

Managers may be afraid that the Scrum Master will usurp their authority. Departments may not want to adapt their processes, but the Scrum Master must use agile coach techniques to overcome fears and unwillingness to adapt.

Unless the Scrum Master has the full buy-in of leadership, any change initiative will derail before it even starts.

How Scrum Master positions can work

Role rotation. Agile teams rotate the responsibility of this role between members. For example, each team member does admin tasks for each Scrum meeting.

Part-time role. The Scrum Master takes on additional responsibilities.

Full-time role. The Scrum Master takes on a dedicated, full-time role. They must have the experience to do this work and skillfully show the team how to apply agile practices.

Guiding many teams. A Scrum Master guides several development teams. They monitor the work progress for several teams.

Agile coach. This Scrum Master role involves coaching teams or other Scrum Masters.

If the Scrum Master role interests you, you should know that Scrum Master jobs are common, partly due to the popularity of the agile method.

Organizations often look for ways to improve product development. They want Scrum Masters to help guide the process to get products to the market quicker.

You can look on LinkedIn for positions for good Scrum Masters. Their research shows that these positions are in high demand, so you can improve your skills with Scrum Master certifications. Your prospects are diverse as you can work in manufacturing, health, government, education, and many others.

Scrum Masters can get a Certified Scrum Master (CSM) qualification. They can also be a Professional Scrum Master.

How to become a certified Scrum Master

Scrum.org offers various resources, including Scrum certifications and training. So, if you want to follow a career in agile methodologies and lead a Scrum team, you can become a CSM or a PSM. You can also opt to train through the Scrum Alliance, which has been operating since 2001.

Hundreds of thousands of Scrum Masters have attained qualifications through these organizations. Both provide recognizable certifications at various Scrum Master levels, so perhaps it's time to boost your career.

You can achieve a Professional Scrum Master (PSM) certificate from scrum.org. This is available at three different levels, including:

• The PSM I certificate. This certificate shows that students understand Scrum and its applications as per the Scrum Guide.
• The PSM II certificate is proof that you can apply the Scrum principles and practices in a complex real-work situation.
• PSM III certificate. This certificate shows that students have an in-depth understanding of Scrum Values and can apply Scrum principles and practices in complex environments and situations.

Anyone who wants to improve their career opportunities can sign up with Scrum Alliance to get their CSM certification. You can become a:

• Certified ScrumMaster (SCM). This certificate focuses on servant leaders and how to help the Scrum team work together to enact the Scrum framework.
• Certified Scrum Product Owner (CSPO). This certificate is for anyone involved in the business aspect of projects. If you want to know more about product development, productivity, and meeting stakeholder needs, this one is ideal.
• Certified Scrum Developer (CSD). This certificate is good when you want to know how to apply techniques and tools to build great software products. You will learn how to apply iterative Scrum methods in this certification process.
• The Certified Scrum Professional (CSP) learns how to improve Agile methodology implementation in each project they guide.

Take your career up a notch.

Easy Agile provides a range of resources to help Scrum Masters achieve their agile methodology goals. In addition, you can access resources such as our learning hub and webinars to improve your skills.

Scrum Masters can also explore Easy Agile Programs for Jira to enhance the software development team’s experience. Another excellent resource is Easy Agile Scrum Workflow for Jira.

Enhance your Scrum Master role with resources that make your work easier by overcoming resistance to new learning curves.

It's common knowledge in the world of digital marketing and eCommerce that personalization results in higher conversion rates, more engaged users, and a better overall brand experience for your customers. What's less common is personalization strategies based on purchase history, user behavior, and psychographic patterns identified across your customer base — these are known as user segmentation.

That's just a fancy way of saying that segmentation groups your customers by how they act, think, and feel. If you can identify these patterns, you can begin to anticipate your customers' needs and build personalized marketing campaigns and user flows.

Let’s say you added a first name to an email. That’s a beginning, but there’s a lot more to personalization strategies than using proper names. Developing deeper insights through segmentation allows for a hyper-targeted marketing strategy and more engaged users.

We'll dive into the weeds of user segmentation, give you some segmenting ideas, and show you how you can incorporate user segments into your Jira projects to help with your Sprint and release planning.

Product managers use Jira to plan based on user segments

If you're in product management, you're responsible for creating an organized product roadmap that aligns with the business goals for that time period. Visualizing the target audience represented in each sprint helps ensure you stay focused on the right functionality to meet your goals.

Often, user personas and customer journey maps are created before user segmenting gets underway. Rich personas and detailed journey maps not only provide valuable information to user experience teams, marketers, and product teams. They are the foundation for building different user segments.

Apply user segments to each stage of your customers' lifecycle, starting with their first contact with your brand, through purchase, onboarding, product usage, and eventually to churn. When personalized through a customer journey stage, marketing campaigns and product user flows enrich your customers' experience, ultimately increasing your profits and impressing your boss.

Lucky for you, Jira can help you do that. Here are some simple ways you can use Jira to organize work by user groups:

• Use labels and corresponding card colors identifying specific user segments.
• Add a custom field as a lifecycle or market segment(s) identifier.
• Create separate Jira projects based on segments.

Easy Agile User Story Maps and Personas are Jira add-ons. These Jira add-on apps are specifically designed to integrate Personas and Easy Agile User Story Maps into your Jira environment.

These tools allow Product Owners to better visualize and plan Sprints and releases with the appropriate balance of user stories for each customer segment. Create a persona for each segment within Jira and you can filter your Story Map by Persona.

User segmentation is as simple or complex as you make it

If you're at the “first name” stage of personalization, you've taken the first step toward building a personalized brand. But now, let’s get started on some basic user segmentation.

Before we get started, you need to understand two principles behind customer segmentation:

1. There is an infinite number of ways to segment your customer population. You'll need to do a lot of testing to figure out which segments return the best results for you.
2. A single customer can belong to multiple user segments. Nope, this isn't going to be a clean, one-to-one matching of customers and groups. But don't worry — we'll give you some tips on how to keep your segments organized.

Let's start by getting on the same page with what we mean by a segment. A user segment is a collection of users who have something in common. That's it.

Take a look at some typical methods of segmenting a user base:

• Geographic segmentation
  • Country, region, state, city, or neighborhood
• Demographic segmentation
  • Gender, age, race, religion, marital status, or family size
• Behavioral segmentation
  • Past purchases, preferred device (phone, tablet, or desktop), responses to marketing campaigns, or in-app feedback contributions
• Psychographic segmentation
  • Lifestyles, beliefs, value systems, interests, or opinions

As you can tell from this list, customer segmentation requires a significant amount of customer data. You probably have a lot of geographic and behavioral data already in your CRM or analytics tool.

Collecting demographic and psychographic data requires you to get more creative. While some customers readily offer this information, others are not so willing to disclose their personal details. Enticing those users through survey completion discounts, promising a more personalized experience, and analyzing social media interactions are a few ways to get a more complete demographic and psychographic disclosure from your user base.

Advanced user segmentation strategies

Basic segmentation is pretty straightforward. Once you've got that down, you'll want to move on to more advanced segmentation techniques to increase your targeting and results. This is where segmentation gets fun.

With advanced user segments, you begin to combine customer attributes across segments. For example, you may create a segment of users from Brooklyn Heights who own a specific product and typically purchase from their phone.

Let's take that example a step further. Suppose next, you create a segment of users from Brooklyn Heights who bought a specific product in the last 14 days, made their last two purchases from their phone, and have never responded to an email campaign. This segment seems like a prime candidate for an SMS campaign. Without segmentation, how would you know?

Another more advanced segmentation strategy if you have multiple products is combining product ownership, purchase history, and affinity data to create segments predicting the next purchase behavior.

An example of product affinity data would be customers who bought Product A also bought Product B 83% of the time.

Then, have your analytics team figure out the typical time lapse between the purchase of Product A and Product B.

Now, build your segments based on customers that bought Product A but have not yet purchased Product B. Your segments will include users that purchased A in the last 30 days, 31-60 days ago, and more than 60 days ago. (Your data will tell you the real numbers based on purchase history patterns within your customer base.)

These segments are ready for everything from targeted campaigns to customers most likely to purchase Product B. Trust us, your boss is gonna love this stuff!

We hope you're starting to see how to get more specific and include more attributes as your segmentation strategy gets more complex and more targeted. We recommend you start generally gradually add complexity to your user segments.

Because your segments are basically filters through which you view your customers, the more you segment, the smaller your population becomes. Customizing a campaign or user experience flow for a population of 50 when you have 5 million customers just doesn't make sense. Gradually adding complexity will let you know when you've gone too far and your population is too small.

Quick tip: Derived versus explicit data

When it comes to specific data attributes for your user segments, don't forget to think about derived versus implicit data. Derived data is presumed based on other explicit data.

Let us explain. Say you are building a music app and one of your user segments is jazz music fans. If a customer completes a form and tells you she loves jazz music, you explicitly know that she is a jazz music fan.

However, if a customer hasn't given you that information, but her music purchase history includes repeated purchases of songs from jazz musicians, you can derive that she is probably a jazz fan.

Think of derived data as a way to combine explicit data that allows you to make some actionable assumptions.

Release the power of segmentation through Jira

By now, you can probably see that user segmentation creates richer personalization experiences for your customers, which garners higher profits and better retention. And with Jira at the top of Gartner's list of agile planning tools, you might be able to use these tips on creating a user segmentation strategy with Jira.

Remember the steps to maximizing your customer and market segmentation strategies:

1. Create rich personas and detailed customer journey maps.
2. Use personas, journey maps, and internal user data to build meaningful customer segments.
3. Build personal marketing campaigns and user experiences for specific user segments.

In Jira, you can visualize, organize, and plan your product work with your user segments in mind. Combined with a roadmap app, Jira is a great tool that allows you to measure and report on the value delivered by each of your user segments.

At Easy Agile, we live by our name — making agile easy is our mission. Go ahead and check out our Jira apps: Easy Agile Personas, Easy Agile User Story Maps, and a flexible Easy Agile Roadmaps.

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.

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.

Just as you looking at a physical map before a road trip helps you understand the legs of each journey, roadmaps help agile teams understand their workloads for the upcoming months. Jira roadmaps offer further benefits, such as timeline visualization and the ability to share relevant information with external stakeholders.

In this article, we'll unpack the purpose of product roadmaps and whether they’re all the same, as well as why Easy Agile Roadmaps for Jira is the simplest roadmapping tool for Jira. You’ll discover how roadmaps help Product Owners, agile team members, customers, and stakeholders. You'll also understand the difference between roadmaps and Gantt charts.

Let’s start with discussing the purpose of roadmaps for agile teams.

Why does an agile team need a roadmap?

Roadmaps help agile teams define their big chunks of work and when to complete them by. It’s an artifact to communicate with the team, customers, and other project stakeholders.

With roadmaps, agile team members have a sense of their journey for the next 3-6 or even 12 months. By understanding this journey, teams can better understand their product’s evolution.

If you’re a Product Owner, roadmaps are a great way for you to:

• Demonstrate that you understand company goals
• Show the C suite and the agile team that you're aware of customer needs
• Show you know how to deliver a valuable product to your customers while meeting your company's goals

Roadmaps are also a great way to remind you and your team how their work fits into the bigger picture. They give you an opportunity to motivate and help team members.

Also, by breaking down epics into user stories in the product backlog, Product Owners and the development team can better prioritize, schedule, and assign resources to those work items.

Now that we've covered the basics of Jira roadmaps, let's take a look at how to adapt them for different roles.

Tailoring roadmaps to meet specific needs

Different people on the team will need different views of roadmaps. Some roles focus on analyzing specific roadmap items of roadmaps, and other roles focus on different parts.

The development team needs roadmaps with expected release dates, milestones, and a detailed customer value explanation.

You may prioritize roadmap items by customer value, which makes sense when considering the customer-first agile methodology.

Often, development teams have roadmaps organized by sprints and work items arranged on a timeline. A work item can be a user story, a task, or a bug.

The C suite uses roadmaps to map the work of development teams onto company goals and metrics.

Those roadmaps display work items organized by month or quarter. This organization helps track progress over time and draw conclusions on goal achievement.

When roadmapping for the C suite, you don't need to worry about providing them with detailed work item descriptions.

The sales staff relies on roadmaps to learn about new features and customer value. That kind of information can help improve sales conversion. Roadmaps are a great way for the sales staff to understand upcoming developments they can get customers excited about.

You should also do your best to offer visually appealing and highly readable roadmaps to your customers. They'll look for a prioritized overview of new features.

Jira roadmaps might help you deliver these different types of roadmaps.

Jira roadmaps

Atlassian included roadmaps in next-gen Jira software. Jira roadmaps allow you to define and organize items in a timeline and keep them up-to-date. You can even share the work status with stakeholders.

But the coolest thing about roadmaps in Jira is that it syncs with the developers' work.

As the scope of a project can change while agile teams are working, it can get tricky to maintain an up-to-date roadmap, especially if you’ve been using a static tool like Excel or Confluence. Thankfully, Jira roadmaps allow you to quickly and easily update the work status and item priorities.

Agile teams can attach user stories to the Jira project on which they're working. As a result, Jira software updates the actual work in their roadmap.

You can also use Jira software to break down roadmap items, or epics, which means dividing work into small chunks. And as if this wasn't enough fun, you can use Jira Software's drag-and-drop functionality to adjust item priorities in the timeline. Consequently, Jira Software automatically adjusts the dates in the epics.

These are a few more reasons why Jira roadmaps are worth checking out. They offer:

• Stakeholder collaboration in creating and maintaining the roadmap
• The ability to share information with external stakeholders
• Increased availability and visibility to team members
• Tight links between a team's work and the roadmap
• Seamless item update ability
• Project status visualization
• Both high-level and detailed item descriptions
• Connections between Jira issue dates and dates on the roadmap

Easy Agile Roadmaps for Jira can help shape your roadmap as a timeline with swimlanes based on work themes or teams. Drag and drop items on the timeline to set when the team will begin and end working on them. You can also:

• Define milestones
• Filter the roadmap’s view
• Track epic completion progress
• Share a PDF version of the roadmap with stakeholders

Before you go, we should get on the same page about Gantt charts vs. roadmaps.

What are Gantt charts?

When we say “Gantt charts are useful for agile teams,” you might immediately think, “That can’t be right!” 😮 However, Gantt charts can be useful in the right context. They’re just not very agile.

The Gantt chart, named for the chart’s creator, Henry Lawrence Gantt, provides a graphic schedule for planning and visualizing tasks organized by project stages.

Project managers use Gantt charts to manage task dependencies and the critical path. This path is the sequence of tasks that team members must execute on time to not compromise the project’s end date.

Simply put, if you’re building a data center, you have to define the order in which the team must execute tasks. Basically, the team can’t start some tasks before completing others.

Now, let’s clarify why roadmaps are agile, whereas Gantt charts are not.

Why Gantt charts and roadmaps are not interchangeable

At first glance, Gantt charts seem similar to roadmaps. However, at their core, they serve different purposes and audiences.

Gantt charts assume that team members will complete work in a linear fashion. This means that the execution of some tasks depends on the execution of other tasks. And any modification to the schedule can compromise the project’s end date, so you should avoid task rescheduling and frequently track the execution of tasks.

This is why the linearity of Gantt charts goes against the very principles of agile. 🛑

The agile methodology originated from the need to address the inefficiencies of traditional project management practices in software development. One of those methodologies is the waterfall methodology.

Agile teams do adaptive planning and deliver outcomes on an ongoing basis. They also focus on continuous improvement. That’s why no Gantt chart would fit into an agile workflow.

Gantt charts follow a linear delivery model with lots of task dependencies, which tends to be slow. 🐌

On the other hand, the agile workflow has shorter development cycles — iterations — with frequent deliveries and the bare minimum task dependencies. That speeds up continuous improvement. Additionally, agile teams adapt their roadmaps very well to ever-changing priorities and requirements.

Roadmaps are good, but Jira roadmaps are awesome

Jira roadmaps like Easy Agile Roadmaps help order work items by priority and update their statuses. Stakeholders can make collaborative edits on roadmaps in Jira, which is very convenient.

Perhaps the greatest feature of Jira roadmaps is that developers can both track work in Jira Software user stories and through the tasks on those roadmaps. From the Product Owner's perspective, the benefit is how they visualize the developers' work and communicate it with stakeholders.

It’s really important to make sure that both the C suite and the agile team buy into the roadmap. If they don’t, you might not be aligning your team’s work with company goals and customer needs.

Keep in mind that roadmaps’ benefits work two ways: Team members better realize how they contribute to achieving company goals, and you can monitor that process.

Try our Easy Agile Roadmaps for Jira. Whether you’re following the Scrum framework or the Kanban framework, it’ll help you organize your team’s work items in a timeline, define milestones, and track progress.

Sprints are at the core of agile principles. And they’re how a Scrum team uses a predefined time period to work together towards an agreed-upon goal. A sprint focuses on interaction and collaboration to produce working software. A team has to do a lot of work to maintain their sprint workflows in Jira. Changing task statuses, notifying teammates to sprint changes, and keeping developers’ code changes in sync with Jira tasks can all add up to a lot of manual mouse clicks. 🖱

Many of these manual steps can be automated to save your team effort.

Help your Scrum team with Jira automations

Scrum is a framework for getting agile work done. The Scrum events are:

• Sprint: The time period in which the team works toward their sprint goal (e.g., completing a set amount of user stories from the product backlog). The next sprint starts when the previous one ends.
• Sprint Planning Meeting: A meeting that scopes the amount of effort required for backlog items prioritized by the product owner. The software development team commits to completing that amount of work.
• Daily Scrum: A brief meeting each workday when Scrum team members update each other on the progress of their work within the sprint. It's a time to lend support or unblock another team member who may be stuck on an issue.
• ​Sprint Review: A time for the Scrum team and stakeholders to review the outcomes of the completed sprint and discuss what impacts they have on future sprints.
• Sprint Retrospective: A meeting to find opportunities to improve on the team's agile processes and its interactions with each other.

Which Scrum roles are involved:

• Software Developers: They get the work done but don't want any sprint surprises.
• Product Owner: This person prioritizes the work and sometimes has to make unplanned mid-sprint changes.

Every player on the software development team, from startups to established companies, has repetitive tasks they need to perform throughout its sprint events. Because we're all human, when we're sprinting, we sometimes forget to transition the status of issues or do the little things in Jira that keep everyone on the team aware of what's happening in our sprint in real-time.

Automate your sprint workflows with Jira

Have no fear. Jira can help automate typical sprint workflows like task transitions and team notifications. 🤯 Agile project management within software development is a methodology that is conducive to automation. You can link behaviors in your Jira issues to trigger actions from tools like Slack and MS Teams, email, GitHub, Bitbucket, and GitLab.

You can use Jira automations to do things such as:

• Notify team members and stakeholders of any changes to a sprint
• Trigger actions based on task transitions within a sprint iteration
• Keep Jira task and sub-task statuses and story points in sync
• Connect code commits and build statues to Jira issues

Oh my!

If you didn't know these tools existed, here's your chance to learn them.

Automate your way to connectivity

Keep agile teammates in the know

When a sprint begins, it's important the product owner notifies team members if something changes. That way, you can make sure it won't negatively impact your ability to complete your sprint goal.

Communication within agile teams is paramount, and Jira provides ways to automatically notify your scrum team based on rules you set about your sprint. For example, you can send emails or Slack notifications when the status of a task changes.

Task and sub-task coordination

Sub-tasks are a handy feature in Jira. They help you break tasks into smaller steps and track their progress as they're being worked on. Scrum masters encourage this universally in agile, but it can be easy for sub-tasks to get out of sync with their parent tasks. We’ll soon learn a Jira automation to prevent this.

Connect developer code work to Jira issues

Your development team has a lot on its plate during a sprint. Not only does it have to complete all of its user stories — but there's also the mechanics of keeping code commits by developers synced with their associated Jira tickets. And, always remembering to keep these in tune with Jira tickets is burdensome. As you’ll see, there are ways to connect actions taken in GitHub, Bitbucket, and GitLab and update Jira tickets.

Jira automations FTW

Here are our nine favorite Jira automations that streamline our sprint workflow.

1. Notify teammates when a story is added to a sprint

Scope creep (adding new points to a sprint after it starts) is nobody's friend. However, there are times when a product owner needs to pull an item from the product backlog and add it to the current sprint. When this happens, it's best practice to inform the whole team that a change has been made. Use this handy automation template to send an email to your team when backlog items are added to a sprint.

2. Automatically assign a task when its status changes

Some team members need to be made aware when an issue transitions to being on their plate. When an issue’s status switches to In Review, for example, you can auto-assign it to a QA teammate.

3. Celebrate when your sprint is over by sending a Slack message

A lot of work happens during a sprint. Because your next sprint always begins immediately when the current one ends, it's often difficult to find time to celebrate wins. Use this celebration to send a fun Slack message to your team when the final issue in the sprint is completed. You can make sprints fun with automation!

4. Automatically put In Progress issues into the current sprint

There are lots of moving parts when trying to ensure that In Progress Jira issues are visible in the current sprint. Nobody wants hidden work. When a developer moves a task into In Progress, you can automatically assign it to the current sprint.

5. Sum the story points of sub-tasks and update the value of the parent task

Be sure that your story point totals are accurate by automatically summing the points of your sub-tasks and updating the parent task with the value. They'll never be out of sync with each other with this nifty automation rule.

6. Close an issue when all of its sub-tasks are complete

Some people like to work with sub-tasks, which is great. But it's easy to overlook closing a parent task after you've finished your work and closed all of its sub-tasks. Well … you can automatically close a parent task when all of its sub-tasks are complete so this doesn't happen. 🤖

7. Move a task to In Progress when a commit is made

Save your developers time by cutting down on redundant tasks. When a code commit is made, it means a task is being worked on. Connect Jira to your commit repository (GitHub, Bitbucket, or GitLab) so that when a code commit is made, the associated Jira issue moves to In Progress.

8. Add a comment to a ticket when a pull request is made

Adding details to a Jira ticket from a pull request can be a copy-and-paste job — but it doesn't have to be. Use a trigger to add the details from the request into a Jira comment.

9. Notify the development team when a Jenkins build fails

Certain issues can't wait to be realized by the whole team on the next daily stand-up. If your Jenkins build fails, this is an awesome way to let the whole team know by Slack, MS Teams, or email ... right away.

Make agile sprints easy

Automations in Jira make a sprint team’s life easier by cutting down on the manual work needed to keep the mechanics of a sprint running.

You can use modified versions of these automations with Easy Agile to make agile even easier! For example, celebrate roadmap wins by notifying your team when issues are completed in your Easy Agile Roadmaps for Jira, or sync your Jira data fields with your roadmap. There are many ways to mix-and-match rules and triggers to make Jira automations work for you.

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.

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

Watch John’s lightning talk now:

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

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