3 ms·
If it's just a ticket in a 2000-task long backlog somewhere, it won't help much anyway. What you actually need to have around is the person who had the idea in
by kqr 3y ago
If it's just a ticket in a 2000-task long backlog somewhere, it won't help much anyway. What you actually need to have around is the person who had the idea in the first place, so they can champion it, adapt it, and flesh it out.
But if they're around anyway, they can keep it in whatever personal backlog they have instead.
- _w1tm 3y ago> But if they’re around anyway, they can keep it in whatever personal backlog they have instead. How should I manage my personal backlog? There’s over a 100 post-it’s on my desk. Should I create another backlog for longer-term ideas or maybe hire a personal PO?
- nicoburns 3y agoI use Apple Notes. > Should I create another backlog for longer-term ideas IMO yes. That way you can easily review it before meetings, and come ready to said meetings with your most important items. I think this is quite a personal thing, so this kind of workflow may not work for you. But I found it almost impossible to work without such a list.
- danielmarkbruce 3y agoThis doesn't work at any reasonable sized org. Maintaining ideas in people's heads falls over quickly as people come and go. It's work to keep a backlog not a total disaster, but that doesn't mean the answer is "tool x" or whatever. It's just work. Ugly annoying work. Ie, work.