Your Kanban Board Ends Too Early
Most Kanban boards stop at release, which quietly teaches teams that deployment is success. If you want impact, make outcome and impact visible in the flow.
Most Kanban boards stop at release, which quietly teaches teams that deployment is success. If you want impact, make outcome and impact visible in the flow.
Most of your scaling apparatus is now optional. Your first principles are not. A companion for leaders running SAFe while adopting AI-native, spec-driven development, and trying to tell the difference.
Is Scrum still relevant when agents write the code? Yes, and more than before, provided you are willing to customize it. A companion to the Scrum Guide walking the accountabilities, events, artifacts, and values for a team running an AI-native, spec-driven lifecycle.
A companion to the Kanban Guide for Scrum Teams for AI-native product teams. What changes in your Definition of Workflow, WIP limits, flow metrics, and Scrum events once agents do the building, and what happens to scaling when the old dependencies start dissolving.
The best time to solve a feature adoption problem is before development. Talk about the user's project, look for real pull, and don't build on polite interest.
AI isn't killing Scrum. It's shrinking teams from cross-functional squads to 1-3 people — and that descaling collapses a lot of org complexity with it.