Why do so many get
software development wrong?

The simplest way to explain it is this, ‘how long is a piece of string? Ambiguity is the enemy of software development. Failure to properly scope out the project and aims, failure to understand the resources and time requirements and feature creep. All of these elements need to be properly managed for a software development program to succeed. If this is the case, and there are so many software development management philosophies and solutions, then why is it so many go over budget, over time and fail to deliver the promised benefits?

Software failure is the norm, not the exception

After a review of 5,400 IT projects by McKinsey and the BT Centre for Major Program Management at the University of Oxford, they found that the average software projects had a 66% cost overrun and a 33% schedule overrun. They also found the average software project had a 17% benefits shortfall.

The development philosophies, disciplines, and solutions used by the majority of software developers do not deliver a project on time, on budget and to the standards expected. The reason for this is simple. The discipline required to manage a software development project needs to be part of the DNA of the organisation and the people in charge of the process.

Design is a discipline, not a profession

Organisations such as Redgum have such a DNA. They’ve built their own solutions. They’ve built software for clients from a clean sheet. They’ve taken on projects in crisis and brought them to a successful conclusion. They’ve managed countless iterations of projects of the same software solutions. They’ve demonstrated to clients when a solution is worth saving and when it’s more cost effective to start from scratch. All of this is only possible because of the discipline of the team.

Institutional memory, not institutional ignorance

You only need to listen to how the average software developer talks to clients to understand how the sector received its reputation. Instead of empowering clients, they use terms and jargon to keep their clients ignorant to their lack of discipline and business acumen.

Absorbing the learning’s that every project provides

Software developers such as Redgum have a continuous improvement process, where they record the memory of their collective learnings from projects. This drives internal process and systems such as Redprint™ , which is designed to demystify the software development process and remove the ambiguity between parties of differing technical knowledge, with the aim of empowering everyone in the decision-making process and development team.

Informed clients make informed decisions

Redgum knows that ongoing clear communication and properly defined documentation lies at the heart of every successful software development project.

They also believe the more empowered their clients are with valuable insights, the more they are capable of making a decision that leads to exceptional outcomes.