Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,641,232
Community Members
 
Community Events
196
Community Groups

Story or Task relationship to Sprints-Fit with Epic/Story hierarchy

It appears to be "common wisdom" that a (Jira) Story should be accomplished in single sprint.  Does this mean that a complex task that has integrity still needs to be broken down until all the pieces fit can each fit a sprint?

Does this imply that for a Unit of Deliverable value ("Epic"), there can be huge complexity between a (Jira) Epic and its (Jira) Stories? 

If so how do we manage the logical continuity between the master Epic, and the Stories that are required to materialize it?  To my mind it implies levels of Epics within Epics or Stories within Stories? 

Or is everything reported/managed in Jira as just a two-level hierarchy?

(I assume Sub-tasks are out of the picture as they cannot earn story points, and tasks are for practical purposes (maybe a different Workflow) the same as stories.)

0 comments

Comment

Log in or Sign up to comment