1. Home
  2. Training Library
  3. Business Management
  4. Courses
  5. Jira Essentials for Agile Teams

User Story Mapping and MoSCoW Prioritization

Developed with

The course is part of these learning paths

Applying AGILE Techniques to Build a DevOps Practice
DevOps Playbook - Moving to a DevOps Culture
Start course
Duration4h 1m


This course is designed for users who are already able to create, update and search for issues in Jira but now want to understand how to use Jira to control, manage, and maximize the effectiveness of their agile projects. We will look at using Jira in Scrum and Kanban projects and how Jira can be a powerful aid in the pursuit of empirical process control.

If you have any feedback relating to this course, feel free to contact us at support@cloudacademy.com.

Learning Objectives

  • Review Agile, Scrum, and Kanban practices and how Jira can be used in conjunction with them
  • Understand how Jira can be used to capture Epics, Stories, Tasks, and Acceptance Criteria
  • Understand how to use Jira to manage Scrum and Kanban projects
  • Learn how to use the Jira dashboard and tools

Intended Audience

Anyone looking to improve the way they use Jira to manage their workflows and projects, through the use of agile practices. 


To get those most out of this course, you should have a basic understanding of agile and Jira.


Just the recap, just a few things on Jira. Remember in Jira, we create a project. So we've got a QA Cinemas project and a project could be of type Scrum or Kanban. So we create projects of a certain type. And then within a project, we add Issues. What you've been adding to your project have been User Stories because Issues can be of a certain type. And so Issues are associated with Issue Types in Jira and you can have issue types, like User Story. And what was some of the other ones? User story. And tasks. Tasks. Yeah.

There are tasks to do items which are sort of similar to the tasks as well apex. And then you can also create your own Issue Types of this list Here is a list that you can change. So that's for you to change as well as Issues. Issues can also have sub tasks. It's almost like a self reference that, to be honest. so that sort of hierarchy we have been creating.

So we've been creating user stories and then we break our user stories down into sub tasks but we've also got issues that can be epics and epics themselves can contain, could can be associated with a user stories. So there's a relationship there as well. It's a slightly kind of odd relationship. but in Jira, there is a special relationship between Epic and user story And Jira specifically deals with that. There's another one that we haven't talked about yet called component. And a component is also a list that you can configure yourself and it's a way of grouping issues together.

So you, you define what this is a list of. So we could say tickets, we could say payment. And anything at all it could be. And you might use this as a way of classifying your issue in terms of where the issue occurred. So if we had a bug and we wanted to say where the bug occurred we could say it's a bug and the bug caught in the ticket system or the payment system or the home screen.

So the bug occurred in the ticketing, the bug occurred in payments, but bug occurred on the home screen and you get to choose what that list is a list of. So we often use components as a way of classifying issues. Sometimes people just use this as a list of teams as a way of separating issues across teams. So it's entirely up to you how you use it.

What a lot of teams do is as well as capturing user stories, they often look at the journey that's involved with one or more user stories because they often combine together to achieve an overall behavior. And so they might Group Stories into an application theme or functionality. So it's where we look at the User Story of a Journey or what we call User Story Mapping.

The User Story Mapping is quite a confident technique. If you look at the whats on the screen now, we're looking at defining a User Journey. And in the case of say an e-Commerce site. We've got a number of different columns, which would be for the process that the user might go through in the User Journey. So a user you might start the Product page where you choose your product and then you might go to the Product page once you've chosen your product. And then from the Product page, you might then go to the Checkout. So that would be our User Journey.

What we might then do is organize the the stories by the pages. So a User Story might be, as a customer. I want to be able to filter my product by product, by category. So there it is. So that might be one of my stories but there's other ones. I want to be able to filter by color, by style. So I want to sort by rating. As a customer I want to be able to see a description. So these are all the user stories but what's going on here? Release one, Release two. (mumbles) Why isn't it all here? What have we done with this journey? Well, what's this showing us? Splits out into different releases with some sets of functionality we can add up over time. Yeah. That's exactly it. Isn't it that?.

So what we've done is we said we know we need to do all this stuff. We know we want a media gallery and we wanna do postcode look up. We wanna pay with credit card and it'd be great if we could filter by style. I can't wait until we've got a quick preview and we can sort by rating and we've got reviews. Yeah we want a lap bar. How can we get to market as soon as possible? What do we need to get to market? How can we get released as soon as possible? What do we, what's the minimum we need?

Well, for release one, we need to filter by category. We need obviously to display a description. We need to show them the purchase options. We need a Buy Now button. We need them to add delivery info and let's just get into pay with PayPal. That's the quickest, easiest thing. Just put a button on that pay with PayPal done, job done, Release one done. So those are the things that need to go into Release one.

So we define the journey that gets us to a payment and that's the minimum number of User Stories that will make it up. That's release one. What's release two okay? let's refine that. So it's one of those picture paints a thousand words, Isn't it? It's great. User Story Mapping is a brilliant tool to use. I don't know whether you already do it.

Did you already do something like this? Yeah. Not as often do similar kinds of things in different ways, but it is something that if you have done before or you do now Yeah often do you phase releases. Phase Releases? Yeah, same kind of thing but certainly having this up and clear to everybody. This is what we're doing. This is the plan. It is nice and clear.

There are add-ons that you can add into Jira that will help you do User Story Mapping actually with your User Stories in Jira directly. Jira doesn't add the box, come with this functionality. But, but yeah, it's another really nice technique. But it's great. We just post it you know. I mean, just, just do it post it notes. And it's brilliant.

MoSCoW prioritization. Jira has a basic set of priorities where you have highest, high, low and those sorts of priorities. But again, in Jira, you can tailor your priority list. So if you want to give issues of priority 'cause you notice it's one of those fields in Jira. you can change your prioritization to be different values. So you could use something like MoSCoW prioritization where you can say things are a must have, should have, could have real ones have. While you are educating same kind of ideal as what we saw earlier on.

About the Author
Learning paths24

QA is the UK's biggest training provider of virtual and online classes in technology, project management and leadership.