Communication Strategy
The teams at RAIT, on-site and offsite are identified at the start of the project. The client forms a team in consultation with RAit. The roles and responsibilities of each of them are defined. The mode of communication with the client is decided at the time of signing the contract. The modes may be telephone, fax, E-mail, Video Conferencing etc or by person whenever required. The frequency, at which the status of the project should be informed to the client, will be mentioned in the contract.
Quality Assurance
A software quality assurance (SQA) team is given the responsibility to frame standards and procedures for achieving software quality and to ensure that each is followed. The SQA group serves as the representative of the client. Formal technical reviews are as effective as testing in uncovering defects in software. The SQA group identifies, documents and keeps a track of the deviations from the process. The noncompliance items are tracked until they are solved. This ensures that deviations are handled according to a documented procedure. If required, some of the QA tools are used to project the quality of the software that is being built. If the SQA group's recommended the analyst follows methods and tools and designer, a high quality output can be expected from them.
Risk Management
Identifying, analyzing and managing risks is known as risk management. This is very important in a project because it provides better control over the project and also provides confidence to tackle problems.
Initially a team is identified (Management + Technical Staff) and the responsibilities are given. The team structure and the responsibilities are documented. Then a project risk table is prepared in which the description about the risks and the factors which influence the risks are mentioned The probability and the impact of each risk is also documented. Once the risks are analyzed, a strategy is prepared to mitigate the risks.
A contingency plan is also prepared by the risk management team, which deals with the steps to be taken when a risk occurs. i.e., when the mitigation efforts have failed.
Configuration Management
Software configuration management (SCM) is an important element of software quality assurance. Its primary responsibility is the control of changes. The job of SCM begins with the commencement of the project and terminates when software is taken out of operation. The SCM aims at improving the ease with which changes can be accommodated and reduces the efforts required implementing the changes.
Project Plan
The objective of Project Planning is to provide a framework that enables the manager to make reasonable estimates of resources, cost and schedule. The RAit Software Project Plan is produced at the culmination of the planning activities. It provides baseline cost and scheduling information that will be used through out the project development.
Before the project planning, a Check - List is answered which contains a review of the contractual agreement, scope of the project and problem identification phases. It enables the planner to take decisions regarding the resources and time allocation for each of the project development phases. The checklist contains questions regarding the scope finalization, problem identification, client requirements in terms of time and output and also the specific standards to be followed during execution.
RAit Scope document provides the outline requirements to enable the task division .It gives an overall idea as to what the project is and a rough estimate of project duration.
RAit Offsite Development Team headed by Project Manager (RA) and Project Manager (Client) consists of the following sub teams in it.
Client
On Site Team
Off Site Team
aboutus
services casestudy
solutions
careers
contactus
