3 ms·
This is where I’ve landed after doing it a long time. If you need to get more granular than an open Kanban and are time bound, it’s just Kanban that refreshes
by AndrewKemendo 2y ago
This is where I’ve landed after doing it a long time.
If you need to get more granular than an open Kanban and are time bound, it’s just Kanban that refreshes some interval (2 weeks etc…) with a triaged backlog
Realistically the basic winning set up is:
0: Know what you’re building and why
1. Feature/bug funnel
2. Triage to: Next iteration Kanban, prioritized backlog or deleted as unnecessary in forecast window
3. Deliver with unit testing based on Prioritized Time bound Kanban
4. Move Prioritized backlog into next iteration (go too far ahead at your own risk)
5. cut line: return task to step 2
Every step is critical here actually and breaks without each.