3 ms·

Thanks! I can see a bit different approach in your workflow, which I like. In our lists, we don't track specific releases, the cards are just continuously movi

Thanks! I can see a bit different approach in your workflow, which I like. In our lists, we don't track specific releases, the cards are just continuously moving up the chain. In your approach you are tracking releases separately from the backlog. I think the last part you mention, to keep a card limit, is what broke our system from time to time. And the reviewing is probably very important, so stale cards are not kept around for no reason. Is there a special way you organize your backlog board? Such as sorting it in themes of your application, urgency, etc? And do you keep track, if it was an external user request (and from how many) vs internal request (your own ideas) or other metrics? Do you find attaching estimates help, such as effort + impact?

loumf 10y ago
> Is there a special way you organize your backlog board? One list for each priority/case-type pair, so High-bug, Medium-bug, ... High-Feature, Medium-Feature, etc' > ... external user request If support made the card, they attach the case. No reporting on this though, it's mostly for followup -- when the card is moved to a Done, we can let the customer know what release it will be in. > estimates We do a very high-level estimate bucket. Mostly to size the release.
- EduardMe 10y ago
  I like the idea of attaching the case. Not only for following up, but also for reading the whole reason why something should be implemented and it shows the developers that there is a real person with a real pain behind it. Furthermore reading the original case sometimes helps in finding more efficient solutions. > high-level estimate bucket How does this bucket look like? Something like: `within 6 months`, `3 months`, `this month` or kind of effort oriented like `high effort` (takes long), `medium effort`, `low effort` (quickly implemented)?
  - loumf 10y ago
    Effort and in days. Cards that are more than 10 days get broken down.

loumf 10y ago

> Is there a special way you organize your backlog board? One list for each priority/case-type pair, so High-bug, Medium-bug, ... High-Feature, Medium-Feature, etc' > ... external user request If support made the card, they attach the case. No reporting on this though, it's mostly for followup -- when the card is moved to a Done, we can let the customer know what release it will be in. > estimates We do a very high-level estimate bucket. Mostly to size the release.

EduardMe 10y ago
I like the idea of attaching the case. Not only for following up, but also for reading the whole reason why something should be implemented and it shows the developers that there is a real person with a real pain behind it. Furthermore reading the original case sometimes helps in finding more efficient solutions. > high-level estimate bucket How does this bucket look like? Something like: `within 6 months`, `3 months`, `this month` or kind of effort oriented like `high effort` (takes long), `medium effort`, `low effort` (quickly implemented)?
- loumf 10y ago
  Effort and in days. Cards that are more than 10 days get broken down.