Your Scrum Team Didn't Get Obsolete. Some Of Its Mechanics Did.
Don't ask whether you still need Sprint Planning. Ask whether you still have an alignment problem. Separating the mechanism from the capability is the whole game right now.
Don't ask whether you still need Sprint Planning. Ask whether you still have an alignment problem. Separating the mechanism from the capability is the whole game right now.
Product ownership is an accountability, not a job title. How I think about it for one team, for an inbound/outbound split, and for a platform team getting asks from five different products.
Every time I introduce a portfolio Kanban, somebody asks about WIP limits. At the portfolio level my answer is usually: don't limit WIP: at least not that way.
A practical conversation on why strong sales and GTM leaders must run today's business while continuously improving the system that creates tomorrow's results.
I revisited my 2011 talk on scaling Kanban from team to program and portfolio. What still holds up, and what I would change today.
When you are running specs through coding agents, the spec is the work in progress. WIP limits are the valve that keeps agentic throughput from piling up in front of the humans who still have to review it.