3 ms·
I've been thinking about the BackLog problem a lot ... the problem I've always had is the backlog tends to massivity (that's a word, right?) really quickly. A p
by tobyhede 15y ago
I've been thinking about the BackLog problem a lot ... the problem I've always had is the backlog tends to massivity (that's a word, right?) really quickly. A profusion of ideas and notes and bugs that end up as a special type of project debt and dragging the tool and team down with it. My current thought is that beyond the immediate future, the backlog doesn't belong on your wall at all ... use a wiki, or a bug tracker, or something designed to capture that sort of information more completely than a planning tool. Stories get promoted to the wall during planning and they are acted on immediately.
- evlpuppetmaster 15y agoYeah I agree. Part of the point of lean is not specifying too much too early. Inevitably new ideas, problems, priorities will crop up and if you've specced out too much too soon, some of it will go to waste. Perhaps the ability to hook up with APIs would be useful though, so you can manage features and bugs in other tools (GetSatisfaction eg).
- tobyhede 15y agoOne of the ideas I have been toying with is using StoryWall as the visualisation tool that plugs into your other apps ... so purely for communicating and visualising workflow, and the details of your system are in tool of your choice.