#NoFrameworks: How We Can Take Agile Back!
A fundamental philosophy from the early days of Agile, and particularly of XP, is that teams should own their process. Today we would say that they should be allowed, and better yet, enabled, to choose their own way of working (WoW).
This was a powerful vision, but it was quickly abandoned to make way for the Agile certification gold rush. Why do the hard work of learning your craft, of improving your WoW via experimentation and learning, when you can instead become a certified master of an agile method in two days or a program consultant of a scaling framework in four? It sounds great, and certainly is great for anyone collecting the money, but 18 years after the signing of the Agile Manifesto as an industry we’re nowhere near reaching Agile’s promise. Nowhere near it.
We had it right in the very beginning, and the lean community had it right all along – teams need to own their process, they must be enabled to choose their WoW. To do this we need to stop looking for easy answers, we must reject the simplistic solutions that the agile industrial complex wants to sell us, and most importantly recognize that we need #NoFrameworks.
Outline/Structure of the Talk
- Meaculpa - My background in frameworks
- What is a framework?
- What is the problem with frameworks?
- Why are frameworks so popular?
- How effective are frameworks in practice?
- What actually works?
- How can we take agile back?
- Understand what the tradeoffs of frameworks/methods are
- Learn about proven lean continuous improvement strategies that work better than, and will enhance, the adoption of frameworks
- Learn about how we can escape from "method prison" and take agile back
Prerequisites for Attendees
Understanding of agile