Again, this article is in the spirit of integrating your team so that you can have a lower total cost of ownership utilizing Nearshore resources. In my prior blog I wrote about when to have your initial team start up in requirements. Here we are discussing moving from requirements to the design stages of the project.
What one should keep in mind when this part of the project kicks in is that most of the team that represents your integrated group will not have had any experience with the customer or requirements team. When design starts, there is a fair amount of requirement documentation reading and transition that should occur. The person in charge of the project, most likely the project manager, should go to the location where the Nearshore resources will be located. This will help in understanding any requirements that seem ambiguous and help integrate the team into the project. This is also a good time for the people who were on-site for requirements gathering, to present their findings.
Once the project manger is on-site and the findings have been presented, the team can get to the design stage, in any situation where there is design, architectural review will be critical. This is no different than with a Nearshore team. Work with the team to begin creating the design. Often I see that the tasks shifted to Nearshore will be the ones related to coding, data transferring and manipulation, and reporting type. While the project manager is on-site with the team, this person should establish timelines and expectations based on the project plan, reviewing them and creating an effective bottom up communication plan.
In the communication plan an emphasis on problem assessment, escalation and resolution is paramount; many times people simply won’t speak out when they are stuck. Once this is done, actual pen to paper can happen in the design. Organizationally it is better if you can have a hybrid type of person, being the person who helped build part of the requirements, do the design. Since these breeds are few and far between, it is important to have design review sessions with the team to ensure they aren’t too far off from expectations.
Once the design has been reviewed and is completed with architectural oversight, you will be ready to progress to the code/configuration stage. I would say the biggest problem that I have seen for the Nearshore design stage is simply making sure the customer has approved and agrees on what will be delivered. Since there is an element of distance and unfamiliarity, I will circle back to the importance of the communication plan to identify potential roadblocks.
- Posted by Doug Erb
- On December 12, 2014