Agile

The term Agile was originally coined to designate a project-oriented software development methodology.

Agile development methods were originally designed for project management processes. For example, eXtreme Programming (XP), Scrum and Feature-Driven Development (FDD) were all originally developed for software development, but are now being extended to all types of project.

They developed in the 1990s, and were popularized in 2001 with the publication of the Agile Manifesto, which grouped all these theories under common Agile principles.

The Agile Manifesto for Software Development

We discover better ways to develop software by doing it and helping others to do it.

Through this work, we have learned to value :

• People and interactions rather than processes and tools.
• Functional software rather than exhaustive documentation.
• Working with customers rather than negotiating contracts.
• Responding to change rather than following a plan.

So, although the elements on the right are valuable, we prefer those on the left.

The 12 Agile principles

1. Fast, continuous delivery of valuable software.
2. Embracing change.
3. Frequent deliveries.
4. Collaboration between business teams and developers.
5. Motivated individuals.
6. Face-to-face communication.
7. Functional software as a key measure of progress.
8. Processes that promote sustainable development.
9. Technical excellence.
10. Simplicity.
11. Self-organizing teams.
12. Regular reflection and adjustments.

These principles completely redefine the historical methodology of software development.

They place the customer and his needs at the heart of the process, thanks to a complete reinvention of the development approach. With the Agile method, software development is no longer linear.

The Agile framework divides the project into cycles (or sprints), at the end of each one a testable version of the project is systematically proposed, which evolves through continuous improvement with each iteration.

In this way, the Agile mindset also establishes interaction and collaboration with customers as a fundamental principle. Feedback is central: it's this feedback on the work of each sprint that helps identify added value and determine which features should be added, developed or abandoned.

These principles of iterative development and close collaboration ensure optimum alignment of the needs of both parties. With iteration cycles lasting just a few weeks at most, these two realities cannot be kept apart for long

This new approach breaks with the old rigid, contractual model, where software development was limited to a single sprint, at the end of which a final version was presented to the customer. The service - designing a customized tool - remains the same, but the process has been completely reinvented.

The Agile model generally promotes disciplined project management that encourages frequent inspection and adaptation, as well as a leadership philosophy focused on teamwork, self-organization and accountability.