Professional Documents
Culture Documents
Cast Studies
Cast Studies
For example, your product development teams plan to create a new website. To deploy
it, organise your work using Epics and Stories to manage several teams. You must
design, compose content, code, and test a website before launching it. In this instance,
the process of forming the website is the Epic, while all other components, such as
creating a copy or developing the website, are the Stories.
Stories also referred to as "User stories," are the requirements stated from the end-
users standpoint and smaller parts of work in an Epic. For example, user-facing benefits
that can be substantiated are known as stories. They begin with a line that explains
what it is that we, as potential purchasers of the product, would like to achieve.
Epics consist of several stories, whereas Initiatives are composed of Epics. Thus, we
can assert that ventures are superior to epics. The initiative utilises the Epics from
several teams to accomplish a larger objective than any Epic can very well.
What is JIRA epic? An epic encompasses a substantial collection of work. "Epic" means
"Big Ask." Epic is a comprehensive list of user criteria and product specifications.
An epic may require multiple sprints to achieve. If more than a project is featured on the
boards whereby the Epic belongs, it can span numerous projects.
The software application consists of numerous epics, where each Epic includes multiple
stories to fulfil a task, and each narrative comprises multiple subtasks to accomplish the
task. Initially, we developed the Epic by including user stories. After the Epic has been
created, we view it along with all of the associated tales, make any necessary edits
based on what the person needs, and then pass the project over to the development
team so that they may finish it within the specified timeframe and mark it as complete.
If you want to create a new issue in JIRA, you can click or press C. The dialogue
box appears.
Alternatively, a direct link to create Epic JIRA can be found on the backlog page.
Navigate to the Agile tab and select the option labelled "View on Board." Doing
so will open the Backlog screen, on which the EPICS frame will be displayed on
the left-hand side.
In the dialogue box, choose the project in which this Epic needs to be made from
the drop-down menu.
To create an epic, go to the drop-down menu labelled "issue type" and then
select "Epic."
Give the needed epic name and the title of the summary.
To begin creating an Epic, click the "Create" button.
A confirmation message for the creation of Epic will appear in a small dialogue window.
A unique issue identification number is created when initial credentials such as epic title,
summary, etc., are loaded into JIRA.
To access the Backlog page, click the down arrow next to the Agile link in the
navigation pane. Once you select the option to "View on Board," the page will
load.
On the left-hand side of the backlog page, all epic JIRAs will be shown.
Select an epic JIRA and click on the arrow in the drop-down menu. It displays
choices to customise the Epic's colour theme, name, information, and "Done"
status.
Click the modify name link and enter the new name to rename Epic. You can also click
on "View epic details," which will access the entire JIRA for the Epic.
Epic JIRA allows us to add more information, such as a description and attachments of
necessary documents, assign it to teammates and add members to make it look
complete.
The actions outlined here can be used to create a new issue in JIRA.
Using the drop-down menu on the Agile link in the top menu, pick "View on
Board" to see the Backlog page.
On the left-hand side of the backlog page, all epic JIRAs will be shown.
Click the triangle to the left of an epic's name to view its information.
It will display detailed JIRA information.
To create a new issue in epic, you will need to click on the link "Create an issue in epic."
Alternately, within the epic JIRA, go to the "Issues in Epic" tab and click on the "+" link.
This will open a dialogue box that is identical to the one obtained in the step that came
before it.
Choose the sort of issue you want to create from the menu bar, which may be a story or
a task, and then input the summary facts to generate unique issue identification for the
issue.
Examples of epics
What do epics look like in practice? Here are two Agile epic examples:
1. A wedding reception
The epic is a small wedding reception with 50 guests. A wedding planner will
be in charge of this epic, and it is their job to ensure that all the user stories
are completed to satisfy the clients (the bride and groom). The user stories
could include:
Booking a live band that specializes in the clients’ favored music genre
Each user story will contain numerous tasks. These tasks must be carried out
within a certain time frame or iteration period.
2. A mobile app
In this example, the epic is a new mobile app to accompany an online beauty
retailer. An app development team will be assembled to tackle the various
user stories, which could include:
https://www.altamira.ai/blog/difference-between-epics-vs-user-stories/
https://www.gla.ac.uk/media/Media_730149_smxx.pdf
https://medium.com/@Jia_Le_Yeoh/example-for-epic-user-story-task-and-
bug-7d7b9d4b0931