When you’re trying to deliver software it can feel like the harder you attempt to lock things down, the more issues come to the surface – the further the go-live date drifts. Pressure from the business starts to accumulate along with mild feelings of panic. If your current project is experiencing issues the chances are you’ll recognize one of the following:
- The runaway project. Like a runaway train this project has no end in sight and just too many requirements. It’s running out of control and yet the pressure to deliver it successfully is increasing daily.
- The unstable project. This project seems ready to complete and you’re trying to get it live. Trouble is, there are more and more bugs emerging and the whole thing keeps breaking. Instability issues start gnawing away at your confidence of ever delivering…
- The project with performance issues.SQL Server database issues may be causing deadlocks or scalability problems – or your .NET application has performance issues that are preventing you going live.
- The project with quality issues. It may be little more than a hunch you have that things are not what they should be and the thought of switching to live is starting to cause you sleepless nights.
If you find yourself with any of these problems then here are 3 steps to tackle your issues:
- Don’t pour more resources into a runaway project to get yourself out of trouble. As has been proven many times over, most famously in “The Mythical Man Month” by Fred Brooks, adding more resources to a runaway project will only cause the project to take longer.
- Don’t continue on blindly hoping that it will all sort itself out in the end.
If you’ve got serious problems then doing nothing is not an option. As bad as it is to add more resources it is equally disastrous to let things continue without some form of intervention. Never forget the impact on morale as a project continues on its slow march to death.
- Do seek professional help.
Sometimes the best thing that you can do is bring in expertise from outside the organization. These experts can come in with a fresh set of eyes and unburdened by the politics of the project. Anybody with a long history of software projects will have seen these types of issues before and will almost certainly be able to bring clarity to the problems and to recommend a set of remedial actions.
See on www.pmhut.com
See on Scoop.it