this post was submitted on 16 Jun 2023
26 points (100.0% liked)
Experienced Devs
3979 readers
1 users here now
A community for discussion amongst professional software developers.
Posts should be relevant to those well into their careers.
For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:
- Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
We habe feature or feature scope epics but also never ending category epics for improvements and support, and project sources. Support gets one task per sprint and subtasks to it. Bugs typically don't fall into epics.
I'm not clear on what misc and organized means for you.
We track (technical) opportunities separately. They put noise into the backlog and never get some. Unless a dev actually does them.
Epics serve for longer term planning and prio.
Other than for sprint planning and refinement the deeper backlog doesn't need much organization. Just some categorization, and to the degree those responsible for picking next tasks/work can do so.
I guess the main tool is epics for categorization. Other than that misc is misc, and order in the backlog is all you can do and is good enough.