소프트웨어를 외부에서 조달하십시오
"실시" 종류를 위한 기록 보관소
-->어떤 소프트웨어 프로젝트든지에서는, 소프트웨어 개발 노동 분대는 단지 30%에서 총경비의 50%를 대표한다. 총경비에 관해서는, 프로젝트 관리에 의해, 분석 및 디자인, 및 보조 활동과 같은 관리 시험 및 환경 준비 날라진다. 이런 이유로 근해 프로젝트에 경비 절약은 15% 이상 총 프로젝트 비용의 25%가 아니다. 당신은 결코 프로젝트가 분명하 지정하는 이고, 디자인이 세부사항으로 준비되면 않는 한, 100%년에서 그런 프로젝트에 200%년의 반환을 찾아내지 않을 것이다. 당신은 수시로 찾아낼 것이다 근해 소프트웨어 개발 프로젝트에 그런 반환을 요구하는 조직은 그들에 외부에서 조달했다. 역시, 총 프로젝트의 당신의 비용에 25% 저축은 확실히 상당수일 수 있다.
근해 소프트웨어 개발 프로젝트에 있는 성공을 달성하는, 생명 부분은 안전 장치 통신망의 필요조건이다. 정보가 교환될 수 있고 관련 사정이 분류된다 그래야 커뮤니케이션이 당신과 당신의 근해 협동자 사이 살아 있는 유지된다 아주 중요하다. 이 동기화된 노력이 우선 지켜지지 않는 경우에, 프로젝트의 성공은 의심스러울 것이다. 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.
