Acting
People often think that the term 'Agile' refers to the developers on an Agile project. Because it's a method that has a lot of consideration for developers and encourages them to plan and design their code while actually working on it, it's easy to see how this mistake gets made.
However, it's a dangerous mistake, as it's a step towards 'letting the developers do what they want'. We've even heard 'Agile' used to describe a team with no management at all.
Proper Agile demands more discipline from developers than some are comfortable with, at least at first. The term 'Agile' actually refers to the project itself: a properly-run Agile project can change direction very easily as new information comes to light and the customer's requirements change.
This is why Trovo finds Agile to be the best methodology for IT development available currently. We have never worked on a project where the customer's requirements have been fixed and not changed from day one. And until we discovered Agile, every time requirements changed the result was chaos and stress. Agile helps us avoid this.
We have never worked on a project where the customer's requirements have stayed constant. This used to be really irritating, but now we use a method built around changing the plan as new information comes to light we take it in our stride.
Trovo's Technical Director tells the story of how our Agile approach removes the conflict between customers and developers when urgent changes to the plan are required.
How does the Agile approach help produce code that is easy to understand and that runs efficiently but that is not over-polished? How do we ensure the optimal level of effort producing quality systems for our customers?