Skip to main content
10 votes
Accepted

How can I create an Epic based on requirements following best practices?

There are two schools of thought about what an Epic is. Some define an Epic as a large user story, often one that cannot be delivered in a single iteration. However, it can be placed and ordered in a ...
Thomas Owens's user avatar
  • 19.6k
7 votes
Accepted

Agile: Can Epics be time-based rather than feature-based?

There is some grey area here, but let's start with a clear answer to work from. Epics are a derived idea from User Stories - specifically an epic is just a big user story that you've broken down into ...
Daniel's user avatar
  • 16.9k
7 votes

How should large non-reducable tasks be handled in Scrum?

I'm not convinced that what you describe fits the notion of "large, non-reducible tasks". So far, I'm also not convinced that any piece of work is large or can't be reduced to something that ...
Thomas Owens's user avatar
  • 19.6k
6 votes
Accepted

How to get an Epic span multiple sprints?

You can assign the Epic's user stories to different sprints according to your needs. And when you browse the Epic you can see how its issues are distributed. Like the below example.
Yassmeen's user avatar
  • 817
6 votes

What is the weighting difference between Epic/Story/Task

Epics – Large projects that entail many people over a long time. Stories – Smaller projects within an Epic that must be completed before the Epic can be considered ‘Done’. Tasks – The day-to-day ...
Uğur KANTEKİN's user avatar
6 votes
Accepted

Production bugs and epics in Jira

Outside of the Jira context, an Epic represents some kind of deliverable business value. An Epic is usually made up of good Stories, the full value is realized to the client and users after all of the ...
Thomas Owens's user avatar
  • 19.6k
5 votes

How to implement Epics on Gitlab without Enterprise Edition?

An epic can be considered a group of issues. Create an issue with your epic name, then create subtasks to this issue. Go to the main issue to see the list of issues and whether they are finished or ...
Nicolas B.'s user avatar
5 votes
Accepted

How to eliminate wasted time / improve cadence on epic boundaries

I worked with an organisation that had a similar problem (although we were using Scrum rather than Kanban). What we found was that the work became very bitty towards the end of an epic and it was ...
Barnaby Golden's user avatar
5 votes

Is this a trick assignment with Release Planning ? Any comments is much appreciated

This scenario feels Waterfall because of the fixed scope of 8 epics and fixed schedule of 10/21/2021 so I wouldn’t say your feeling is off on that point. However, this is very much reality in many ...
James Tention's user avatar
5 votes

Is this a trick assignment with Release Planning ? Any comments is much appreciated

This is a weird test. You have a fixed time, fixed goal and fixed resources. Nothing there is flexible. There is no decisions to be made here. You are not a project manager, you are a project ...
nvoigt's user avatar
  • 8,525
4 votes
Accepted

How can I force an epic to have a limited/finite scope?

TL;DR Whenever possible, think of epics as placeholders for more detailed product backlog items, not as evergreen stories. It's better to add new stories to the Product Backlog as they are discovered ...
Todd A. Jacobs's user avatar
  • 50.5k
4 votes
Accepted

Example epics for an mobile game

Since you've marked your question as Scrum, my advice to you is to have your Product Owner talk to the stakeholders. Both the ones sponsoring the project (in your case, the teacher), and the ones who (...
Sarov's user avatar
  • 14.8k
4 votes
Accepted

Epics vs Projects vs something else

If you want multiple 'projects' to be on the same Scrum-board Sprint, then you can accomplish that by having a board with the JQL filter set to read from multiple JIRA projects (ie. 'project = ...
Sarov's user avatar
  • 14.8k
4 votes
Accepted

How do you associate a bug identified after customer acceptance with the relevant epic?

This kind of traceability can become difficult and problematic as one backlog item or even epics modify the behavior of a previous one, but if you do want to link them, you can still use JIRA's "...
Daniel's user avatar
  • 16.9k
4 votes
Accepted

Epics disappear from Scrum board

In Jira, Epics are containers for smaller units of work, which are often represented by other issue types like Story, Bug, and Task. Epics won't appear in the Backlog view in Jira, however they will ...
Thomas Owens's user avatar
  • 19.6k
4 votes

How can I create an Epic based on requirements following best practices?

I just wanted to add a little to Thomas's excellent answer. Epics are a solution to a problem. The problem is typically: "Our backlog is a bit cluttered and some stories are quite big". You don't ...
Barnaby Golden's user avatar
3 votes

How to implement Epics on Gitlab without Enterprise Edition?

Unfortunately, Epics were introduced in GitLab Ultimate 10.2 and are not a part of the free tier. That said, our team has used the label feature in free rather effectively, much as you've described ...
dom_michalec's user avatar
3 votes

Jira Project vs Epics vs Categories

So I see a mashup of terms from traditional and Agile worlds. The answer below assumes you are using Scrum. Product = Project For your project, create a project in JIRA. Everything related to your ...
Muhammad's user avatar
  • 854
3 votes

User story for a requirement which generates files and sends to external system

There are two questions here: how can we represent this in a user story and how do I break it up? Because nothing in agile or scrum forces us to use user stories (unless you're practicing XP ...
Daniel's user avatar
  • 16.9k
3 votes

Should common functionalities be repeated as very similar stories within each context they're needed?

A user of the system can have multiple roles at the same time that form a hierarchy from a very generic role to a specific role. For example, if a user is logged in as an Administrator, they will at ...
Bart van Ingen Schenau's user avatar
3 votes

What is the weighting difference between Epic/Story/Task

A shorthand answer: Epic: Generally takes more than one iteration to complete, contains more than one User Story & is written in a User Story format. User Story: Generally is completed in one ...
Shawn Adams's user avatar
3 votes
Accepted

Use of sub tasks vs epics in Jira

If I get your problem correctly, your struggle is about how to effectively break down work. As you explained, you could either work mainly with User Stories and break them own into sub-tasks OR work ...
Tiago Cardoso's user avatar
  • 8,653
2 votes

Epics and stories prioritization in JIRA

Let me sum these up and provide a little more clarity since I can't comment yet. Jira no longer shows Epics in the same manner it shows stories. In the past you could prioritize the Epic itself by ...
Majaii's user avatar
  • 405
2 votes

In Agile methodology, Should epics be named after big tasks/activities encountered in user journey?

Use Story Mapping is powerful and useful, but even for epics you want to think in terms of User Stories. Organizing those stories by "User Journey" is great. That's a way to see the flow and get a ...
Ari Davidow's user avatar
2 votes

Organizing testing in a Scrum(ish) development project

There is nothing scum(ish) about this project Team members are not involved in deciding what can be accomplished in the sprint. No sprint planning. It is top-down. No coordination among team members ...
Ashok Ramachandran's user avatar
2 votes

How to get an Epic span multiple sprints?

The key is to assign the relevant user stories to sprints--not to assign the epic to sprints.
Ari Davidow's user avatar
2 votes
Accepted

Reopen an epic after a feature request?

You create a new Epic with a similar name The key point here is this: after some time - if the customer already signed off on the original feature, it was right to close the Epic. If they've ...
JBRWilkinson's user avatar
2 votes

Agile: Can Epics be time-based rather than feature-based?

TL;DR None of your current examples are really valid epics. They are actually labels, and you should think of them as labels for release targets instead. To use epics properly, you should treat them ...
Todd A. Jacobs's user avatar
  • 50.5k
2 votes

Correct Work Item Hierarchy in Azure Dev Ops

The Epic is just a bigger Feature which itself might require smaller features (multiple User Stories) to get Done. It goes like this: When an item is first added to the Product Backlog it is ...
Alexandru Jieanu's user avatar
2 votes

Correct Work Item Hierarchy in Azure Dev Ops

PBIs should not be treated as something different from epics or features. Epics, features, requirements, and tasks can all be product backlog items. In Azure Devops the hierarchy is as below: Epic |...
Shaunak Lawande's user avatar

Only top scored, non community-wiki answers of a minimum length are eligible