Thread by @RonJeffries

I said I was going to steal this idea, and here goes. Agile is a style of working expressed in values and principles, and frameworks offer various practices. The point isn't even to be "Agile", it is to improve at whatever you're actually supposed to be doing.

Inspect and Adapt.

There's apparently no limit to how good or bad you can be. (For proof, look around you.)

What you call better and worse is up to you. It's not about Agile, it's about your world.

There's just where we are, and which way we move:

Now of course our problem, and the ways of adapting are multi-dimensional. I'll draw two, owing to the limitations of my ability to draw. Picture this in 15 dimensions, please.

We are somewhere and we can improve or get worse:

So the notion of "Agile", and of "Agile frameworks", and for that matter all frameworks, I imagine, is to enable the people to move from where they are, toward "Better" results.

There are many paths to "Better", and you get to choose. "Agile" makes some suggestions.

Now your job is complex, in the formal sense, and the things to do are not cut and dried. Sometimes, after a while, you'll notice things aren't improving. If you're wise, you'll try something else:

There is no finish line, no boundary. We can always improve, we can always deteriorate.

And there's no line in the middle where to the left we're bad and to the right we're good.

Use Agile ideas as hints for things to do to get better at your work, not better at "Agile".