Agility is the result of a maturation of software development methods for over 30 years. It feeds on other areas of engineering but also takes into account the specificities of the domain software (immateriality, modularity, technological change, uncertainties ...).

To be effective Agility requires a close combination of management and engineering practices. Far from being an uncoordinated approach, it requires great discipline and a strong commitment of everyone involved.

Migrating Agility involves a real change of mindset, especially in relations between management and teams, and between the client and supplier. It must, for example:

• Agree to start building a solution from an incomplete knowledge and imprecise requirements
• Prefer the simplest implementation possible and then evolve the solution incrementally
• Build on the experience gained to optimize the development process
• Trusting teams to qualify for their full involvement
  

The difficulties of a transition to Agility should not be underestimated, but the potential benefits are particularly important in terms of: the ability to respond to change, cost containment, quality, productivity, motivation and commitment of the teams.