Agile is a very popular word in the technology field, but as often happens when something becomes popular, its original meanings often gets mistaken.
Why using Agile processes
Evolving the process
Capitalizing what we’ll learn about your users and about your market with frequent adaptations to the process.
Transparency makes the process inspectable, allowing you to identify waste and bottlenecks.
Welcoming the inevitable scope changes, instead of rejecting them as not adherent to the plans.
Continuous improvement of the productive process
An agile team focuses first and foremost on the quality perceived by the user, on the user’s experience while using the product, on the satisfaction of the user’s needs and -consequently- on the improvement of the productive process and of the technology at its core.
Over time those values gave form to processes frameworks that put to practice the manifesto’s principles. There are many modern myths, both positive and negative, about those organisational tools, but truth is that in the right contest being agile leads to tangible benefits and to a concrete and measurable increase in quality.
An Agile team
Deliver soon and often
Instead of investing time and resources into the definition of intricate specifics in the hope to guess the needs of your users, it rather deploy as soon as possible and with a higher frequency small improvements of the product and observe how those are accepted, adapting their plans according to that.
A change of plans is a new opportunity, not a problem! The attention doesn’t have to be on “delivering what agreed upon” but on developing a successful product. If this means a change of plans based on new evidence (see previous point) or to an unpredictable event that subverted the scenario, no problem.
Focus on value
Work makes man noble. Or not? In our opinion working doesn’t make a man noble, per se. To reduce waste, maximise the produced value, make the productive process sustainable in order to keep performances high: this is nobilitating..
Adapting to the product needs isn’t enough; the productive process can be constantly improved. Making policies transparent, individuating problems as soon as possible without putting anything under the rug, inspecting periodically the working processes and adapting them in order to reduce waste and enhance the produced value is part of the process, just as it is to write code.