Thread by @RonJeffries

Today we take as our text, this tweet

https://twitter.com/failfastmoveon/status/1162696278570090496?s=21

Michael is creating a book of cartoons and deserves support.

These notes are about the underlying notion behind this cartoon.

1/11

The co-creator of Scrum, Jeff Sutherland, has done and continues to do great work in the area of Scrum. His 2017 book "Twice the Work in Half the Time" is worth reading.

I reviewed it here: ronjeffries.com/articles/017-0…

2/11

I also commented in that review about the title, which I believe is misleading to the point of being harmful. That's because Scrum won't get _more work_ by somehow whipping the ponies harder. Scrum will, if applied as intended, produce far _more value_ per unit time.

3/11

Value, not work. Scrum doesn't produce features faster, though it might _deliver_ features sooner. How's this possible? Your typical development process builds "all" the features, then does a few years of "final testing", then ships the nearly debugged product.

4/11

Scrum just has to beat that record to _deliver_ features sooner. It does that very simply: you pick a very few features to work on (not "all"), and you get them working within a week or two; working so well that you could actually give them to your users.

5/11

"Shippable Increment" means you really could give the product (subset) that's finished at the end of the Sprint to customers. It's that solid, that good ... and it can be that useful.

6/11

If a sensible Product Owner has truly shippable software in their hands every week or so, it will become clear sooner or later that just maybe they ought to ship it. Maybe they give it to all the users, maybe to just a few.

7/11

For a while they may be thinking "well, I need x and y and z," but even that should focus them on finding the simplest bits of x and y and z so that at least Customer Joe could use it."

8/11

So a wise Scrum PO, seeing working software, is influenced to begin to deliver it. That's good.

And that's not all.

9/11

Scrum puts all the makers together with the making of the thing being made[1]. Decisions are made locally, not by shadowy figures sending down proclamations, not by long intervals of asking permission to do things.

Scrum eliminates value stream delays.

10/11

10.1/11 [*] pacé @GeePawHill

By smoothing the process, and by delivering working software Every Damn Sprint, Scrum _delivers_ value faster.

Twice the value in half the time, not twice the work.

More value, less work. That's Scrum.

11/11