Zoosh Cloud Native Software Development Logo
Zoosh Cloud Native Software Development Logo

Article

Software Development Challenges and How to Reduce Them

Software Development
ERP Migration & Modernisation

The most common software development challenges are time, budget and scope, the team on both sides, and user experience, plus a fifth when you inherit custom code or change partner. None can be removed entirely, but each can be reduced, and in Zoosh Digital's experience the team decides most of it.

Software development projects are big undertakings and for the investment that needs to be made in doing one properly, you would hope the projects would be smooth sailing.

Unfortunately, software development projects are typically time consuming and have a tendency to go over budget. It's safe to assume that the process won't go 100% according to plan and while this unpredictability can be advantageous for innovation, it can make planning ahead a bit of an issue.

If you're wondering what the common pitfalls of software development are and how they can be avoided, then this article is for you.

Why do software projects fail to run to plan?

Software development problems rarely have exotic causes, but overruns are uneven, so averages mislead.

A 2022 peer-reviewed study of 5,392 IT projects found cost overruns follow a power-law distribution, with “a fat tail that includes a smaller number of projects with extreme overruns”. The UK National Audit Office, looking back on 25 years of government digital strategies, found underperformance “often resulting from decisions on technology being taken too early, before the business problem is properly understood.” The study spans IT projects of all types and sizes from firms and US government agencies, and the NAO speaks of UK government, so treat both as a pattern, not your odds.

Time: why schedules slip, and what agile cannot fix

Schedules slip because setbacks arrive after planning, and no method guarantees the date.

One of the most apparent issues that tends to crop up in software development is that of time management. Projects have a tendency to go on beyond the expected timeframe and while this is unavoidable in certain circumstances, having the right team can minimise the frequency of this type of issue.

To an extent, setting realistic expectations and having milestones and deadlines is helpful but unfortunately, errors can pop up and setbacks can occur. The Scrum Guide (November 2020) defines Scrum's Sprints as “fixed length events of one month or less”, each producing an Increment that “must be usable”, so problems tend to surface while they are still small. While an Agile methodology can be helpful, that's not to say that it guarantees a perfect schedule can be kept.

What fits your project depends on which of scope, time and cost your delivery model fixes.

Budget and scope: how growing scope becomes overspend

Budgets tend to overrun when scope grows but time and cost do not: that is scope creep.

As well as going beyond time constraints, software development has a tendency to go over budget and while this too is unavoidable to a degree, it tends to occur due to the scope of the project broadening or shifting. A definition from PMI's PMBOK Guide (2008 edition) calls scope creep “adding features and functionality (project scope) without addressing the effects on time, costs, and resources”, or doing so “without customer approval”.

It is another concern that can be tough to completely remove from the process but hiring an experienced team that are more in tune with the kind of changes that are bound to happen can make preparing for them a lot easier. Zoosh Digital's ERP timeline guidance warns: “A less experienced partner says yes to everything in the sales phase and deals with the consequences during the project.”

A PMI paper by Richard and Elizabeth Larson recommends “a change management process in the Scope Management plan”, and your contract should say which of time, cost and scope may move.

The team, and the owner on your side

An experienced team will see problems coming, as long as someone on your side can decide.

An experienced software development team will be more familiar with the pitfalls that can typically occur and while they won't be able to prevent issues from arising, they will be able to steer the project with a clearer sense of how things are likely to play out. In addition, for any software project you will need someone from your company to oversee the project to improve the chances of success.

Zoosh Digital's ERP guidance sizes that role: “An ERP implementation requires 20 to 30% of a named internal person's time throughout the project.”

User experience: building for the people who use it

Working software is not enough: its users have to review it while it is built.

Getting UX design right is also another key issue in the process. Meeting the user's expectations and needs stretches beyond simply achieving functionality. Achieving an end product that the users can be happy with and provides a good user experience requires the involvement of a UX designer and also requires ensuring that the functionality and presentation are undergoing constant reviews from the end users during the different sprints.

The UK government's Service Manual, written for public services, says: “If you do not understand who they are or what they need from your service, you cannot build the right thing.” That is where a custom build from idea to launch starts.

Software development risks when you inherit code or change partner

Inheriting custom code or changing partner brings four risks: hidden source, blocking extensions, lost knowledge and an unplanned handover. Microsoft Dynamics 365 Business Central is the worked example; the questions apply to any bespoke system.

Source code you cannot see

Microsoft's documentation states: “When you develop an extension, your code is protected against downloading or debugging by default.” Whether you can download it depends on a setting the original developer chose, which is off by default. Who owns the code is a contract question, not a Microsoft one.

Extensions that block updates

Microsoft's update timeline gives each major Business Central update a five-month update period and a one-month grace period; in the enforced period after that, an extension that makes the update fail “might be automatically uninstalled from the environment so that the update succeeds”, though its data “isn't deleted from the environment”. Zoosh Digital's guide to what a bespoke extension commits you to calls each one “a commitment: to maintain it, to test it with each update, to document it, and to explain it to the next partner”.

Knowledge that lives in people's heads

When builders leave, their knowledge can leave too. Zoosh Digital's custom ERP development guide suggests asking any partner, itself included: “Who will be able to maintain this after go-live, and does it depend on the specific people who built it?”

The handover

Before the old partner leaves, secure:

  1. The original project and app ID. Microsoft warns “You won't be able to upgrade from the app with the old id to the app with the new id”, so a rewrite under a new ID starts without that upgrade path.
  2. The source, in a repository you control.
  3. A signed assignment or licence for the code.
  4. A customisation audit, which Zoosh Digital's migration guide says “maps every piece of C/AL code to one of these four outcomes”: rewrite, standard functionality, a marketplace app, or retire.
  5. A written overlap period when both partners can reach the system.

If you are choosing a new Business Central partner, ask who will maintain the code you hand over.

FAQ

What are the most common software development challenges?

The most common software development challenges are time, budget and scope, the team, user experience, and the risks of inheriting custom code or changing partner.

Why do software projects fail?

Software projects tend to go wrong for repeat reasons: scope growing without adjusted time and cost, no client-side owner, and, as the UK National Audit Office found in government, technology chosen before the problem is understood. A 2022 study of 5,392 IT projects found overruns have a fat tail.

What is scope creep?

Scope creep, in a definition from PMI's PMBOK Guide (2008 edition), is “adding features and functionality (project scope) without addressing the effects on time, costs, and resources”, or doing so “without customer approval”.

How do you avoid scope creep in a software project?

You reduce scope creep with a written change management process: a decision-maker on each side, cost and time impact stated before accepting a change, and agreed limits on what may move.

What should you check when you inherit custom code?

When you inherit custom code, check the source is accessible (Business Central protects extension code by default), you hold the original project and app ID, ownership is assigned in writing, and what an audit says to keep.

Conclusion: the team decides most of it

One pattern does emerge from looking at the issues and the reality is that the end result does boil down to the quality of team you choose. Good communication and a clear owner on your side will not remove these issues, but they keep the project running as smoothly as it can.

So if you're looking for a software development project to run as smoothly as possible, an experienced, agile team can deal with most of the issues you can expect to see elsewhere.

Zoosh Digital, a Microsoft Dynamics 365 Business Central implementation and technology partner based in Ireland, provides technical support for bespoke and integrated solutions, including upgrade and release support. Where a new build fits better, it offers bespoke and custom software development.

Talk it through with Zoosh Digital, even if the answer is to replace what you inherited.

Referenced sources