The importance of agile software development

What is agile?

Let's start by understanding what this process is. The first element that makes up agile development is that it is iterative rather than linear. To put it another way it's about making smaller development leaps that can be reviewed and adapted more easily than the, more old-fashioned, linear style of project.

It's also very much about collaboration and connection to the business. Where previously a software team might seem to disappear from view only to return with a less than overwhelming project, the agile approach allows frequent review by the business, so they are always in the loop.

Agile development in its core is a series of build and review cycles. Each cycle takes place over weeks, rather than months and allows for frequent input, testing and, where necessary, changes in approach or direction.

What are the benefits of the agile approach?

The iterative approach we have described above brings, we believe, a number of benefits to both developer and client. Firstly, the constant review cycles allow the team to better cope with any changes to requirements. Learnings can be acted on immediately, rather than in the next project at some point down the line. In particular organisations in fast-paced business areas can use this to their competitive advantage to ensure the final system is still very much relevant to their customer base.

Alongside this it allows for much faster delivery. Minimum viable products can be got to market much quicker using this approach, where each module had been given the time and attention it deserves. The continuous review and testing elements also allow for higher quality of product at the end of the cycle. Feedback is heard much earlier than in more conventional approaches and the order and timetable of module development can be adjusted to take full advantage.

Finally, the other benefit that we would like to highlight is that this approach makes it much easier to manage all stakeholders. Those who are particularly close to any stage of production get their voices heard regularly and this can be seen to make a difference to development right away. Even if they are frustrated at a missed opportunity, they know the next point when their views are sought will be right along, and action can be taken without great delay. Knowing you are getting regular opportunities to view progress, comment and re-direct go a long way to keep the whole team happy.

So why might you choose not to use agile?

As we mentioned right at the start, whilst we are regular users of an agile approach, it isn't right for every project. So what are some of the reasons why you might not want to go down that route?

For a start it generally means that compromises need to be made along the way. Whilst this can sometime be a benefit, if there is a clear vision for how the end product should turn out, frustrations may grow if one module proves to be more difficult than expected and latter requirements need to be revised, or dropped altogether, to prevent missing key deadlines.

Of course, the agile approach can also alleviate some of these potential delays, but only if the business can be fully committed to being involved along the full lifecycle of development. Business stakeholders may simply not have the time to be able to attend regular reviews and, in these cases, making more efficient use of their time by consolidating planning, review and testing makes more sense.

Conclusions

So, in conclusion, if you are fortunate enough to be able to choose your approach, and the business are keen and committed to be involved the whole way through, then agile is for you. If you've had projects that started out well, but by the end the product seemed to have missed the point with no time, or money, left to make a change then you should talk to us about agile and how you can make it work for you and your business.