Getting Started with Jira
The course is part of this learning path
This course provides an introduction to Jira and covers user stories, user story mapping, epics, acceptance criteria, and MoSCoW prioritization. By the end of the course, you're going to have a good understanding of the features available in Jira and how to use them to manage your workflows.
If you have any feedback relating to this course, feel free to contact us at firstname.lastname@example.org.
- Get a foundational understanding of Jira
- Learn about user stories and the related acceptance criteria, constraints, and business goals
- Learn what epics are and how stories roll up into them
- Understand user story mapping and MoSCow prioritization
This course is intended for anyone who wants to learn more about Jira and how it can be used as a tool to manage your workflows.
To get the most out of this course, you should have a basic understanding of Agile and Jira.
Epics describe a large requirement too big to fit in a sprint, and whereas a user story might be days to weeks, epics might be weeks to months to complete. The bigger, and then normally epics are broken down into stories, and stories are broken down into subtasks. You can see stories have subtasks inside of them.
Let me just quickly show this to you, 'cause I know this was a question that a few of you had earlier on. In Jira, if you remember, view all projects. I got lots of projects in there, and there's my demo Scrum project I created earlier. There's my backlog. In Jira as it is here, you can see that in my backlog, and if you want to look at your backlog, you can just click on the jenga blocks on the left hand side. I can click on my epics. See this epics tab.
If you're using the cloud version of Jira, you'll see a road map icon, and the road map icon is where you can create your epics, and epics will be, they look a bit more like, almost like a gantts chart. If I get there later, I might show you on the cloud version. But if I open my epics, what I can do, I can add epics to my project, and I can give my epic a name.
If I call it payment processing, and I can manage, but let's say this is an e-commerce size or something. I won't do a summary. I'll just create it very simple. You can see that we've got, I'm creating two epics, and if I click on an epic, just here. You see the epics on the left hand side, and as I just clicked on this epics tab, I can use with it on the right hand side, I can very quickly create an issue within this epic just by clicking on create issue, and I can create a user story really quickly. Those are now two user stories that are part of my payment processing epic, and there's my items management.
Let's have our user story in here. Choose products, select product or something like that. View products. Those are all of my epics at the moment, and you can see that "pay with credit card, "pay with paypal" is part of payment processing, and view products is part of item management. If I click on payment processing, I can see what's part of the payment processing epic. An epic contains user stories, and then if I click on "pay with credit card," I can then go to, well I can either, I can click on the three-dotted button. More actions.
Do you know what? I won't do it from there. I'll do it from here. There's a little kind of tick box on the bar, on the tool bar on the right hand side. Click on that. I've clicked on "pay with credit card." I've clicked on the little kind of tick box, and that's where I can break my issue or my user story down into subtasks.
Subtasks are the pieces of work the developer will actually do. These subtasks, you can see them just at the bottom here. Create a microservice, design a webpage, whatever the actual tasks are that the developers are gonna do, they will be in the subtasks. An epic contains user stories. The user story is broken down into subtasks. The subtasks are the things that as developers, we would actually work on, and that would be the hierarchy that Jira supports.
Remember we talked about sprint planning. Well, part of sprint planning might be to identify, first of all, what we're gonna do. That would identify which of these items in our backlog are gonna go into our sprint. What can we deliver? Hopefully, we've already estimated, or we might have to do a bit of estimating, but then we would say, how are we gonna deliver it? And that's where we might break these user stories down into subtasks. You may have already done some of that. You may not have done, but that's part of your sprint planning, which is just before you do your sprints. That would be your process, and then what I would do, is I would say, register with Paypal.
Let's say that's another thing that we need to do, but if I create sprints, just there, that's when we could choose what we were gonna do next. I would drag the issues in the backlog that we're gonna deliver into my sprint, and so, that would be the general process, and like I say, we will come back to it. Epics, stories and subtasks, and that would be our hierarchy, and of course, projects, our project contains these issues, these epics and stories.
I just showed you linking, all of those things together. I didn't show you how you can do this manually. If you click on the three-dotted button on an issue, just click edit, and you can also create a link to an epic from within the issue itself. If you click on an issue in your backlog, if you then go to the three-dotted button, which is the detail for your issue, and then just click edit, you can also link your issue to an epic from this dropdown here. It's slightly easier just to do drag and drop. You can drag. You can just literally drag issues into the right epic box by doing that. There's always more than one way to do almost everything in Jira.
QA is the UK's biggest training provider of virtual and online classes in technology, project management and leadership.