We staff each project with an integrated, global team that includes the right mix of skills depending on the project needs. Typically, a global team will include project leadership (e.g., Project manager, Architect) both in the US and in China. Our iterative software lifecycle model is architecture-centric and requirements-driven. Therefore, we pay utmost attention to getting both the requirements and the architecture right. To ensure this, we bring the technical leadership of the team to the client location during requirements elicitation and architecture activities to ensure deep understanding of the requirements and the architecture. The technical leadership then transforms this knowledge to the rest of the team offshore. In addition, our US-based project managers travel to China to be with the team during critical junctions in the project. This ensures that the team behaves as a single unit.

Because of our global structure, we can form a team that works seamlessly on a 24-hour basis. The time difference between our locations in the US and China works to our advantage; the end of the working day in the US coincides with the beginning of the following working day in China. Any issues or problems left unsolved by the US-based team at the end of the working day are worked on by the China-based team and resolved before the following morning.

Our global delivery methodology ensures that team members in the US and in China form a cohesive team. We structure a communication plan to ensure open upward and downward communication lines between the client and us; between the design team and the development team; and between the business stakeholders and the development team. The communication plan is developed in the early phases of a project and is signed off by our clients.

Our method includes extensive on-boarding sessions to ensure that each team member understands the business objectives of the software product, the project plan, the requirements, their roles and responsibilities, and the communication plan. We follow that up with regular check-ins, email, instant messaging, conferencing and model-based communications (using a UML-based tool to communicate via models).