Delivery
Sprints, ceremonies, releases and the process around them.
Delivery in practice
Most delivery problems are not engineering problems. They are commitments made against capacity that does not exist, ceremonies that produce updates instead of decisions, and releases treated as events rather than habits. These pieces are about the arithmetic and the process underneath a team that ships predictably: how much a sprint actually holds, where the hours go before anyone opens an editor, and what to change on Monday.
Related tools and pages
Something isn't shipping. Let's find out why.
Send me three sentences about what's stuck, or take the free 30-minute call. Either way you'll get an honest read - including if the answer is that you don't need me.

