More clients are asking us to run their projects following an agile methodology. In 2012 37% of tracked projects within the Commodities and Capital Markets practices were agile – compared with just 1 project in 2011. Why this change and what are the benefits/pitfalls of moving to an agile development process?Regardless of how a software development project is run… quality, time and cost are always the key fundamentals.

Large Financial institutions typically wish to closely track cost, especially in an industry with a high IT spend and immovable deadlines. The adoption of agile within these organisations has taken time as the organisations moved away from the upfront ‘certainty’ that a waterfall project provides backed up by the large testing effort at the end. Regulation and the risk of something going wrong reinforce the belief in waterfall.

“The move to agile is often driven by the business experience with RAD & BAU activity”
Within smaller institutions (200 staff or less) the IT teams will be managed or more closely directed by the business. And where IT needs to be reactive to business needs a RAD or agile process will probably already be present. The business perception of these agile projects often drives the methodology change in the larger programmes of work.

Read the whitepaper written by Darren Voisey, Principal Consultant Developer at Excelian here