KODE Kanban
How we work is Kanban adapted to projects. Work flows continuously instead of being packed into sprints, and engineers pull new work when they have room for it.
The flow
Every project moves through six steps. Each one has its own page with the details.
- Step 1: Choose the work Product with business leaders; engineering leadership staffs it
- Step 2: Shape the work Project lead and product
- Step 3: Estimate and plan Project lead; forecast checked by engineering leadership
- Step 4: Build with AI Engineers, with product and design
- Step 5: Review and release Peer review; product enables feature flags
- Step 6: Finish clean Post-live milestone: flags, data and debt
AI at every step. People own the quality of each one.
Between projects, engineers pull smaller requests from the 1-Offs project, then pick up the next project.
What makes it Kanban
- Work flows; it isn't batched. Projects and their milestones move across our two-week cycles rather than being forced to fit inside one.
- People pull work. Engineers pick up the next story when they finish one, and pull smaller requests from the 1-Offs project between projects.
- Capacity sets the pace. We take on the work we have the capacity to deliver well, instead of committing to a fixed amount each sprint.
- Flow stays visible. Linear shows where every project and story stands, and the forecast shows whether each project is on track.
What makes it ours
Textbook Kanban moves individual tickets through a board. We plan around projects and milestones: each milestone is a useful increment customers can use, and each project ends with a post-live milestone so the next team inherits clean code.
The two-week cycle is a rhythm for planning and checking forecasts, not a deadline. It isn't Scrum: there are no sprint commitments. And it isn't waterfall: we release in increments and learn from customers as we go.