3 ms·

Physical boards have a nice feel to it but you can only put so much on it. On JIRA, Trello or whatnot you have the chance to provide some more context using ex

by weitzj 7y ago

Physical boards have a nice feel to it but you can only put so much on it. On JIRA, Trello or whatnot you have the chance to provide some more context using extensive descriptions, pictures, references, urls. I guess if you have a team which is not distributed, and everybody is on the team 100% of their time and you manage that your holidays overlap a lot, it might be feasible to have a physical board. Otherwise I see all this communication overhead to explain to everybody what the thing on the board means in detail.

winrid 7y ago
This. Six years in we're past ticket #45k. Thats a lot of documented work and history that is valuable to be able to search.
- simonmales 7y ago
  I'm two years in on a greenfield project, looking back at the old tickets does happen, but rarely. I guess you could treat as a poor man's documentation, though our tasks are not written in that perspective.
ManuelKiessling 7y ago
> Physical boards have a nice feel to it but you can only put so much on it. I’m wondering if maybe that is the single most important property of physical boards. You have an immediate and tangible feedback that maybe you should stop creating new tasks, and work in getting existing tasks done first.
mytailorisrich 7y ago
> On JIRA, Trello or whatnot you have the chance to provide some more context using extensive descriptions, pictures, references, urls. All of those should not be on a board. That's the problem with Jira and friends, which is widespread in software tools: feature bloat. The limitations of a physical card or a physical board are a feature. The point of a physical board is for everyone to get a summary at a glance. Detailed descriptions, etc. should be in documentation.
- clintonb 7y ago
  I believe the commenter is referring to the ability to add URLs and images to individual stories and tasks. If I’m doing frontend, I need mocks for major UI/UX changes.

by weitzj 7y ago

winrid 7y ago

This. Six years in we're past ticket #45k. Thats a lot of documented work and history that is valuable to be able to search.

simonmales 7y ago
I'm two years in on a greenfield project, looking back at the old tickets does happen, but rarely. I guess you could treat as a poor man's documentation, though our tasks are not written in that perspective.

ManuelKiessling 7y ago

> Physical boards have a nice feel to it but you can only put so much on it. I’m wondering if maybe that is the single most important property of physical boards. You have an immediate and tangible feedback that maybe you should stop creating new tasks, and work in getting existing tasks done first.

mytailorisrich 7y ago

> On JIRA, Trello or whatnot you have the chance to provide some more context using extensive descriptions, pictures, references, urls. All of those should not be on a board. That's the problem with Jira and friends, which is widespread in software tools: feature bloat. The limitations of a physical card or a physical board are a feature. The point of a physical board is for everyone to get a summary at a glance. Detailed descriptions, etc. should be in documentation.

clintonb 7y ago
I believe the commenter is referring to the ability to add URLs and images to individual stories and tasks. If I’m doing frontend, I need mocks for major UI/UX changes.