Little by little, Agility has been diverted and no longer belongs to developers. In this article you will understand how much the developers have become forgotten from agility.
Image already added
Image already added
In 2001, 17 brilliant developers tried to find an answer to this interrogation: the way we deliver software is not efficient at all. How could we do it differently, so they asked themselves a lot of questions:
That came out from their discussions is what we know as the agile manifesto : 4 values and 12 principles. It is the heart of agile and it has been designed by developers for developers.
Nowadays when you talk about agile, people will make a shortcut and will talk to you about scrum that’s because Scrum is the most used agile framework in companies.
The rules of the game are simple, and all explained in the scrum holy bible: the scrum guide. It’s only an 18 pages guide explaining the values, concepts behind the notion of sprint, the artefacts (product backlog for example), the different events (From daily scrum to retrospective), the roles (Product Owner, Scrum Master, Dev team).
Scrum is really easy to understand but what about its implementation?
The anti-patterns described below are the ones we have observed in our coaching experiences.
The scrum master role is the most misunderstood role. It requires a lot of soft skills (facilitation, communication, empathy) and it’s definitely not the same job as project management.
By not holding a vision it creates a loss of meaning and motivation for the Dev team.
This moment is often lived as a micro-management moment because in most organizations PO and SM are perceived as team managers.
When you work during an entire sprint on a product increment you are proud of and you don’t have the opportunity to demonstrate it and gather feedback by your own, it creates a lot of frustration inside the team.
Often in Dev teams they have impediments related to the technical side (environment issues or technical debt for example). Scrum Masters do not tolerate this kind of discussions during the retrospective, so when can the dev team take time to introspect and adapt on the code base and technical stuff ?
Often self-organization is a sweet dream. A lot of organizations are not ready to trust people.
Developers do not find themselves in this version of agility. They feel that is no longer in their laps.
It’s not the idea’s fault, it’s the implementation.
They all believe in the manifesto for them “it’s common sense” BUT they no longer feel concerned (“It’s for project managers, PMI”).
For those reasons companies need to be more agile. They strongly need to think on ways to re-on-board the developers in agility.
As agile enthusiasts we strongly believe that agile is a good answer to developers past and current problems.
Want to know how to make your developers a part of Agile?