|
|||
| Getting your project delivered by a team which is physically present thousands of miles away is very different from getting it done by an onsite team. Though this might not have sounded much interesting a decade or two ago, today it has been practiced by many with noticeable benefits. Advances in communication technologies and infrastructure combined by ability of project teams to work in a distributed fashion have made this happen with ease. |
|||
Just as body language, eye contact, a firm handshake etc. play important roles in face to face interactions, off-shore software development has its own set of intangible but vitally important factors. Factors that Ramsoft has been able to focus on, improve and inculcate into all our senior Account and Project Managers. Since Ramsoft's focus has always been on off-shore project execution, we have had the opportunity to build skilled Project Managers and fine-tune the various processes and factors in managing such development activities. Offshore projects undertaken by Ramsoft fall under the following major heads - Development, Testing/QA, Migration and Support/Maintenance. The actual model of project execution depends on the clarity of requirements and is mutually agreed upon with the clients. |
|||
Multiple projects can run at the same time at the offshore development centre. The software team for each project gets a dedicated work space to execute the project. We control the access to the project site to adhere to the privacy requirements of our valued clients. Effective project management is the key to success in a remote development model. Once a project starts, we create a detailed project plan with associated risk management and contingency plans. Based on our past experience in offshore software development, we have created a document called PDSP (Projects Defined Software Processes) which covers all the issues that are to be addressed and the items that are to be planned in the project (whether it is development, testing or maintenance work). Our team creates this document with the help from client, for each project. It serves as a guideline throughout the project. Clarity in understanding of requirements is the second key factor in a remote development model. Once any work is initiated, detailed interactions (usually face to face) take place for us to clearly understand what the client wants, and for the client to clearly understand what they are going to get. Our Key business analysts and technical experts visit the client's offices, to discuss, understand and capture the requirements using appropriate methodologies. An understanding of the culture and expectations of the client is also an intangible outcome of this step. Meanwhile, we build the offshore development team at Bangalore. This team undergoes relevant training and orientation. On their return, the team that visited the customer site conducts a functional workshop for the offshore team at Bangalore to disseminate the requirements. Time and again, we involve the clients in the reviews at critical phases, either on-site or offshore. Constant reviews at critical phases ensure consistency, quality and conformance to the requirements. Final implementation also usually involves an onsite visit to properly hand over the software. |
|||
