Software de Outsource
Archivo para la categoría de la “puesta en práctica”
-->En cualquier proyecto del software, el componente del trabajo del desarrollo del software representa el solamente 30% a el 50% del coste total. En cuanto al coste total, es quitado por la gerencia de proyecto, análisis y diseño, prueba, y preparación ancilar de las actividades, por ejemplo, de la gerencia y del ambiente. Esta es la razón por la cual los ahorros de coste en proyectos costa afuera no son más el de 15% a los 25% del coste total del proyecto. Usted nunca encontrará una vuelta de 100% a 200% en tales proyectos, a menos que el proyecto haya sido bien definido y especificado, y el diseño se ha elaborado con los detalles. Usted a menudo encontrará desarrollo costa afuera del software la organización que demandaba tales vueltas en proyectos outsourced a ellos. Sin embargo, el ahorro del 25% en su coste del proyecto total puede ser absolutamente una cantidad significativa.
Para alcanzar éxito en proyectos costa afuera del desarrollo del software, la parte más vital es el requisito de un sistema de comunicación de seguridad. Es muy importante que la comunicación está mantenida viva entre usted y sus socios costa afuera, para poder intercambiar la información y las materias relacionadas se clasifiquen hacia fuera. Si este esfuerzo sincronizado no se asegura al principio, el éxito del proyecto será dudoso. 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.
