9 ms·
Just delete stuff you’re not going to do.
by natbennett 14d ago
Just delete stuff you’re not going to do.
- giwook 14d agoYes, but easier said than done.
- bluGill 14d agoHow do I stop someone else from putting that back on my backlog again? Just today I had someone open a bug on my code because they decided that the organization was wrong. Some modules should be moved from one directory to another. Never mind why they opened it as a bug, the reality is people are opening and putting stories on my backlog.
- vogelke 14d agoIf they can't justify why this is a bug, and why it's worth your time to fix this as opposed to something else, you should be able to revoke their permission to touch your backlog.
- isaacaggrey 14d agoI wouldn’t delete any items any backlog items. Much better to always close with a reason. You can make this a first class status in whatever platform like a “Closed - Duplicate”, “Closed - Unneeded”, etc. This helps with searching for rationale in the future, looking back to similar items, etc. You can’t stop someone from putting it back but you can close it as duplicate and link it as related. Edit: also if the person putting work in the backlog is not a core contributor or product you should formalize some other intake process that can triage whether it meets the bar to get in
- tclancy 14d agoThis is great when you’re the sole dev and PM. It does not scale well. Especially if you have stakeholders above you in the org chart.