-
Agile started as a developer-led reaction to the heavyweight processes that valued output over outcomes, utilization over effectiveness, clairvoyance over evidence.
-
> I think that ultimately, Extreme Programming has mushroomed in use and interest, not because of pair-programming or refactoring, but because, taken as a whole, the practices define a developer community freed from the baggage of Dilbertesque corporations agilemanifesto.org/history.html
-
The 4 main values include two that focus on empathy for sustainable software development > Individuals and interactions over processes and tools > Customer collaboration over contract negotiation
-
The other two are implicitly empathetic > Working software over comprehensive documentation > Responding to change over following a plan
-
The principles also encourage empathy for "users, colleagues, and partners" where they are referred to as Customers, Business People, Developers, and Individuals
-
Many "Agile" organizations do focus more on reducing cycle times than they do on promoting sustainable development. Many "Agile" organizations don't even know about cycle times and they just follow the policy/procedure they were taught is "Agile".
-
Essentially a lot of organizations have been "dilbertizing" agile development. That's not a problem of agility being a core principle. It's a problem of not keeping true to valuing "empathy for users, colleagues, and partners"
-
And that final thought of o11y being a reflection of empathy?
-
I'll leave further reaction to that as an exercise for the reader