Kanbanize Now!

Kanbanize Now!Or - how we kept running two week sprints while our robots shipped in two hours A confession before we startSomewhere right now, a team is holding a sprint planning session to decide what four agents will do over the next fourteen days. The agents finished it during the meeting. Nobody has told the humans, because the humans are busy playing planning poker over a story that has already been implemented twice, in two different branches, neither of which anyone has read. This is not a story about AI replacing developers. It is a story about a process built around a constraint that no longer exists, defended by people who have forgotten why it was built. Agile was a response to expensive feedbackRewind to 2001. Releases were quarterly. Builds were a coffee break. Getting a customer opinion required a formal review with printed documents and at least one person who owned a laser pointer. In that world the two week iteration was genuinely radical - a forcing function that…