3 things to understand before
outsourcing software development

Outsouring is now easier than ever with numerous web sites and marketplace to describe the requirements. Once the decision is made to outsource a project, a proper execution plan is to be followed to make the project a success. So, here are some few tips to be followed during execution of the project.

1. Frequent but short discussions

A basic activity of spending just atleast 10-15 minutes discussing with the development team either once or twice a week will have a great impact in the completion of project. This would make the client to understand the direction in which the development team is moving and quickly correct any devaitions at an early stage. Last minute surprises and frustrations can be avoided by simply following this. Also, for the development team, they would understand the requirements better and this would reduce the gap between the software features and user's requirements.

2. Changes in requirements during later stages are expensive

During the start of the project, project is at early stage and it is like drawing on an empty sheet, so it is very easy and flexible for the developer make any changes. Also, the developer will have a good understanding and control over the code. Any changes would very easily be done by the developer. However, as more and more functions are added, the code becomes more complex. Any changes done to the code at a later stage of project have a good chance of affecting other areas of the code and break the functionality. This chance of break-down is more after more code is added to the project. Therefore, the developer will not have the freedom of code change that he/she had during the early phase of the project. This greatly makes the changes become expensive at later stage of the project.

The graph indicates the effort needed to make changes increase over time.

3. Simple Tools (like plantUML) for communicating design

Clear communication of the required design is very essential. Especially, the various components involved and interaction among the components should be well communicated between the teams and clients. At the same time, drawing a diagram is easier but maintaining or changing it will be a difficult task. However, plantuml is an amazing tool which auto generates the diagram based on the text content. Since the core elements are textual content, maintaing the texts are easier than the bitmap images. Though some time needs to invested to understand this language but definitely will pay off in the long-run. This will make the communication of the design undoubtedly smoother

Thanks for reading till now :-) So let me share two more bonus points for outsouring

Bonus 1. Using your product everyday

Regular usage of the product will give various insights about the product. as a user, you can witness flaws, issues, usability and many more. You will be able understand the user's painpoints in doing so. Regular usage also builds up a lot of confidence in your product. Also, if it used by the entire team then you get more insights and confidence in the product

Bonus 2. Cumulative-feature testing via Usage

Assume that if you want to use feature C of a product then you have to use feature A and feature B. In other words, you have to use feature A & B only then you can reach feature C and use it. This way when you test feature C then you have to test feature A & B. This knowledge will make you plan the features of application better to accomodate the features

I would love to hear more about your ideas on some good outsourcing tips