Agile vs. Traditional software methodologies for successful government IT procurement

Although many people would not agree with me, I personally think that standalone agile methods would not be as successful as the UK Government think they might be, when applied to public sector organisations. In my opinion, in order to successfully tackle the problem and reduce the risk of project failure, a mixture of agile and traditional software methodologies should be put into practice for a number of reasons.

As always happens, large IS projects are exposed to adverse influences, the so called project risks, which may result in delaying the timely completion of the project, increasing the cost or reducing the final quality of the product. Project risks affect all aspects of a software project: the organization, the personnel, the technology etc. and can prevent the intended benefit of the project being realised.

All these different types of risk at which a complex IS project is exposed to, should be taken into account by public sector organisations. Some of these risks can be successfully reduced or even eliminated by using the right software development methodology and it is up to the UK Government to make a decision between agile and traditional methods, or as I suggest, a mixture of both.

Read More…

 Scroll to top