Is Agile a fad?
Some are starting to hear about Agile recently and believe that this is a fad as there have been before. The reality is that Agile is about to come of age, in February 2019 it will blow out 18 candles.
Agile was born in 2001, when a group of people linked to software development met to discuss the techniques and processes they used for software development, which were very different from the techniques and processes used by the vast majority, inherited from the industrial stage. At that time, what is known as “agile methods” emerged and the Agile manifesto was created.
While it is true that the Agile manifesto refers to software, as these are its origins, the values and principles it postulates are extensible to any field.
The Agile manifesto is based on 4 sets of values:
Although the elements on the right are valued, the elements on the left are valued more highly. Both groups of elements are valued. This does NOT mean that:
- Teams can at any time decide to return to Waterfall or change the way they work if it affects more teams.
- Not documented
- The client becomes the project manager and is responsible for drawing up the plans.
- Unplanned
Beware of “misinterpretations”.
In addition to the values, there are also the principles contained in the Manifesto. These 12 values are as follows:
Our highest priority is customer satisfaction through early and continuous delivery of valuable software.
We accept that requirements may change, even at late stages of development. Agile processes leverage change to provide competitive advantage to the customer.
We deliver functional software frequently, between two weeks and two months, with preference given to the shortest possible time period.
Business managers and developers work together on a daily basis throughout the project.
Projects are developed around motivated individuals. They must be given the environment and support they need, and entrusted with the execution of the work.
The most efficient and effective method of communicating information to the development team and among its members is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. Promoters, developers and users must be able to maintain a steady pace indefinitely.
Continuous attention to technical excellence and good design improves Agility.
Simplicity, or the art of maximizing the amount of work not done, is essential.
The best architectures, requirements and designs emerge from empowered teams.
At regular intervals the team reflects on how to be more effective and then adjusts and refines its behavior accordingly.
Of the 12 values mentioned above, we can group them into 4 major areas:
- Iterative and incremental value delivery: the focus of Agile is value delivery. This delivery is not done all at once, but is delivered incrementally and iteratively. In other words, we don’t do everything all at once, nor do we try to do everything perfect the first time. We are delivering in parts and adding more and more value.
- Collaboration: Agile cannot exist without collaboration. Collaboration among team members, all together towards a common goal greater than individual objectives. Collaboration with the customer is also essential. The customer is the one who validates our solution, a smooth collaboration will help to produce a better product.
- Adaptability: Agile is an adaptive methodology. It is about being able to respond effectively to business changes.
- Continuous improvement: The idea of Kaizen or continuous improvement is essential to be Agile. We assume that we are discovering better ways of doing our work. We must have mechanisms that allow us to reflect on how we do things and draw up action plans to improve them.
Besides we will find many tools, frameworks or processes to try to be Agile. This is misleading, simply by using a framework or certain tools, if we do not base our practices on the values and principles mentioned above.
The 4 principles above capture the essence of the Agile Manifesto. These can be extrapolated to any team or organization regardless of whether they are in the software business or not.
