Emphasize interactions, co-construction
Agile managing is co-constructing while in motion, rather than imposing fixed processes.
A first step in supporting a co-worker or the whole team: having them imagine the future, the project, the next steps:
- What should the co-worker be able to accomplish?
- How will he orient himself at the outset?
- What stages does he anticipate?
- What does he need?
In this way we respect 2 principles of agile management:
▸ Individuals and interactions rather than processes and tools
▸ Give the teams responsibility.
Co-workers would often like to have greater visibility on the medium to long term. How to help them accept that change is an integral part of the project? We start out in a direction which may evolve over the course of time, and that isn't a problem! The problem would be to want to plan everything out and for things to happen as expected.
Agility is adaptability => It's up to the manager to promote a culture of change, to adopt a pedagogy which de-dramatizes uncertainty and modifications in direction, and to progressively make change familiar.
We thereby respect another principle of agile management:
▸ Welcome requests for change positively.
Proceed according to micro-objectives
Micro-objectives foster adaptation in a moving context: we don't confine ourselves in a straitjacket but function rather by short steps, at the end of which we re-evaluate the pertinence of the next phases.
We regularly ask ourselves questions: Is this really what we want, moving forward? Does our recent experience teach us something that we need to take into account?
In this we respect a principle of agile management:
▸ Adjust our behavior and processes at regular intervals in order to be more efficient.