Digging Software Projects

In Software migration projects like any other kind of project, risks can compromise the project success and must be identified. The difference with a Software development project is the Software is already built, and sometimes the company selected one already to be implemented.

If you are starting a project like this, the following considerations may help you to identify risks.

1.- Substitution causes

You have to know what situations users found that pushed them to make the decision. Some of them can be area processes changes for improvement or functional limitation in the current Software. It’s so important to identify and track these causes because are the ones to be not included again in the new Software.

2.- Software evaluation process

These questions have to be answered: How the evaluation process was made? Was many providers enough? Was there a evaluation committee?  Who was in it? What were the evaluation features? Is there a company with the chosen Software in a production environment already?  These answers can tell you if the new Software was chosen right.

3.- Change management

Any change program can detect users with optimistic point of view and resisters. When users get involved in projects the possibility of success increases.

4.- Expectations & fears

You must interview with end users to identify expectations in terms of functionality and productivity. Identify the nightmares that they don’t want back in the new Software.

It’s important to identify if new features are required by the users that involves a software development project with the provider, internal software development team or with a third party with a outsourcing contract.

5.- Technical & Operational Support

You have to know how and when users will be helped with their issues and questions. So, it’s necessary to know if the company will invest in an internal T&OS department or will the company hire the provider’s service.

After the mentioned considerations are finished, all risks detected must be included in the project risk management plan.  It is our job to show users that we’ll help them to work happy and convince them that we’ll work in the selection of the right tool that increase their productivity.