To Code or Not to Code...that is the question

Many organisations are faced with this question when presented with an opportunity to develop a custom solution for a client or specific market. A very simple question supposed to have a very simple answer. However, the journey to this answer is not so clear cut or simple. Some organisations in the business of writing software often find themselves wondering where they went wrong when things start going south.

In a bid to answer this question in a manner that will limit the probability of organisations being shell shocked two months down a failing/stagnant project, there is need to consider the below.

Before you choose to code

1. Do you have the time to undertake the project?

2. Is the stated project duration realistic?

3. Do you have the software developers needed for the project and do they have the required skill set? If not, can they acquire the skills within the project timeline and deliver the highest quality?

4. Do you have a tool/method to easily track progress and time spent on the project?

5. Do you have a central code repository for your developers to work from?

If you can answer yes to all the questions above, you are good to go and can safely choose To Code. If not, the below section is for you. 

If you choose Not To Code, or are unable to code, or choose to outsource or partner, you need to consider the following

1. Do you have a solid contract that will push both you and your partner to perform?

2. Does your chosen partner have the skills required to deliver on the project?

3. Does the partner have a proven track record?

4. Do you have an internal resource/s to support the product once the project is over?

5. Do you have an internal project manager that is able to clearly articulate project requirements to the partner (This is very key if you and your chosen partner speak different first languages)

6. Do you have a method/tool to track progress being done by your partner?

The above is non-exhaustive but can be a good start for what to consider when trying to undertake a software development project as an organisation.