Re:The size of abacklog is inversely proportional to how oft...
by doix on Tuesday January 23, 2024 @10:42AM
(#39104863)
Yeah, I agree with that. I should have been more specific in my comment. Going directly from feedback to _development ticket_ is (sometimes) bad. Sometimes when it's just "this is broken", it's fine.
I agree that you need some system to track feedback. I'm not convinced a board is the optimal choice, because (some?) feedback is kind of timeless. In my mind, it is never "done". Feedback can apply to future features that haven't been thought of yet when the feedback was originally processed, so it's valuable to keep it around in some sort of tag based system. You probably want a way to easily search it as well when designing new features.
Re:The size of abacklog is inversely proportional to how oft...
by datadrivenangel on Tuesday January 23, 2024 @02:51PM
(#39108780)
The central paradox of product development: planning is work, and eventually planning is enough work that you need to plan to plan to plan to plan and the whole thing collapses because you try to systematize judgement too far up the value stream.
Re:The size of abacklog is inversely proportional to how oft...
by happytiger on Tuesday January 23, 2024 @11:47PM
(#39113748)
Pretty on point.
Re:The size of abacklog is inversely proportional to how oft...
by stag91 on Friday January 26, 2024 @09:30AM
(#39142978)
https://www.getcustomeriq.com/ is pretty much dedicated to "evaluating feedback and determining whether it is actionable" fwiw
Maybe you don't want raw feedback dumped directly into your development board, so you might not just add extra columns to it, but another parallel board whose "done" column flows into the dev board's backlog seems like a reasonable approach.