The Agile Community Embraces an Unworkable Fantasy

(Image is from “My Book of Bible Stories”​)
  1. Self-organizing autonomous teams are the best way to organize programmers.
  2. Managers are an “anti-pattern”; ideally there should be no hierarchy, and no one should have explicit authority. All authority and all leaders should emerge through self-organization.
  3. No individual should be accountable: only entire teams should be accountable.
  4. Failure is the best way to learn.
  5. One should always trust the team, even if you have never worked with the team before.
  6. All development teams should be feature teams that work across the entire set of technology stacks of the product.
  7. Anyone should be able to work on anything.
  8. An open team room is the best arrangement, so that people can collaborate most easily and will benefit from “osmotic” communication.
  9. More collaboration is always better, and verbal communication is always best.
  1. Organizations keep their existing market research and product definition methods, which have a long lead time, and which “hand off” product requirements to “IT” to build.
  2. Organizations dismantle old style program-level or product-level leadership, but don’t replace it with an Agile equivalent.
  3. Organizations try to “roll out” Agile, treating it like a process change, when in fact it is mostly a learning journey.
  4. Organizations fail to put sufficient emphasis on the technical side of Agile, which today is “DevOps”.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store