When to Use Epic vs Story

Рет қаралды 6,535

Күн бұрын

Are you confused about when to use Epics and Stories in your Agile project management? 🤔 In this informative video, we dive deep into the key differences between Epics and Stories, helping you gain clarity on how to effectively utilize them in your projects.
📌 Epics: Discover how Epics serve as the backbone of your project, representing high-level initiatives and major functionalities. We'll explore when to create Epics to encapsulate large-scale project components and guide your team towards a well-defined vision.
📋 Stories: Understand how Stories contribute to the breakdown of Epics into manageable, user-focused tasks. We'll show you when to craft user stories, ensuring they are granular enough for efficient development while meeting end-users' needs.
If you are enjoying the content and want to help support the channel, check out the links down below!
Udemy - Jira Fundamentals Course - www.udemy.com/course/jira-clo...
Apetech Merch Store - my-store-dc4aec.creator-sprin...
Subscribe to The Jira Life - / @thejiralife
And don’t forget to check out channel sponsors down below!
Check out our sponsor's app Out Of Office
marketplace.atlassian.com/app...
Get 20% off with the following codes:
Monthly Billing code: OOOAAPETECH
Annual Billing code: AB6H8V
Link to my other Atlassian Jira videos
• Jira Tutorials
Link to my Atlassian Live Streams:
• Jira Community Live St...
Link to Atlassian's Jira products:
www.atlassian.com/software
Link to my Fiverr profile:
www.fiverr.com/alexortiz924?u...
Link to my Upwork profile:
www.upwork.com/freelancers/~0...
#agileprojectmanagement #ScrumMaster #productowner #agiledevelopment #agilemethodology #EpicsVsStories #userstories #AgileBestPractices #projectmanagement #agileteams #AgilePlanning #softwaredevelopment #teamcollaboration #AgileSuccess #AgileProcesses #ProjectVision #IncrementalDevelopment #AgileLeadership #AgileTraining #EfficientDevelopment #AgileTips #AgileMindset #AgileDelivery #AgileCommunity #AgileLearning #AgileSkills #AgileMastery

Пікірлер: 8

@robertwen-releaseteam6820 Жыл бұрын

Loved that you used Bill Wake's INVEST model!

@rillest75 6 ай бұрын

This video was EPIC!!

@elim9780 Жыл бұрын

Shared with coworkers! That good

@nikk4 5 ай бұрын

Thanks so much for the video! Can you please do a video with an example company/project that showcases how work actually flows from Jira Product Discovery (JPD) to Confluence to and from Jira? At what point should we be creating Objectives, Strategies, Themes, Families, Initiatives, and Epics? What’s the best way to use Atlassian so everyone on your team (Dev, Product, Design, Sales, Customer Success, Marketing) can visually see our Roadmap and be able to track down our progress from Mission/Vision to Story/Bug/Task and Subtask (and everything in between). How can Jira be set up to help *everyone* see how their individual and teammates’ work is helping our cause, and furthering us closer to achieving our mission. (Best practices for tracking OKRs?) And what are best practice tactics to know when to create a Confluence page? (As Jira rolled out multiple layers of hierarchies above Epic to all Premium & Enterprise users, do you find it best to create a Confluence Page for Initiatives or Epics or both and why? If Initiatives get a Confluence Page, is it good/bad practice or link multiple Epics (one for each major version like v1, v2, etc.) to that Initiative’s Page? Or one Confluence Page to one Epic? But then the individual Epics without an Initiative doc don’t relate easily to each other, so there may be lost context or understanding how/why something was done a version way , especially when retrospecting.) But how do you keep important context for yourself and for teammates who are working on these issues but may be removed from customers or impt context? 🎉❤

@user-nj3fo7ng5b 11 ай бұрын

You are an awesome resource!

@raaghavsh2926 Ай бұрын

So as a Senior PM, I want my engineers to create an internal Product dashboard for me with some key metrics that I want to track on a daily basis. Now although this is not directly affecting my Product or our customers nor is this an increment, this is still a new requirement. Hence, I want to capture this on Jira. So in order to do this, do I have to create an Epic for this titled 'Product Metrics Dashboard' for example and then add user stories within this Epic for each of the metrics that I want to track? Any suggestions would be great.