Re:Ask HN: How does your team run the kanban backlog/board?
by mharroun on Thursday April 25, 2019 @07:57AM
(#19747112)
Our product/dev team is ~18 but how I like to do these things:
- "Projects" are set as epics / clusters of tickets
- Ordering of the backlog/board follows as such:
-- Critical bugs
-- Critical "One off" Tasks
-- Sets of Project tickets by priority.
-- Uncritical issues if time allows (moves up in urgency as it sits)
Ideally the following happens for us:
- A group of 2-4 devs work on each project batch of tickets
- If a bug/task can be done by the person who "owns" that system they should do it, but this should never delay critical work.
We have a 30 min weekly meeting to review the status of completed/in-progress work as well as discuss newly added bugs and one-off tasks. Some times this is as fast as 10-15min. This is where we poll to feel if we will hit the deadlines of the product/engineering roadmap and compensate if needed.
Major projects/epics follow a project kick off meeting and then a technical spec/review phase before tickets are then put into an epic to be executed.
- "Projects" are set as epics / clusters of tickets
- Ordering of the backlog/board follows as such:
-- Critical bugs
-- Critical "One off" Tasks
-- Sets of Project tickets by priority.
-- Uncritical issues if time allows (moves up in urgency as it sits)
Ideally the following happens for us:
- A group of 2-4 devs work on each project batch of tickets
- If a bug/task can be done by the person who "owns" that system they should do it, but this should never delay critical work.
We have a 30 min weekly meeting to review the status of completed/in-progress work as well as discuss newly added bugs and one-off tasks. Some times this is as fast as 10-15min. This is where we poll to feel if we will hit the deadlines of the product/engineering roadmap and compensate if needed.
Major projects/epics follow a project kick off meeting and then a technical spec/review phase before tickets are then put into an epic to be executed.