Software de Outsource
Arquivo para a categoria da “execução”
-->Em todo o projeto do software, o componente do trabalho do desenvolvimento do software representa somente 30% a 50% do custo total. Quanto para ao custo total, é removido pela gerência de projeto, a análise e o projeto, testar, e preparação subordinada das atividades, como, da gerência e do ambiente. Isto é porque as economias de custo em projetos offshore não são mais de 15% a 25% do custo total do projeto. Você nunca encontrará um retorno de 100% a 200% em tais projetos, a menos que o projeto bem estiver definido e especificado, e o projeto estiver preparado com detalhes. You will often find the desenvolvimento offshore do software a organização que reivindica tais retornos em projetos outsourced a eles. Não obstante, o saving de 25% em seu custo do projeto total pode ser completamente uma quantidade significativa.
Para conseguir o sucesso em projetos offshore do desenvolvimento do software, a parte a mais vital é a exigência de um sistema de comunicação failsafe. É muito importante que a comunicação está mantida viva entre você e seus sócios offshore, de modo que a informação possa ser trocada e as matérias relacionadas sejam classificadas para fora. Se este esforço sincronizado não for assegurado no início, o sucesso do projeto será duvidoso. Your communication strategy needs to be well defined, and such strategies should include communication tools, such as conference calls, video conferencing, wikis, bug tracking, and continuous integration build servers and a source control repository. Here we will have a brief look at some of these tools:
Conference calls/Video Conferencing - There should be a routine conference call set up between your team and the team from your offshore company. In here too a schedule needs to be set up, ensuring that conferences start and end at specified time. The issues discussed should be well documented to be referred to later.
If you have an access to a video conferencing system, it would become a highly desired facility in such scenarios. However, true video conferencing equipment would require high bandwidth, unlike the $100 web cams which are increasingly used for such conferencing. Setting up video conferencing and its operation is costly, and this conferencing could perhaps be scheduled once a week.
Wiki/Whiteboard/RSS - You would need collaborative development effort in any project outsourced offshore. Ideally the “white-board” solution is quite effective in solving different kinds of technical issues. This allows both the parties to work on a common document structure, hence following the same method of representing their status regarding the project.
Continuous Integration and Bug Tracking – You need to a way for all team members to immediately, at any time, know the status of the project from the code perspective. Two ways this can be facilitated is through a continuous integration build server and the implementation and diligent maintenance of bug tracking/automated test results.
Source Control Repository - A document repository is a part of an important tool for providing communication between the onsite and offshore teams. This repository should be accessible by both the teams 24 hours, 7 days a week, remembering that your offshore team will be working when you will have nights. The repository should preferably have a secured access, with each identified members having their own username and password.
You probably noticed the exclusion of email and instant messenger (IM) as tools? Of course, I do not suggest you remove these applications entirely. But offshore software development teams tend to quickly rely on them too much. When information is exchanged across email or IM, the knowledge contained in the communication is buried. Using these tools appears to be a time saver on the surface. However, in the longer term, in the exchange of emails/IM becomes a burden and time waster when attempting to reference previous communication dialog.
