Ask HN: What's your most useful Kanban system for small software teams?

Re:Ask HN: What's your most useful Kanban system for small s... by loumf on Saturday March 25, 2017 @09:30PM (#13958505)

> 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.

[ Parent | on HN ]

Re:Ask HN: What's your most useful Kanban system for small s... by EduardMe on Sunday March 26, 2017 @10:42AM (#13961005)

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)?

[ Parent | on HN ]

Re:Ask HN: What's your most useful Kanban system for small s... by loumf on Sunday March 26, 2017 @01:33PM (#13961894)

Effort and in days. Cards that are more than 10 days get broken down.

[ Parent | on HN ]