You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I've found myself taking a bunch of different approaches. Each has its merits. What is everyone else doing?
Epics should be used when you want to group a bunch of issues together for visibility and easy tracking of percentage done. Think of it like a traditional project level grouping where the project has a defined start and end date.
We typically do not use story or task but create our own issue types because Story and Task are too generic for the work we do and it makes it harder to get metrics.
Here's an excellent blog by Mike Cohn on the differences between Story and Task:
https://www.mountaingoatsoftware.com/blog/the-difference-between-a-story-and-a-task
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.