Logo
Link Devider

Processes - Engineering

The practices in this section pertain to technical issue resolution or research, documentation, dissemination, adoption and certification of new technology skills in the company.

Option Matrix builds Win-Win Relationships with a guarantee of quality on schedule

Overview
The practices in this section pertain to technical issue resolution or research, documentation, dissemination, adoption and certification of new technology skills in the company. There are 6 key process areas and the details are provided below.

    Requirement
  • Requirements Management - This process area is about the step by step tasks required to manage client requirements. The purpose of Requirements Management (REQM) is to manage the requirements of the projects and modules and to identify inconsistencies between those requirements and the project's plans and work products.
  • Requirements Development - This process area is about the step by step tasks required to develop the client requirements, and then develop the project requirements from the client's requirements and to validate the requirements. The purpose of Requirements Development (RD) is to produce and analyze customer, project, and project component requirements.
  • Technical Solution - This process area is about the step by step tasks required to select the project's module solutions, develop the project design and implement the project's development design. The purpose of Technical Solution (TS) is to design, develop, and implement solutions to requirements. Solutions, designs, and implementations encompass projects, project components, and project-related lifecycle processes either singly or in combination as appropriate. The Technical Solution process area is applicable at any level of the project architecture and to every project, module, and project-related lifecycle process.
  • Project Integration - This process area is about the step by step tasks required to prepare for project integration, ensure interface compatibility and integrate the final project. The purpose of Project Integration (PI) is to assemble the project from the modules, ensure that the project, as integrated, functions properly, and deliver the project.
  • Verification
  • Verification - This process area is about the step by step tasks required to prepare for project module verification, perform peer reviews and verify selected modules. The purpose of Verification (VER) is to ensure that selected work products meet their specified requirements. The Verification process area involves the following: verification preparation, verification performance, and identification of corrective action. Verification includes verification of the project and intermediate work products against all selected requirements, including customer, project, and module requirements.

In this section, we have provided details of the engineering control processes carried out by the company during the execution of projects. There is a further objective to hold discussions for ensuring that the company is organized for success and is constantly identifying / implementing opportunities related to continuous incremental / step improvements related to quality, client satisfaction and repeat business. The summary emails in these processes must be copied to Business Leader as well as HR & Accounting Manager. There are the 5 control processes related to project management and the description is provided below:

Half Yearly Performance Appraisal (Mandatory)

Purpose
Business Leader conducts a weekly meeting to identify and resolve any issues or roadblocks faced within any of the active projects

Entry Criteria & Inputs

  • This is a mandatory meeting and must happen every week
  • Quality Manager maintains Issue Resolution Log (Template 25)

List of Activities

  • Business Leader conducts the meeting
  • Agenda and list of participants is decided by Business Leader
  • Quality Manager circulates an email with summary of discussion (Exit Criterion)
  • Quality Manager must highlight and escalate non-compliance to Business Leader if this meeting is not held in a particular week (Verification)

Measures
NUM of times "Weekly Issue Resolution Meeting Not Held during the year"

Outputs

  • Control on Issue Resolution
  • Improvement in Research Process

Weekly Research Review Meeting (Mandatory)

Purpose
Business Leader conducts a weekly meeting to allocate roles and track progress of the research tasks required as per the IPP for any of the active projects

Entry Criteria & Inputs

  • This is a mandatory meeting and must happen every week
  • Quality Manager maintains Research Review Log (Template 26)

List of Activities

  • Business Leader conducts the meeting
  • Agenda and list of participants is decided by Business Leader
  • Quality Manager circulates an email with summary of discussion (Exit Criterion)
  • Quality Manager must highlight and escalate non-compliance to Business Leader if this meeting is not held in a particular week (Verification)

Measures
NUM of times "Weekly Research Review Meeting Not Held during the year"

Outputs

  • Control on Research Process
  • Improvement in Research Process

Weekly Training Review Meeting (Mandatory)

Purpose
HR & Accounting Manager conducts a weekly meeting to identify and resolve the issues or roadblocks faced by any of the MT or ST roles in the company

Entry Criteria & Inputs

  • This is a mandatory meeting and must happen every week
  • Quality Manager maintains Training Review Log (Template 27)

List of Activities

  • HR & Accounting Manager conducts the meeting
  • Agenda and list of participants is decided by HR & Accounting Manager
  • Quality Manager circulates an email with summary of discussion (Exit Criterion)
  • Quality Manager must highlight and escalate non-compliance to Business Leader if this meeting is not held in a particular week (Verification)

Measures
NUM of times "Weekly Training Review Meeting Not Held during the year"
Attrition Rate = Number of Employees who left the company in last one year / Total Number of Employees as on date

Outputs

  • Control on Training Activity
  • Improvement in Recruitment and Training Process

Monthly Library Review Meeting (Mandatory)

Purpose
Project Manager conducts a monthly meeting to identify and implement improvement opportunities related to the creation, maintenance and utilization of the library of code, screen and process artefacts

Entry Criteria & Inputs

  • This is a mandatory meeting and must happen every month
  • Quality Manager maintains Library Review Log (Template 28)

List of Activities

  • HR & Accounting Manager conducts the meeting
  • Agenda and list of participants is decided by HR & Accounting Manager
  • Quality Manager circulates an email with summary of discussion (Exit Criterion)
  • Quality Manager must highlight and escalate non-compliance to Business Leader if this meeting is not held in a particular week (Verification)

Measures
NUM of times "Monthly Library Review Meeting Not Held during the year"

Outputs

  • Control on Knowledge Library
  • Improvement in Knowledge Management

Monthly Technology Adoption Meeting (Mandatory)

Purpose
Business Leader conducts a monthly meeting to manage the process of research, design, dissemination and adoption of new technologies in the business unit

Entry Criteria & Inputs

  • This is a mandatory meeting and must happen every month
  • Idea Log (Template 45)
  • Quality Manager maintains Technology Adoption Log (Template 29)

List of Activities

  • HR & Accounting Manager conducts the meeting
  • Agenda and list of participants is decided by HR & Accounting Manager
  • Quality Manager circulates an email with summary of discussion (Exit Criterion)
  • Quality Manager must highlight and escalate non-compliance to Business Leader if this meeting is not held in a particular week (Verification)

Measures
NUM of times "Weekly Training Review Meeting Not Held during the year"

Outputs

  • Control on Technology Adoption
  • Improvement in New Technology Adoption Process