5 ms·

Thanks! > Backlog w/Work-in-Progress Limit: I think the limitation of items insides lists and having cycles with limits is a good point. Often I feel overwhel

Thanks! > Backlog w/Work-in-Progress Limit: I think the limitation of items insides lists and having cycles with limits is a good point. Often I feel overwhelmed by the amount of ideas we have. I feel most things will never be implemented and just add to the noise. It surely "looks" good (having many cards), if you present it with many different colors and images. But it really doesn't help to sort things out and do the most impactful first. > Icebox I like the idea of the Icebox. I guess thats similar to the "inbox" concept, where you throw in unvalidated requests, ideas, reports, etc. > Tagging Internally I once suggested we should tag by impact and effort score (reddish tones for impact and blueish for effort), but this escalated quite quickly into a rainbow of cards, just adding to the clutter. And it feels like our product manager decides entirely from his gut feeling. Maybe tagging is just noisy in Trello. What's your experience, can you "over-tag" cards? Does it need a limit? Or does it work better in say Pivotal Tracker?

amk_ 10y ago
The tags you are describing are useful for planning but they become noise for developers in their day-to-day interactions with the board. Maybe you could use a custom field on your cards or a bracket [3] notation for effort? You could replace the impact tag by stack-ranking your cards in your Inbox/Icebox project. In general, I prefer to use tags to highlight actionable things like "this is a high priority bug" or "this is ready to deploy" or "this is blocked" more than categorization, which can be better accomplished with separate boards. If your system has the concept of "epics" to group issues, that's a plus as well. PS you might want to take a look at this article if you're having difficulty prioritizing things: https://medium.com/startup-grind/ruthless-prioritization-e4256e3520a9#.tummgadw8 https://medium.com/startup-grind/ruthless-prioritization-e42...
- EduardMe 10y ago
  Yep, that's much better and thanks for the article!

amk_ 10y ago

The tags you are describing are useful for planning but they become noise for developers in their day-to-day interactions with the board. Maybe you could use a custom field on your cards or a bracket [3] notation for effort? You could replace the impact tag by stack-ranking your cards in your Inbox/Icebox project. In general, I prefer to use tags to highlight actionable things like "this is a high priority bug" or "this is ready to deploy" or "this is blocked" more than categorization, which can be better accomplished with separate boards. If your system has the concept of "epics" to group issues, that's a plus as well. PS you might want to take a look at this article if you're having difficulty prioritizing things: https://medium.com/startup-grind/ruthless-prioritization-e4256e3520a9#.tummgadw8 https://medium.com/startup-grind/ruthless-prioritization-e42...

EduardMe 10y ago
Yep, that's much better and thanks for the article!