Is Your Project In A Mess? – Top 5 Solutions To Turn It Around

Keeping a project on track is far from a simple task. The mere act of bringing together a group of individuals with unique thoughts and opinions is bound to introduce a whole mix of problems. So is it really a surprise when projects drift away from best-laid plans?

Recognising and admitting that you have a problem is the first step. Now you need to work to get back on track before it is too late and your project is headed to the dustbin. Let these top tips on how to revive your project, help guide you to success.

1) Do you know what it is you are trying to deliver?

Unless you really know and understand the scope of your project then you can’t say for sure that it actually needs saving. Write yourself a list of requirements, whether that be using a formal requirements management tool, agile user stories or just a list of features. Having a list gives you the means to measure the amount of the project actually completed. Ideally this list is then used to create a bunch of tests that prove you’ve met the needs of the project. After all if you can’t prove something works, then how can you say it’s done?

  Check #1 – if you haven’t got your list then start now

Check #2 – if you don’t have a bunch of tests then stop development and put them in place immediately

2) Do you know what’s been done?

With your feature list in hand, asses what’s been done and what hasn’t. Use your tests to evaluate whether it actually works or not. Just because a developer says it’s done, until you can see it working and passing your tests then it’s not.

  Check #3 – if you don’t know which features have been actually been completed you need to find out now

  Check #4 – ensure that your developers know what they are expected to do to pass the features that remain on your list

3) What can you multi task?

Having established the planned features and exactly where you stand in their completion, you will know how desperate the situation is. It’s now time to get down to solving the problem. Look at your list of requirements, are they like building a house where the foundation must be finished before starting on the wall, or is it possible to develop multiple features at once?

Check #5 – challenge your existing dependencies and break as many connections as possible

4) Are you doing the important stuff?

When projects get into trouble there is a huge temptation to drop all of the things that help drive the quality of a project. This then leads to fire fighting and general panic, and later burnout and still no project finished. It’s imperative to still ensure testing and reviews take place to build a foundation of stable and reliable development.

  Check #6 – don’t fall to the temptation of ‘just write the code’, keep project quality alive and kicking

5) Are you putting a square peg in a round hole?

There is a gut reaction when projects begin to drift to simply throw more bodies at the problem. After all, more people working on a feature will mean it is finished faster. This could not be further from reality. All this will achieve is a mass of useless resources, maybe a fight over the best solution and a waste of time and money. Rather than try to brute force speed through numbers, it may be quicker and more cost effective to ensure that team members are allocated to tasks in areas where they are most productive.

  Check #7 – if you don’t know the capabilities of each of your team members, you should make it your top priority.

  Check #8 – have the capabilities of your team been matched to the development requirements of the remaining features?

More From The Blog

Achieving Software Quality During Implementation

Achieving Software Quality During Implementation

Achieving Software Quality During ImplementationSoftware quality is not something you can introduce to a system during the final moments before a release, nor should it be something to sacrifice simply to increase the speed of development. Rather it should be given...

Do You Know If Your Project Failing?

Do You Know If Your Project Failing?

Do You Know If Your Project Failing?Did you know that a study by IBM found that only 40% of software projects successfully meet schedule, budget or quality targets? Or that a separate study by the Portland Journal found similarly concerning results, with between 65...

Developing A New Desktop Application? Have You Considered…

Developing A New Desktop Application? Have You Considered…

Developing A New Desktop Application? Have You Considered…There is always a great number of things to remember when you embark on a new system development, meaning it can be quite easy to overlook some rather important points. To give yourself some piece of mind take...

Developing A New Web Based System? Have You Considered…

Developing A New Web Based System? Have You Considered…

Developing A Web Based System? Have You Considered…There is always a great number of things to remember when you embark on a new system development, meaning it can be quite easy to overlook some rather important points. To give yourself some piece of mind take a look...

Developing A New Embedded System? Have You Considered…

Developing A New Embedded System? Have You Considered…

Developing A New Embedded System? Have You Considered…There is always a great number of things to remember when you embark on a new system development, meaning it can be quite easy to overlook some rather important points. To give yourself some piece of mind take a...

Why Do You Need Requirements? – 6 Top Reasons

Why Do You Need Requirements? – 6 Top Reasons

Why Do You Need Requirements? - 6 Top ReasonsIt would be impossible to spend more than a month in the world of software development and never encounter requirements to some degree. Almost every project is centred around some form of requirements documentation, and...

The Hazards of Updating Legacy Systems

The Hazards of Updating Legacy Systems

The Hazards of Updating Legacy SystemsThere is, of course, only one real hazard – to fix a bug or make an enhancement and, in so doing, to introduce a new problem.  The problem usually manifests itself in an area far away from where the changes have been made and so...