Agile development is, at its core, a series of build and review cycles. Each cycle takes place over weeks rather than months, allowing for frequent input, testing and, where necessary, changes in approach or direction. It's iterative rather than linear: 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 everyone stays in the loop.

What are the benefits?

The iterative approach brings a number of benefits to both developer and client. Constant review cycles allow the team to cope better with changes to requirements; learnings can be acted on immediately rather than in the next project down the line. Organisations in fast-paced business areas can use this to their advantage, keeping the final system relevant to their customer base.

It also allows for much faster delivery. Minimum viable products can get to market more quickly, with each module given the attention it deserves. Continuous review and testing allow for higher quality at the end of the cycle, because feedback is heard much earlier than in more conventional approaches.

So why might you choose not to use agile?

Whilst we're regular users of an agile approach, it isn't right for every project. It generally means compromises need to be made along the way, and if there's a clear vision for how the end product should turn out, frustrations may grow if one module proves more difficult than expected and later requirements need to be revised, or dropped, to avoid missing key deadlines.

The approach can alleviate some of this, but only if the business can be fully committed to being involved throughout the lifecycle of development. Business stakeholders may simply not have the time to attend regular reviews, in which case consolidating planning, review and testing can make more sense.

Conclusions

If you're fortunate enough to choose your approach, and the business is keen and committed to being involved the whole way through, agile is for you. If you've had projects that started well but ended up missing the point, with no time or money left to make a change, it's worth talking to us about how you could make agile work for your business.