A Push Has a Beginning, a Middle, and an End

A Push Has a Beginning, a Middle, and an End

Michael WiseMichael Wise
3/12/2026
6 min read
Method
Ways of Working
Push Manifesto
Agile
Software Development
Delivery

Why call it a 'push' and not a sprint, a story, or a task? Because the word carries the thing the others lost: a unit of work with a real shape β€” and most importantly, a real end.

People ask why I bothered with a new word. We already have sprints, stories, tasks, epics, tickets, cards. Did the world need "push"? I think it did, because the words we had quietly lost the most important property of a unit of work: that it ends.

A push is a logical unit of output with a beginning, a middle, and an end. That's the whole definition, and every word in it is doing a job.

Watch how work actually behaves in most teams. A "story" gets carried over. A "task" spawns three more and never quite closes. A "sprint" ends on the calendar but the work inside it doesn't, so it migrates to the next one wearing a new number. The unit of work has become a fiction β€” a label on a continuous, shapeless stream that never resolves.

This is corrosive in a way that's hard to see day to day. Work that never ends never gives you the small, real satisfaction of completion. It never lets you stop, look back, and learn from a finished thing. It just flows, and you bail water, and the board is always full.

A logical unit of output that has a beginning, middle and end. 'End' generally represents completion.

The end is the load-bearing word. A beginning is easy β€” we start things constantly, often too many. The middle is where the work lives. But the end is what most processes have quietly deleted, and its absence is why teams feel like they're running on a treadmill.

An end means three things. It means the output is complete enough to stand on its own β€” not perfect, but done in the sense that it delivers the value it set out to. It means you can stop, by definition, because the thing is finished. And it means you get a clean edge to learn from: a finished push is a closed experiment you can actually evaluate, where an open-ended stream of work resists all measurement because it never holds still.

"Logical unit" matters too. A push isn't a fixed-size box you cram work into until the timer goes off. Its size is set by the work's own shape β€” the natural boundary where one coherent piece of output is complete. Some pushes are an afternoon. Some are three weeks. The discipline is that the boundary is real β€” it corresponds to a thing being genuinely done β€” rather than imposed by a ceremony's clock.

This is the quiet break from time-boxing. The box can be useful for rhythm, but when the box becomes the unit, you get work shaped to fit the box rather than the box shaped to fit the work. Half-finished things get declared done because the sprint ended; whole things get artificially split because they didn't fit. The push inverts that: the work defines the boundary, and the boundary is honoured.

A thing with a beginning, middle, and end has a shape, and a shape gives you somewhere to stand. You know where you are in it. You know what "done" looks like before you start. You know when to roll 'em. You can hand it to someone and they can see its edges.

That's what the word "push" is protecting. Not a methodology β€” a shape. The simple, almost old-fashioned idea that work should be the kind of thing you can finish, and then actually finish it.

A Push Has a Beginning, a Middle, and an End Β· Push Manifesto