Return to site

SCRUM: The Increment Is Dead by Yuval Yeret

· scrum


An Increment is a concrete stepping stone toward the Product Goal.

Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together.

To provide value, the Increment must be usable.


The Increment Got Us Here

If you’re a veteran 👴 of the software industry, you remember those days when we released to production every couple of months.

If you’re also an experienced 💪 Scrum practitioner, you probably associate the time you started to use Scrum with when you started to release more frequently.


Transcending Scrum and the Increment?

But these days, you might think that since Scrum is focused on Sprints, You need to transcend 🪄 Scrum.

Can I ask you a couple of questions?


The Need For Continuous Deployment

Why do you need Continuous Deployment?

Most of the Scrum practitioners answer to that is “Not Really”. 🤷

So, why?

The reason is empiricism 👨‍🔬.

In growing business and technical uncertainty, those with the fastest feedback loop 🔄️ win.


What we mean when we say Working Software

Classic teams only get to that level of “working” pretty infrequently.

Their REAL feedback loop takes weeks if not months 😱 to close.

Their level of empiricism leaves much to be desired. 👎


Continuous Deployment with Scrum and Kanban

Kanban helps the Scrum Team identify bottlenecks.🍾

The role of the Sprint

Scrum sprint is not forcefully a release cadence.

Great Scrum Teams plan on a cadence.

They release on demand. 🛂



The Increment isn't dead. ❌☠️

#scrum #increment