Why Everybody Hates Agile • Jesper Boeg • GOTO 2023 (Category Management)
Interesting. report From Jesper Boeg, Agile/Lean Coach, who explains why everyone doesn't like Agile and Agile coaches:) Slides of this funny presentation are available here, and the main thoughts that I took for myself are set out below.
- Agile has been reduced to a set of practices Instead of agile principles, it is now customary to operate with a set of practices that should bring success. For example, these are discovery and delivery cycles, sprints and burndown charts, double diamonds from products, agile release trains, system and solution architecture, and so on. Further, adherents of different practices howl with each other in religious wars, missing the significance of the context that gave meaning to those practices that approach it.
- Agile has become a monster A dogmatic approach to proper agile (Scrum, Less, SAFe, Kanban, Scrum&Scale, Nexus, ...) We got a monster, but there's no evidence that one approach is always better than the others. - Excuses are abundant But people try to explain the canonical approach to the whole organization in different ways. (||If anything, these explanations are crap in lean oil.||): If the processes are different, it will be difficult for people to switch between teams.
- It's a "proven" method. If we do everything according to the book, we will definitely be forced to solve real problems. If we don’t do everything the same, we won’t be able to share our ideas. We need to clearly define roles and responsibilities at all levels. - We should not be surprised - We shouldn't be surprised that this is happening. The world around is complex, and the brain is lazy and tries to use the second system at a minimum. (I recommend reading Kahneman’s book, “Thniking, Fast and Slow.” remembered earlier) - Agile gone wrong: Theory vs reality Here the author gives a selection of theses that in practice differ from what the agile theory says. Sprint Commitment Will Ensure Efficiency – The sprint goal is sometimes unattainable ONLY Working quality software to scale counts - sometimes you need to make low-quality but quickly get money Product Discovery on Everything – The Author Cynefin framework And he says that obvious and complicated don't really require discovery. Scrum Master as a full time role - but not always)
- and a bunch of other examples.) Summary & advice – the author concludes on a high note, remembering the basic principles that are more important than the set of practices that he tries to adhere to
- A purpose for each team
- An outside-in organizational structure
- Teams are empowered, self-organizing and relatively stable
- Small batches
- Early and continuous market, customer and end-user validation
- End-to-end pull system
- Operational and technical excellence
- Modern leadership But he also mentioned that Business structure is important A starter set of practices is important, but it should be used wisely and immediately explain why a particular practice is useful in the current context. If you have to change management, do not change everything at once.)
#Management #Processes #Leadership #Agile #Philosophy