A Checklist for Managing Offshore Projects

[article]
Member Submitted
  • can pronounce the names of both the team members. The teams have identified and practiced local greetings that should be addressed in conference calls and other communications
  • The teams have a friendly open working relationship with each other, and that they communicate as per the need basis. The communication history is available and documented

Analysis and Design: Checklist
Ensure and provide the evidence:

  • The onsite team has developed the analysis and design documents (business and technical; referred as documents in the following points). The documents are detailed, clear and complete, and have been reviewed and approved by the appropriate stakeholders. The review and approval history is available and documented
  • The documents have been supported by examples, supporting documents and contain exhaustive test cases that verify the completion. The business SMEs have approved the test cases against the business requirements
  • Each document includes a feedback checklist, for the intended recipients (such as offshore developers) to complete, to ensure that the reader has understood the document
  • Each document, that results in a testable deliverable, includes a completion exit checklist, for the intended recipients (such as offshore developers) to complete, to ensure that the recipients knows what he/she needs to deliver in order to make the deliverable 'complete'. The completion exit checklist is such that once completed, it will produce the confirmable, verifiable and testable deliverable/li>
  • The onsite team has developed and published the test plans for the system and the integration tests. The business SMEs have approved the plans against the business requirements
  • The team members have documented questions, any missing information and clarifications on the documents, and sent them to the onsite team
  • The onsite team has addressed all the questions, feedback, assumptions and issues, have accordingly updated the documents. The feedback and update history is available and documented
  • Each document, that results in a testable deliverable, includes the success criteria for performance
  • Documents are available in a secured common area and accessible to the teams
  • The designated reviewers have been assigned–both onsite as well as offshore–against each deliverable. They are the keepers of the completion exit checklist against which each deliverable will be signed-off
  • Project managers have reviewed/revised the project schedule with each team member and that the members have understood the schedule as it relates to their tasks and deliverables
  • The technical and project standards have been reinforced (formal or informal) with an extra emphasis on project standards, communication, escalation and review mechanism
  • QA environment and QA plans have been put in place to test the technical deliverables
  • The detailed inventory of deliverables and assignments–on who will deliver and when–has been posted sparingly in the work place
  • The team members have a friendly open working relationship with each other, and that they communicate as per the need basis. The communication history is available and documented
  • If this is the first project, the onsite SMEs have identified the prototype features that will be developed before the rest of the application

Develop and Test: Checklist
Ensure and provide the evidence:

  • The development team has followed the technical and project standards. This has been demonstrated in delivery of the prototype system.
  • The technical and project standards have been reinforced (formal or informal) with an extra emphasis on technical standards, version control, communication, testing and review mechanism
  • Each team member, from both the onsite and offshore teams, is aware of the schedule and knows the communication hierarchy. The detailed inventory of deliverables and assignments–on who will deliver and when–has been posted sparingly in the work place
  • The team member, responsible for a deliverable, has verified the deliverable against the completion exit checklist before

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Oct 12
Oct 15
Nov 09
Nov 09