| Project Management |
| |
| We have a robust and skillful project management and execution process. The project management process ensures appropriate communication channel and resource allocation. The project management process accounts for the following at the macro and micro levels: |
- Resource Allocation
- Communication Channel
- Updates and Escalation Process
- Project Execution Process
- Contingency and Disaster Recovery
|
| Resource Allocation: |
| |
| Resource allocation is the first process before a project is initiated. The Delivery Head and Project Manager prepare a resource plan and identify the resources required for a specific project. The resource plan also incorporates the hardware and software, and other support required for the development and execution of the project. A team is allocated for a project based on this resource plan. We consider the following factors while allocating resources: |
- Prior experience of the team members
- Technical skills and attitude
- Work efficiency
- Compatibility and communication skills
- The required hardware and software
- Other support
|
| A team normally comprises of the following members: |
- Project Manager (PM)
- Graphics Leader (GL)
- Subject Matter Expert (SME)
- Technical Consultant (TC), for technical writing
- Test Engineer (TE)
- Team Leader (TL)
- Authors/instructional designers (ID)
- Manager, Quality Assurance (MQA)
- Quality Reviewers (QR)
- Graphics Specialists (GS)
|
|
| Communication Channel: |
| |
| The responsibilities of different members of team, in terms of communication, are as follows: |
| |
- The PM performs all the client interactions, and disseminates the required information down the line. The PM is responsible for handling client interactions and designing the schedule for a project
- The TL is the single point of contact for all communication with the authors and IDs and the PM. The TL is also responsible for assigning the work to the authors and IDs
- MQA is the single point of contact with the PM, TL, and the DH for all quality related matters. The MQA assigns all assignments for reviews to the CAs and QRs. The MQA is also involved in designing the review schedule, and is the single point of contact with all the respective heads of the department for quality matters
- The CTO is responsible for all matters related to TCs and the interaction between the TCs and authors/IDs
- The GL is responsible for assigning the jobs to the GSs and for all interactions with the respective heads of the departments for graphics and visualization matters
|
|
| |
| Updates and Escalation Process: |
| |
Quality Updates
The MQA performs weekly quality feedback session with the TLs, who further disseminate the feedback to the respective authors/IDs or GSs. The MQA can directly interact with a particular author/ID in case of critical matters. A monthly quality audit is also performed and presented to all the members of a team. |
| |
Project Monitoring
The PM monitors the progress of a project on a regular basis. The PM can interact with the TLs, authors/IDs, and other respective heads of the departments in case of any slippage. |
| |
Other Escalation Issues
For all other escalation issues, we follow two processes, the top-down approach and the bottom-up approach. In the top-down approach, the operational head of a department escalates a matter to the respective operational head of the other department, or to the concerned member, as required. In the bottom-up approach, authors, IDs, or GSs can escalate a matter with the operational head of their respective departments, or with the operational head of the concerned department, as required. The two approaches ensure quick turnaround time to address the matter |
 |
| |
| Project Execution Process: |
| |
 |
|
| |
| Contingency and Disaster Recovery: |
| |
| Before staring any project, the PM, DH, GL, and MQA collectively identify the potential areas of slippage and disaster and draft a contingency plan. Based on this contingency plan, potential actions are also derived and approved to resolve the slippage or disaster. The potential actions comprise of the following factors: |
- Identification and response to the causes of slippage and disaster
- Identify the resources to respond to the slippage or disaster
- Drat a plan to repair the foreseen damages caused by the slippage or disaster
- Back up all data at a secure, central location to avoid data loss
- Restore all infrastructure/resources for all unforeseen damages
- Accumulate the damage cost
- Document the entire action plan
|
| In case of unforeseen damages, we have an influential recovery plan, which is revised and updated at regular intervals. This plan encompasses routine data and software backup, and checking for potential threats related to disasters. The disaster recovery team director manages and executes the recovery plan. The following actions are performed in the recovery plan: |
- Identification of the nature and extent of damage caused
- Identify and categorize the types of damage caused
- Identify the source of damage
- Identify and schedule restoration processes
- Implement and monitor the restoration process
|
|
| |
