Whatever your “agile” software of choice is, there is a high chance you use Epics.
Most projects use them to organize Stories/Tasks/Spikes and whatever other types of tickets you have in your backlog.
But are epics only buckets for organizing your tickets, or should they be something else?
It is not uncommon to see Epics in the backlog serving as eternal buckets. Their cycle time started when the project started and has been running since.
But, do they provide any value this way? Or do we have better ways to map this work?
In this series, I will be talking about some generic Epic tips and tricks while others will relate to Jira. If you are not aware of this software, you are a lucky person. I’ve been using it for the past 10 years.
So buckle up, this will be an interesting one. Share it with your Product Owners.
If you have ideas or questions please feel free to reach out to me on LinkedIn or via email.