4 ms·

The problem with trello is linking tickets intelligently is hard. The concept of epic/subtasks is missing. So if a ticket becomes to big, and you want to keep

The problem with trello is linking tickets intelligently is hard. The concept of epic/subtasks is missing. So if a ticket becomes to big, and you want to keep the history while breaking it up, requires a boat load of copy/paste. Also, there is a trend to have a physical board with tickets, as well as a trello board. This was fashionable amongst the scrum masters at previous large employer. It was universally hates as we had to spend loads of time playing with physical cards, then try and copy the state into the ticketing system. Its was annoying and a massive waste of time for everyone. Especially as it didn't encourage people to write the work they've done on the ticket, to allow it to be taken up by someone new.

jimnotgym 8y ago
> Also, there is a trend to have a physical board with tickets, as well as a trello board. Oh no! This sounds like a horrible idea! Two sources of truth, everybody trying to avoid the work of syncing them. Eek. > The problem with trello is linking tickets intelligently is hard. One way is to break any sizeable task onto it's own board. Just note on the card that it has been moved to a board of it's own. There is a logical team>board structure for this. Then you have a master board with the main building blocks on it, and then sub boards with tasks/stories on them. It is no panacea, but it can work
- Wowfunhappy 8y ago
  > One way is to break any sizeable task onto it's own board. Just note on the card that it has been moved to a board of it's own. There is a logical team>board structure for this. Then you have a master board with the main building blocks on it, and then sub boards with tasks/stories on them. It is no panacea, but it can work We've experimented with this type of thing in my company. In practice, we found that having multiple boards for a single project is just a bit too much to keep track of. I could see this working if Trello made it easy to quickly move between boards. This could be something as simple as a breadcrumb style path: Grandparent Board > Parent Board > Child Board, or something to that effect. Or maybe that would overcomplicate Trello, I'm not sure.

jimnotgym 8y ago

> Also, there is a trend to have a physical board with tickets, as well as a trello board. Oh no! This sounds like a horrible idea! Two sources of truth, everybody trying to avoid the work of syncing them. Eek. > The problem with trello is linking tickets intelligently is hard. One way is to break any sizeable task onto it's own board. Just note on the card that it has been moved to a board of it's own. There is a logical team>board structure for this. Then you have a master board with the main building blocks on it, and then sub boards with tasks/stories on them. It is no panacea, but it can work

Wowfunhappy 8y ago
> One way is to break any sizeable task onto it's own board. Just note on the card that it has been moved to a board of it's own. There is a logical team>board structure for this. Then you have a master board with the main building blocks on it, and then sub boards with tasks/stories on them. It is no panacea, but it can work We've experimented with this type of thing in my company. In practice, we found that having multiple boards for a single project is just a bit too much to keep track of. I could see this working if Trello made it easy to quickly move between boards. This could be something as simple as a breadcrumb style path: Grandparent Board > Parent Board > Child Board, or something to that effect. Or maybe that would overcomplicate Trello, I'm not sure.