Externalisez le logiciel
Archives pour la catégorie de « exécution »
-->Dans n'importe quel projet de logiciel, le composant de travail de développement de logiciel représente seulement 30% à 50% de tout le coût. Quant à tout le coût, il est emporté par la gestion de projet, l'analyse et la conception, essai, et la préparation auxiliaire d'activités, comme, de gestion et d'environnement. C'est pourquoi les économies sur des projets en mer ne sont pas plus de 15% à 25% de tout le coût de projet. Vous ne trouverez jamais un retour de 100% à 200% sur de tels projets, à moins que le projet ait été bien défini et indiqué, et la conception a été préparée avec des détails. Vous trouverez souvent développement en mer de logiciel l'organisation réclamant de tels retours sur des projets a externalisé à eux. Néanmoins, l'économie de 25% sur votre coût de tout le projet peut être tout à fait une quantité significative.
Pour réaliser le succès dans des projets en mer de développement de logiciel, la partie la plus essentielle est la condition d'un système de communication de sécurité. Il est très important que la communication soit maintenue vivante entre toi et vos associés en mer, de sorte que l'information puisse être échangée et des sujets reliés soient triés. Si cet effort synchronisé n'est pas assuré au début, le succès du projet sera douteux. 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.
