Behind the Code: The Hidden Struggles of Software Project Implementation

 Software industry is one of the biggest bets in the current era. Software growth has seen an exponential growth which no other line of business would have seen within a shot span of time. The software industry boasts of a revenue of 698.80 Billion in 2024 and the estimate of 858.10 billion in 2028. The estimated Compound Annual Growth Rate (CAGR) for the Software market during the period from 2022 to 2028 is 5.27%. Investors are gearing up to invest more on IT and ITES industry and the share prices are growing hitting all-time highs during the last few years. People want to work for software companies and lots of colleges are focussing on Computer sciences and Information technology as students are going berserk over IT jobs rather than any other traditional low paying jobs. While we often celebrate successful software development, it’s essential to recognize that not everything is sunshine and rainbows in this domain. The dark side of software is alarming than providing a hope for the future.

Did you know that 66% of Software projects (based on the analysis of 50,000 projects globally) end in partial or total failure  according to the Standish Group’s Annual CHAOS 2020 report? This does not end here, and we can see that there are some more stats which will surprise everyone. Does the size of the company have an impact on the success / failure rate of a software company? Does a large company execute more success stories than the smaller ones? If your answer is yes, perhaps you are wrong. The actual stats say that large companies have a 60% higher failure rate in software projects than small companies.

Any project in any line of business can have delayed delivery as there might be issues which are unearthed during the execution of the projects and unplanned delays because of various factors. Stats specify that approximately 40-50% of software projects are delivered late.

Another important aspect of project management is the cost overruns. Cost overrun is a nightmare to any industry. It reduces the profit margin and in cases lead to losses. What is the point in executing a project and putting so much of effort and getting into a cost overrun that there is no profit at the end of the day? Can you guess the percentage of projects getting into overruns and the percentage by which the costs overrun wrt the planned cost?  52.7% of software projects will cost 189% or more of their original estimates. When the cost overruns by 189 % can any company really make any profit? Can we call such a project as being executed successfully when the cost overrun is 189%? Isn’t this a case of operation success patient dead scenario?

Failures, Overruns, Delays are part of every business. There is no business which has got successful without going through failures.  People learn from failures before they can be successful. This makes it mandatory for us to understand the reason for failure and identify ways to resolve them. This is not possible overnight and might take lots of time. The next question arises as why software has such failure rates. Let’s find reasons why do these failures occur.

Incomplete requirements:

First things first, gathering requirements is one of the most important things for the success of a project. The scope of the project, the expectations of the customer can be identified only if the requirements are complete. Incomplete, open ended, unclear requirements create lots of problem. Nearly 32% of software project failures are due to poor requirements management. We also need to consider that in some cases the requirements keep changing day by day or different requirements come up from different stake holders in the customer organizations. Research says 78% of software projects experience scope creep, which often leads to project failure. The success of the software projects primarily exists in the clarity of the requirements. If this is not complete, the probability of failure is more. Frequently changing requirement does not guarantee success too. It is fine to add more scope as future requirement as the project progresses. But a dynamic, changing, weak requirement is going to impact the success of the software projects.  

Communication gap:

Communication gap is the biggest problem in today’s scenario. The customer feels that they have given complete clarity of the requirements to the business analyst. The business analyst feels that he has understood the requirement and provides a solution which might not satisfy the requirement provided by the customer. The developer interprets in a totally different way and develops a software accordingly. The Business analyst, Subject matter expert or the developer may additionally provide solutions which they feel as a value add or will help the customers but fail to impress them. Even though solutions are approved by the customers, but they do not see the overall picture and solutions are later modified for new scenarios not addressed initially or based on customer requests for usability or simplicity.

The biggest problem of communication is the illusion that communication has taken place. This is where the gap starts building. While it is true that the communication has taken place, has the sender validated the flow of information to the receiver? Even if the communication is successful will it undergo changes later are some of the questions which have to be taken into consideration. The clarity of the requirement by the customer and specifying the expectation along with its KPI play a vital role in software success. Open ended questions, Incomplete answer and assumptions leads to communication gap.

How do we curb these communication issues?

1.      Be Transparent: A successful communication requires both the parties to be completely transparent and discuss with openness. Transparency in the workplace has gained significant attention in recent years, and rightfully so many forward-thinking companies have become more and more concerned with improving transparency. 

2.      Partner within your team: Treat your teammates as your partner in success and failure.  Share your goals and vision. Speak to them freely. Try to understand each other’s attitude and style. Work together, party together. Start communicating.

3.      Simplify your message:  Complex and intricate problems can be broken down into smaller and simpler pieces. Presenting the problem in simplified way will help others to get a better understanding of the problem and will help all to reach to the solution collectively.

4.      Don’t assume, Ask questions: Listen to the answer carefully. Question back. Till the message is received by the recipient in correct form and order, keep the communications rolling.

5.       Accept the Diversity: Accept the fact that there is basic difference between male and female, between Indians and foreigners and between a functional and technical resource. Be patient. Don’t stop communicating.

All these steps may take a lot of time. But if we bridge this gap at inception, we will cross the biggest hurdle in achieving our organizational goal. Good communication gives us large room to grow. Build that human connection. Fill the gap; make the communicating bridge to reach to the end without falling.

Poor Project Management:

Project management success is essential for an organization's survival in the market. Implementing effective project management practices ensures that projects are completed within set timelines and budgets. Any organization experiencing project delays or cost overruns cannot effectively compete in the market. Surprisingly, 47% of unsuccessful projects fail due to inadequate project management. The repercussions of poor project management are significant, with an average of 12% of project budgets being wasted due to mismanagement, counterproductive behaviours, and poor decision-making.

Did you know that over 80% of software project managers admitted they have knowingly shipped a flawed product? It's concerning to note that sometimes stakeholders of the projects fail to consider a win-win scenario. Instead, they focus solely on their internal objectives without considering the objectives of other stakeholders. By fostering transparency and aligning objectives between parties, the likelihood of project success could be greatly increased.

 Effective project management is achievable when the project manager successfully:

·         Manages project goals with clarity, ensuring alignment with organizational priorities.

·         Controls costs by monitoring expenses against the planned budget and optimizing resource allocation.

·         Adheres to schedules through realistic timelines, critical path analysis, and effective communication.

·         Motivates teams by providing leadership, empowerment, and fostering collaboration.

·         Cultivates a positive work environment through culture, conflict resolution, and well-being considerations.

·         Provides active support, addressing obstacles promptly and advocating for the team’s needs.

Successful project management is about people, adaptability, and continuous improvement. 

Lack of Resource planning:

Resource availability and planning is yet another criterion in making a successful software product.  The dynamic need of specific resources at various durations of the project timelines and the nature of entry / exits of employees contribute greatly to  the failure of the software product. Resource planning helps project managers to align projects’ deliverables with available resources. Without it, you can’t really control the project’s delivery, its timeline, and the budget.  Resource planning that’s executed properly and managed carefully will help improve the overall health of the organization. Statistics say that 27% of software projects fail because the organization lacks the necessary resources or capabilities.

Software quality

Software quality is another key KPI which needs to be measured. The quality of the product is very important to determine the success of the project. Higher the quality of the product, higher will be the success rate. It has been found that only 52% of software projects pass the post-release test for quality. This is in line with the software failure rate of 66% specified above. It is also worth noticing that the over 80% of software project managers admitted they have knowingly shipped a flawed product. The reason for bad software quality could range from the resource availability, expertise, experience of the resource to stringent timelines, unachievable deadlines, compromised process, inadequate testing to name a few.

Low user involvement:

Creating an environment where users willingly embrace new software is crucial. Even if the software is delivered on time, meets quality standards, and fulfils requirements, its success hinges on user acceptance. User acceptance refers to the willingness of end-users to adopt and utilize a new system. Despite technical excellence, software remains ineffective if users resist using it. B2C Companies invest heavily in marketing, promotions, and sign-up offers to entice users to try their products. But how many companies invest and  adopt strategies to improve the user involvement to a new software? Change can be challenging, especially when users are accustomed to existing processes. User involvement significantly impacts software project success. Studies suggest that 15.9% of project success can be attributed to user engagement. Companies should actively engage users during development, seek their feedback, and address their concerns. Investing in user training is essential. Users need guidance to navigate new systems effectively. Motivation plays a key role. Companies should inspire users to embrace change and highlight the benefits. Understanding user pain points and resolving them enhances acceptance. Without management backing, user acceptance becomes challenging. Leadership should champion the new system, communicate its advantages, and encourage adoption.

Conclusion:

All of these seem very difficult to implement. Organizations can break the cycle, however. By teaching employees the basics of teamwork, communication, transparency and good management practices, struggling organizations can “educate their way” toward better project management and higher success rates. And successful organizations, for their part, can put in place a culture of sustained success, no matter what the changing business landscape brings.