Jon is a self-taught programmer, started in video games but now does web development. He follows principles, argues for scientific software development, and does not like writing in the 3rd person.
If by "Toss it from the backlog" you mean delete that idea then I disagree because you lose the iterations that idea received in its lifetime (all the comments etc.). If you mean move it somewhere else then I also disagree, because why not just store all the ideas there to begin with?
What do you feel is advantageous to creating a backlog item, rather than letting ideas stay in the forum you mention? Ideas could percolate and combine in creative ways on the forum and act as inspiration for stakeholders, and only when the time is right would the backlog item be created.
With this I also call to mind Lean favouring pull systems, instead of pushing stories into the pipeline. Pushing is waste, that's the path to a warehouse of products that go unused, it's better off eliminated IMO. I favour a simple backlog that spells out a specific and actionable direction for the product over some reasonable timeframe.
Having worked in QA for a while I would never really delete anything, at most mark it with a "deleted" flag. :)
However marked, it would simply no longer appear in the list of active things to consider. It can still be searched, and if it comes up again it is resurrected from its zombie state.
Forums tend to be chaotic in my view. You don't necessarily get threads, instead having multiple threads over months talking about similar requests. The "backlog" (a generic issue system in my mind) would combine these posts into a central location. In no way does it block any forum activity.
It doesn't matter by which criteria something makes it into the backlog, even if fully thought out and planned, some will eventually be ignored. The rate of addition will always exceed the rate of implementation. This is okay, since as you said (or implied) in the original article, it's more important to adapt to current cirumstances than complete the list.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi EdA, thanks for sharing your thoughts!
If by "Toss it from the backlog" you mean delete that idea then I disagree because you lose the iterations that idea received in its lifetime (all the comments etc.). If you mean move it somewhere else then I also disagree, because why not just store all the ideas there to begin with?
What do you feel is advantageous to creating a backlog item, rather than letting ideas stay in the forum you mention? Ideas could percolate and combine in creative ways on the forum and act as inspiration for stakeholders, and only when the time is right would the backlog item be created.
With this I also call to mind Lean favouring pull systems, instead of pushing stories into the pipeline. Pushing is waste, that's the path to a warehouse of products that go unused, it's better off eliminated IMO. I favour a simple backlog that spells out a specific and actionable direction for the product over some reasonable timeframe.
Having worked in QA for a while I would never really delete anything, at most mark it with a "deleted" flag. :)
However marked, it would simply no longer appear in the list of active things to consider. It can still be searched, and if it comes up again it is resurrected from its zombie state.
Forums tend to be chaotic in my view. You don't necessarily get threads, instead having multiple threads over months talking about similar requests. The "backlog" (a generic issue system in my mind) would combine these posts into a central location. In no way does it block any forum activity.
It doesn't matter by which criteria something makes it into the backlog, even if fully thought out and planned, some will eventually be ignored. The rate of addition will always exceed the rate of implementation. This is okay, since as you said (or implied) in the original article, it's more important to adapt to current cirumstances than complete the list.