This is in response to the question I was asked by one of my clients. And I wanted to share it with all of you.
Usually when I start a new mission, first, I meet the management in the entourage of the team, to understand their real expectation, answer their questions and put a framework around this adoption.
Model used
For the adoption of agile practice, Software Craftsmanship or DevOps, I rely on certain models in my approach:
Tuksman model
Source: https://medium.com/unexpected-leadership/forming-storming-norming-and-performing-5d06d021a969
Model ADKAR
Source: https://online.visual-paradigm.com/de/diagrams/templates/adkar/adkar-model/
How to get practice
This approach is diverse from one community to another, because we are dealing with humans and each has a different behavior in relation to a context. But here are the outlines:
- Meeting with the group, presentation and exchange on the methods that we will jointly discuss in the coming months.
- Enter the approaches already in place.
- Apprehend together the agile practices that will go
- Live these approaches, inspect and adapt
- Emerge DevOps and Crafts needs in teams with the ADKAR model
Essentially, we iterate with the ADKAR model from one technique to another. If we push them, without these understanding their meanings, it does not have much value, because once the bringer has turned his back, it is quickly forgotten.
The following practices are mostly brought in parallel to those of agility:
- Continuous Integration, Continuous Delivery
- Pyramid tests, TDD, BDD, TCR, clean code
- Pair Programming, Mob Programming
- Specification by Example, Story Mapping, Event Storming
- Hexagonal architecture, DDD
Then others at the discretion of the community
