4 ms·

Backlog items can start as rough ideas though. Refining of a ticket can be done later when you need to. But it can only be started to be worked on when the team

Backlog items can start as rough ideas though. Refining of a ticket can be done later when you need to. But it can only be started to be worked on when the team thinks it is refined enough.

idopmstuff 3y ago
In my experience, if you go this route what you end up with is a thousand tickets with a title and little to no description text that eventually get deleted because you can't figure out what it was about six months later (even if you're the one who wrote it).
- bhaney 3y ago
  And that problem somehow goes away if you store that same information in a separate system?
  - xboxnolifes 3y ago
    No, but it's about keeping the ticket box signal to noise ratio in check. One box for actionable, high signal items. One box for all the ~junk~ ideas.
    - peebeebee 3y ago
      Junk ideas are useful to document too. When the idea resurfaces, one can read why it did not get through the first time. A ticket-system like JIRA is the same as an e-mailclient to me. You sort by activity, having the most active tickets on top. You can flag/mark them, you can put them in different boxes or just use tags,... All are just means to create order in chaos. But I would never think to move my old e-mail to a different 'system' than my normal e-mail(client). I never think of old e-mails or drafts as something I need to clean up.
  - fourthark 3y ago
    Yes, because you just don't look at the list at all.
    - IanCal 3y ago
      Which is fine, you can then save even more effort by never writing them down at all.
- morgante 3y ago
  Those don't need to be separate systems, and keeping them in one system is often beneficial to see the evolution of the concept. I'll frequently have an idea and toss it into a backlog ticket. Maybe just as a title to start. When a customer mentions that problem/feature, I can add that info in the backlog even if it doesn't immediately become a priority. When the issue does become something worth working on, I'll usually add more details but the various evidence accumulated over 6 months of letting the item "bake" is invaluable.
  - nicoburns 3y ago
    They don't need to be in principal. But in practice I've yet to find a tool that does both things well.

Backlog items can start as rough ideas though. Refining of a ticket can be done later when you need to. But it can only be started to be worked on when the team thinks it is refined enough.

idopmstuff 3y ago

In my experience, if you go this route what you end up with is a thousand tickets with a title and little to no description text that eventually get deleted because you can't figure out what it was about six months later (even if you're the one who wrote it).

bhaney 3y ago
And that problem somehow goes away if you store that same information in a separate system?
- xboxnolifes 3y ago
  No, but it's about keeping the ticket box signal to noise ratio in check. One box for actionable, high signal items. One box for all the ~junk~ ideas.
  - peebeebee 3y ago
    Junk ideas are useful to document too. When the idea resurfaces, one can read why it did not get through the first time. A ticket-system like JIRA is the same as an e-mailclient to me. You sort by activity, having the most active tickets on top. You can flag/mark them, you can put them in different boxes or just use tags,... All are just means to create order in chaos. But I would never think to move my old e-mail to a different 'system' than my normal e-mail(client). I never think of old e-mails or drafts as something I need to clean up.
- fourthark 3y ago
  Yes, because you just don't look at the list at all.
  - IanCal 3y ago
    Which is fine, you can then save even more effort by never writing them down at all.
morgante 3y ago
Those don't need to be separate systems, and keeping them in one system is often beneficial to see the evolution of the concept. I'll frequently have an idea and toss it into a backlog ticket. Maybe just as a title to start. When a customer mentions that problem/feature, I can add that info in the backlog even if it doesn't immediately become a priority. When the issue does become something worth working on, I'll usually add more details but the various evidence accumulated over 6 months of letting the item "bake" is invaluable.
- nicoburns 3y ago
  They don't need to be in principal. But in practice I've yet to find a tool that does both things well.