is 28 years away. One generation.

Developers who are thirty today will be fifty-eight.

They will probably still have ten years to work. And yet it will be 2052.

According to the European states, if they still exist, we will have achieved
carbon neutrality. If they still exist, because there's nothing to say that tensions
won't split the world as we know it into different zones with very different access
to energy, freedom and knowledge.

But we will also have consumed between 60% and 90% of copper, for example,
and that will have an impact. It's even said that between 2030 and 2040 AI will have
acquired an intelligence comparable to that of men and women, so what about 2052?
Are you preparing for that? Are you thinking about it? Here are a few ideas to
get you thinking about the future of the role of developer.

Do you dare to invite people and not to mandate ? Do you feel the paradoxes of change management ? Everybody is speaking about commitment, engagement. Easy to say, but how can you really try to do it ? Everybody is speaking about change management. 30% are successful since 30 years whatever fields say the figures.

Open (Agile) Adoption, Open Space Agility : let's follow the path of these new approaches. Liminality, storytelling, marketplace, _rite de passage-, stigmergy, during that session we will follow the path of a respectful invitation to change : step by step. At the end you should be able to implement it as a leader, as a facilitator, as a teammate.

Based on the Lego/cynefin workshop (http://areyouagile.com/2013/04/cynefin-et-son-lego-game/, http://www.agile42.com/en/blog/2011/12/25/cynefin-lego-game/), this workshop is about knowing with which system you are dealing with, and what kind of answers you should think about depending on the context.