Key touch points |
Risks sought to be mitigated |
Mitigation Strategy |
| Planning & Project Management |
Unrealistic estimates & Schedules
Wrong Assumptions & Dependencies |
Risks are measured and tracked on a weekly basis with the client and appropriately mitigated/escalated on occurrence |
| Knowledge Transfer |
Improper understanding of the application & Architecture |
Onsite visit by technical leader or by client representative and/or demos/conference calls/artifacts/email communication to ensure appropriate knowledge transfer takes place |
Configuration Management |
Non matching version control systems and lack of procedures & standards |
Ensure commonality of tool for version control to bridge any gaps which are likely to occur at project initiation stage itself |
| Quality Management |
No code review mechanism
No coding standards given by the client, guidelines and/or follow organization standards
No explicit quality objectives for the given engagement
No mechanism to review customer complaints
Non adherence to best practices and standards to drive quality |
ISO certified processes ensure code reviews, coding standards, quality objectives, best practices are adhered to. External audits help in finding out any discrepancies or blind spots and acts as a trigger for corrective action. |
| Change Management |
Lack of understanding of modified approach and requirements
No structured approach on analyzing the impact
No formal mechanism to Identify dependencies and interrelationships of requirements |
Detailed change management methodology is documented and followed throughout the tenure of the project. |
| Test Management |
Non availability of test bed and test data
Non availability of established testing criteria
No formal tracking to manage the identified bugs to closure with a tool |
Independent testing team to remove bias created by developers on the quality of the product developed. Risks related to test environment, acceptance criteria, defect management are identified during project initiation and tracked to ensure appropriate mitigation is done when the risks occur. |
| Project Communication & Escalation mechanism |
Not identifying structured and unstructured communication
Not identifying established communication mechanism
Non existence of escalation strategy, procedures and responsible personnel
No follow up mechanism on any problem in service in a timely manner |
Communication & escalation mechanism is documented and followed as per project plan articulated at the time of project initiation to avoid communication related risks. |
| Hiring/Attrition |
Not being able to ramp up resources
Attrition |
In-house Just-in-time resourcing engine helps in ramping up resources on need basis and shadow resources are deployed in projects to handle attrition risks. |
