5 Pitfalls to Software Project Failure
Poorly Controlled Scope
Scope is enemy number 1; it is the amorphous blob that threatens to consume and grow until it is an uncontrollable monster, swallowing all of your carefully planned man hours.
Increases in scope are often the result of failure to manage the customer and expectations. In any given project, there are only so many levers that can be used to control the successful delivery and it is up to the skilled project manager or client interface to toggle these levers of team size, timelines, requirements, and so on.
The worst is when growth of scope originates from within the team as it is a form of cancer that only causes teams to compromise on quality to meet timelines promised to the customer. You see, when scope creep originates from the customer, there is a certain expectation that of course, costs will increase or timelines will need to be shifted. After all, they are asking you to do more than was initially agreed upon. But when new scope originates from the team itself, the customer will not readily accept this delay.
The cost of scope increases is often not well accounted for. A change that takes a developer 2 days to make will cause ripples that force test teams to adjust their scripts, documentation teams to update their documents, and possibly trigger expensive regression testing.
Smart teams and leaders will understand that these can be controlled, in many cases, by simply creating a roadmap and understanding that desired features and capabilities that don’t fit into existing timelines can be added to “v.next”.
(Over) Reliance on Manual Effort
To a certain extent, software engineering requires raw manpower to execute large projects that require many hundreds of thousands of lines of code and lots of moving parts.
But within the lifecycle of a project, there are many activities that can be simplified by the use of automation. Teams must judiciously balance the cost and effort of the automation versus the savings gained, but more often than not, even a little bit of automation is better than none. It’s crazy to think that it was once the case that all phone calls were manually routed between parties.
Nowadays, the idea seems crazy! Imagine if the billions of people on this Earth were to rely on the same processes to connect phone calls today!
Testing is a great example where failure to automate creates a bottleneck to progress. It increases the cost of changes and bug fixes because it increases the cost of regression testing. Make the regression testing virtually free and the cost of introducing changes (whether small scope creep for critical bug fixes) is decreased dramatically.
Technologies like Selenium WebDriver and Visual Studio’s built in tooling make it possible to achieve significant gains in productivity when it comes to testing. Don’t let excuses hold your team back.
One skilled test automation engineer is worth her weight in gold!
Poor Communication and Collaboration
Strong and open channels of communication are critical for the success of projects, especially so when some or all of the resources are remote.
The flow of information and feedback from the customer to the design and engineering teams must be swift and clear so that expectations are known and any roadblocks can be communicated back. Engineering teams will often have insights into the challenges and nuances of a customer’s input and it can be dangerous to agree to timelines or make promises without clearly engaging the teams executing the implementation. Ideas that seem simple on paper or in concept can require massive engineering changes or sacrifices to achieve and not properly estimating this work is a common pitfall.
Demarco and Lister’s Peopleware offers excellent insight into how to foster better communication and collaboration between teams.
Often, one of the simplest solutions is to simply talk to each other instead of using emails, chat messages, and worst of all: assumption (“Oh, I thought you already knew that”; we’ve all heard that one before!). Get in front of a whiteboard and draw out ideas, deadlines, goals, and so on. Go out to eat lunch together. Plan team activities that engage everyone. Make sure that everyone is on the same page on a professional level as well as a personal level.
Not Keeping Your Eyes on the Prize
It’s easy for a team to get distracted and lose their focus on the goals of the project and the conditions of victory.
It is therefore critical that teams focus on a goal-oriented approach to the delivery of software projects. This is a mind-set that scales up from daily scrums to weekly reviews and so on. Even a short coffee break can be used to re-orient a wandering team member towards the goal posts. Small, daily victories can help teams build momentum and continuously align towards the long term milestones.
It’s important that individuals and teams know, at any given time, what is expected of them and what the priorities of the project are. This allows individuals to make decisions autonomously and with little managerial overhead as they understand how to align themselves with the goals of the project and team. Clear communication of goals allows any misunderstandings to surface early by pinning expectations to milestones — be they simply daily ones, weekly ones, or project level milestones.
Teams and leaders that are poor at communication and collaboration will often lose their focus on the prize because there is a lack of understanding about shifting goals and priorities; there is a dependence on assumption instead of clearly aligning all parties to a set of well-defined conditions of victory. These anti-leaders will focus on the tasks instead of the goals; it should be the other way around – focus on the goals and derive your tasks from them.
Unwillingness to Compromise
Teams must always be ready to compromise because this is the real world where timelines and successful delivery of usable software matters, but people also have families and life outside of work. Unplanned circumstances arise that challenge the best laid blueprints.
If it is discovered that a feature will negatively impact performance of the system in the current architecture, compromise must be made on either the feature or the timelines to ensure that the desired capability can be delivered as usable software.
If unforeseen circumstances eat into the project timelines, compromise must be made to clearly redefine the scope and conditions of victory.
This is the real-world; man-hours are not unlimited and an unwillingness to compromise when necessary leads to poor quality as a team pushes to make up time.
In many cases, it is a bitter pill to swallow as it may mean telling a customer that a feature must be delayed or built into the next release, but I find that more often than not, openness and clearly communicating these issues as early as reasonable is productive and allows for rational decision making.