![]() ![]() These allow you to connect issues with keywords across Projects. If you’re interested in using Epics simply to group tasks, then you might consider Labels. Versions are also comparable, but they are not intended for long-term use. Both sit below the level of Epics on the hierarchy, though, and can hence be used to break up Epics to provide increased transparency and traceability. What’s more, while some Projects will run forever (for example, when being used to manage ongoing processes or maintenance tasks), Epics should have a defined purpose and should eventually be closed – otherwise, they’ll become bulky and unwieldy.Ĭomponents and Features are similar high-level issue types that can act as containers for multiple tasks. You might be wondering if Epics are quite so epic, what makes them different from Projects ? The key thing is that Epics should break up Projects – if all your tasks fit into a single umbrella Epic within the Project, then it’s unlikely to be providing any benefit to you or your team. This means the tasks can be looked at in context and can assist with ordering the backlog and prioritizing work – simply using the Epic as a container for tasks. That said, while Epics were made with Agile in mind, that doesn’t present any limitation on teams using other processes – and Epics remains a highly effective tool for planning and tracking tasks.Īn alternate use for Epics is to connect multiple related user stories or issues together. Splitting projects into multiple streams makes progress easier to track and adds clarity when explaining the different building blocks contributing to the project to individuals inside and outside the team.Īll of this makes project management simpler and more efficient and gives the team greater agility.įrom an Agile perspective, an Epic would represent a single goal or piece of deliverable work contributing towards a theme and would be made up of the independent tasks or user stories needed to reach that target. These then run in parallel with one another and can work in concert towards the ultimate objective of the project. With Epics, you can break the project down into one or more blocks of work. This might cover work that will be completed over a longer period of time or over multiple sprints, for example – and with a scope that’s entirely up to you. They incorporate multiple specified pieces of work and allow you to bundle a group of issues together. What are Jira Epics and what are Jira Epics used for?Įpics sit at the top of the list of Jira’s hierarchy of tasks. What are Jira Epics and what are Jira Epics used for?.In this guide, we’ll break down what Epics are, what they’re for (and what they’re not for) and how you can go about creating and using them. And generally speaking, Epics are intended for jobs that, as the name would suggest, aren’t going to be done in a day but are going to be…. Jira is all about getting work done, and Epics are a valuable way of contributing toward that goal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |