Just what I always wanted. My own little process. I will name him Agile, and I will hug him and pet him and squeeze him...
The first principle of the Agile Manifesto is:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
My own LinkedIn bio used to read, "I ship software." I recently expanded it to two sentences, the last bit being "...I help ship software that delivers real value to customers." I believe, much like that first principle of the manifesto states, that the two most important things in a software business are shipping product and making sure that product provides value to your customers. You must have both to be successful. Everything about the organization must support those two things. If they do not support one of those two things, they are probably superfluous.
The Agile methodology was established to support this. It is its stated "highest priority," after all.
What the techniques and processes called "agile" in 2019 do are frequently not in support of shipping or providing value.
Agile software development processes much more frequently:
- Let managers feel like they are getting the most value out of their software developers in terms of output, not in terms of value delivered to customers.
- Allow product owners to exert their will over product direction without any feedback from customers. There's no time to get feedback on existing features when the process is forever focused on getting the feature "right" prior to exposure to actual users, or on the next feature.
- Provide a salve over a systemic lack of trust within an organization.
- Give accreditation to inexperienced software practitioners, giving them a sense of control over the often chaotic, complicated, nondualistic, messy business of developing a system constructed by humans writing lines of code.
I'm quickly running out of time for today...more on this in the future!