It is a common mistake to think of agile as a set of practices for software development teams. But it’s not - at least not in the commonly interpreted manner - as indicated by the first principle:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
The majority of development teams practicing agile are - in fact - not agile teams. It’s a harsh statement, I know.
This is for the simple reason that, most so-called agile development teams are locally-optimized to create software. Some of them create working software.
And fewer than those are creating software that customers can actually use, in a true continuously delivered software.
The flaw is in what customers get, not in the fact that they get working software.
This post is the 3rd in a series on Agile Manifesto tl;dr. Click here to go to the first post including an index to the others.
Let’s break this principle to smaller pieces:Add a comment