Jira Epics 101 - Learning the Basics

Рет қаралды 74,408

Күн бұрын

An Epic in Jira is a single goal or deliverable that is broken down into a group of related tasks that can be worked on independently. In this video, our Atlassian Director, Josh Kochelek, will break down everything you need to know about Epics. From what an Epic is, to its purpose and best practices.
In Jira, Epics are a special issue type (similar to Task or Story) that can be created by users, with associated fields, screens, and a workflow.
Epics are just one of many ways to organize your team’s work in Jira software and offer a variety of features and benefits for teams using the product. These features were designed to help implement Agile methodologies, but are powerful for any team looking to improve their abilities for planning work, predicting timelines, and adapting to changes as they arise.
Read the blog for more details: moduscreate.com/blog/jira-101...
--------------------------------------------------
📽 Subscribe to get the latest insights from our global team of technologists, designers, and strategists: mdus.co/subscribe
📝 Check out our blog for tips, tutorials, and opinions on application development, customer experience, product management, and more: moduscreate.com/blog
💻 Modus Create builds customer-centric products, processes, and platforms to help businesses succeed in the digital economy.
🌐 For over 10 years, our global team of strategists, designers, and technologists have helped the world’s biggest brands such as Burger King, Kaplan, AARP, PBS, and Time Inc. deliver powerful digital experiences to their clients. We work in an iterative, outcome-driven way to support our clients with product strategy, customer experience (CX), full-stack Agile software development, and security.
📈 Inc Magazine has rated Modus Create as one of the fastest-growing American companies for seven years in a row. Our distributed team of Modites have been pioneers in the open-source community, creating innovations such as the Ionic-Vue integration, RoboDomo, Beep, and Capsule. Visit moduscreate.com to learn more.
#Atlassian #Jira #Epics

Пікірлер: 19

@cna9708 Жыл бұрын

Best Jira problem explanations I found so far are from this channel. Most of the other content feels like 90% filler sentences and a demonstration how to click two buttons to achieve almost nothing

@BrianRichardson-jn7vn Жыл бұрын

Excellent intro to Epics and I'm headed right over to Components next as we're trying to put an end to Epics without an end date. Great video, looking forward to checking out more now.

@moramoga 2 жыл бұрын

Great material Josh and Modus team!

@0Sareena0 Жыл бұрын

Amazing content, super useful man. Thank you!!!

@BirdRockin Жыл бұрын

Great basics video! Epics explained in plain English with easy to understand examples

@minzeymichael 11 ай бұрын

Nailed it. This really helped clear things up for me.

@user-jd3fp7fo4w 7 ай бұрын

Great content, SUPER helpful. Thanks

@ChristophGranz 2 ай бұрын

Good introdution to epics in Jira. Thank you.

@KordTaylor 6 ай бұрын

Nice video. Thank you! 👏🏻👏🏻👏🏻

@roberthall7225 Жыл бұрын

Hey there. When you are viewing the drop down in the epic panel from the backlog, do you know how the "estimate" is figured? I know you can set it to show from either story points or time, depending on what you use. What I'd like to know is, when you're using story points, what drives the estimate? I know it's not a straight total of all of the issues within that epic that have been pointed. Can you shed some light? Thanks!

@biomagician Жыл бұрын

Hello, thanks for the video. Do you have a recommendation for how long an epic should last?

@stevemaiorano7065 8 ай бұрын

Depends if you are doing a release or not, how long is the release? Does the Epic need to be carried over into another release?

@andreparadise Ай бұрын

good stuff

@egeorge4097 10 ай бұрын

When you receive your EPIC from your task manager/product owner/team leader as a Business Analyst, how do you proceed/go about to do your day to day tasks with that EPIC piece of work?

@noeljriveropino5906 2 жыл бұрын

Hi Josh, I have a question. Let's say I am working in a project that has this parts, a web app, a mobile app, and a Rest API. Should i create 3 different kanban boards? or 1 kanban board and the 3 parts should be created as components?

@joshkochelek9691 Жыл бұрын

Hey Noel - It really depends on how your are managing the team, running your meetings. You can either create separate boards that filters to specific components, or you can build one board with custom swimlanes based on the components. There's other ways too (like building one board and then having quick filters based on components) It's just a matter of what data you want to be present on the board.