project planning qms training. mahindra satyam confidential 2 objective to define a comprehensive...

Project Planning

QMS Training

Mahindra Satyam Confidential 2

Objective

To define a comprehensive plan for the projectTo ensure that the project plan forms the basis for project tracking and monitoring


ProcessSelect Process for the Project

Tailor the QMS

Gather Inputs for Planning

Obtain Deviations

Document Project Plan

Review Project Plan

Approve Project Plan

Communicate the plan

Manage the Project Plan

Execute the projectwith a partial plan

Revise the Project Plan

Plan for Maintenance Work Requests


Select Process for the Project

Based on the project type identified during Project Initiation, PL checks the availability of the relevant process for executionIf the required process is not available in the QMS, PL raises a QMS improvement and informs the Process Management Group (PMG)


Tailor the QMS

PL with the help of QR Identifies the project specific

activities required for executing the project

Arrives at the tailored project specific process based on the tailoring criteria provided in each procedure

Records the tailoring done, if any, in the Project Tailoring Record


Gather Inputs for PlanningPL gathers the inputs required for preparation of the project plan: Scope, acceptance criteria, brief intro of the project,

broad estimates, warranty details Requirements and schedules as agreed upon with

the customer Project specific process including the phases, work

products, quality assurance activities, maintenance of records etc.

Risks as identified during contract review stage Estimates from Proposal stage Reusable data from Project Knowledge Base tool Skills and experience of available project team Measurement objectives


Obtain Deviations

PL obtains concession for QMS Deviation where identified project activities are in a way not defined/recommended in Qualify


Document Project PlanResources

Estimates

Deliverables

Acceptance Criteria

Project Knowledge Base

Work Management Structure

Scheduling and Tracking

Customer Interaction

Roles & Responsibilities

Review Plan

Risks

Skill Requirement & Training

Metrics

Defect Prevention

Configuration Management DAR

Business Continuity Plan

Customer one assessment Plan


Resources

PL documents the required resources in the project plan: Requirement Availability Plan for procurement, in case of shortfall

Resources include Personnel Hardware Software, or Any project specific resource


EstimatesPL revisits the estimates accepted for the project at the contract review stage PL refers to the past data while performing the

estimationIf the PL finds that the project cannot be executed as per the accepted estimates, the project estimates are to be revised In case of any mismatch between the estimates, PL

plans to cover the gap and documents in the Estimates section in the project plan

PL tracks the project estimates during the project execution and revises if required PL revises the project plan whenever there is a

change in project estimates


DeliverablesPL identifies the deliverables for the projectThe deliverables can be Customer Deliverables - Work products to

be generated as part of project execution that need to be delivered to customer for project sign off

Project Deliverables - Work products generated as part of project execution [which include reusable components], but are not requested by customer as deliverables

PL documents these in the Deliverables section of project plan


Acceptance Criteria

Acceptance criteria are the conditions under which the customer will accept the delivered softwareAcceptance criteria clearly identifies and understands what customer considers as acceptable softwarePL documents the acceptance criteria as agreed upon with customer in the Acceptance Criteria section of the project plan


Project Knowledge Base

PL refers to the Project Knowledge Base tool in eSupport for leveraging the experience of other projects to enhance the planning of his/her projectThe Project Knowledge Base containsBest practices Lessons learntSample documents


Work Management Structure

PL identifies the various phases in the life cycle of the project based on the project specific processPL documents these phases, along with the associated inputs, work products, effort estimates and planned schedule in the Work Management Structure of the project plan


Scheduling and Tracking

PL documents the mode of scheduling the project and tracking the project progress in the Scheduling and Tracking section of the project planOPTIMA is recommended for

scheduling and tracking

PL also schedules activities such as Metrics Analysis, Defect Prevention meetings and documents them in the relevant sections


Customer Interaction

PL identifies all modes of customer interactions including periodic formal client feedback and their frequencyTypical modes include telecon /

videocon, status report etc.

PL also identifies the escalation process on both the customer side and Mahindra Satyam


Roles & Responsibilities

PL identifies the responsibilities of the project team, such as SCM, Testing etc.PL documents these in the Organization Structure section of the project planPL also depicts the communication channel between the project team and customer The project team and the support units


Customer One assessment Plan

The customer one assessment shall be planned for the project deliverables. The details of these assessment plan activities along with the roles to perform these activities shall be documented in the Customer One assessment plan section. The applicability of Customer one assessments shall be as per the Customer One Assessment Procedure. PL documents the Customer one assessments planned for the project.


Review Plan

PL plans the reviews or inspections for the work products identified from each of the project execution phasesPL documents these in the Review Plan section of the project plan


Risks

PL revisits the risks identified at the

Contract Review stage identifies potential risksestimates their impact on the project,

and plans for the mitigation and handling

of risks in the risk management tool


Business Continuity Plan

Business continuity planning has to be done for project specific Business continuity requirements Project BCP includes preparation of project

specific Risk mitigation plans for Disasters Disaster recovery plans & Contingency plans

This shall be done in accordance with Mahindra Satyam’s Business Continuity Management System (BCMS)The PL communicates project BCP details to the BCL of the business unit for inclusion in business unit BCP


Skill Requirement & Training

PL arrives at a comparison of the skills required for the project versus the available skills in the team If the skills required are not available in the

team, PL prepares a training plan PL includes the schedule for acquiring the

training in the project plan in the Training Plan section

Maintains detailed schedule for each training separately

Identifies and documents Waivers, if any


MetricsPL documents metrics plan by

Identifying Goal Metrics Goal metrics are the ones which quantify the project targets. There are Mahindra Satyam

mandated Goal metrics which are defined w.r.t effort, time, quality and, scope. Apart from the Mahindra Satyam mandated metrics, project team would capture additional metrics when:

There are any customer mandated metrics as per the Contract Corporate mandate(STARTRAC) Customer sets any Improvement targets for project performance parameters like

productivity improvement, defect reduction, cycle time reduction, etc Identifying Control Metrics

The metrics that affect the performance of goal metrics are called control metrics which would be computed and tracked during the project execution. Based on the statistical co-relation analysis,

relationship between goal metrics and control metrics are identified . Identifying Process performance models

Process performance models help in effective planning thereby help the project to predict the performance of the project. Based on the project goals, project would select the appropriate Process Performance Models available and document the same in the metrics plan. For eg if the project manager wants to monitor the effort variance of the project so as to execute the project with in estimated effort, projects may choose to use the EV process performance model. This model helps the PL/PM determine optimum effort that needs to be planned and to be spent for Project management, Reviews and Testing activities to achieve project EV goal.

Setting target values (Goal, Upper and Lower limits) for Goal and Control metrics The target values are set as per organization baselines/customer targets / corporate mandate.

The goal setting of the same is automated in process performance model sheets which are derived based on statistical analysis.

Documenting the section “Strategy for achieving goals” In case if the goals for any particular metric is stringent (based on contractual

agreement/project FLCB performance targets) than the existing goals at Unit/Organization level, then the strategy for achieving the same needs to be documented in the metrics plan.


Defect Prevention

PLDefines the Defect Prevention

activities for the project Identifies the periodicity of the Defect

prevention meetings and criteria for evaluating the effectiveness of the defect prevention actions in the project

Documents these in the Defect Prevention section of the project plan


Decision Analysis and Resolution

PL Identifies instance where DAR needs

to be implementedSelects the DAR techniqueCompiles the Possible SolutionsApplies the DAR technique


Configuration Management

PL identifies the configuration management aspects to be implemented in the projectidentifies the affected group to whom configuration status should be reporteddocuments in the Configuration Management section of the project plan in detail includes the periodicity of the configuration

status reports


Review Project Plan

PL submits the project plan to QR for inspection/reviewThe project plan goes through an inspection at the time of first preparation and when major changes occur in the plan In case of minor changes, a review

may be sufficient


Review Project Plan

QR identifies the inspection /review team for inspection/review of the project planQR uses the Project Plan Review checklistPL tracks and closes the inspection/review findings In case of any conflict between the PL

and QR during the review, the matter will be escalated to the PM and Head (TQA)


Approve Project Plan

PM approves the project planThis implies that the PM takes the

responsibility for the execution of the project based on the plan

PM ensures that the project plan is inspected, approved and version controlled before the project execution starts


Communicate the Plan

The project plan indicates all the relevant recipients of the plan as audience to the planAfter the approval, the plan is communicated to all the relevant recipients Subsequent major changes to the plan also be communicated to all relevant recipients


Manage the Project Plan

The project plan shall bemanaged and controlled


Execute the Project with a Partial Plan

If all the inputs required for preparing the project plan are not available at the project execution start time, PL prepares a partial plan with available inputs The sections for which relevant information is not

available are tagged as TBDs TBDs will have possible timelines to obtain the

information Partial plan is reviewed, approved for project

execution The TBDs will be cleared as and when possible The review of the plan will be repeated


Revise the Project Plan

If any section of the project plan needs to be revised, PL verifies if any other sections get

impacted and need a revision It is mandatory to re-validate:

Estimates Risk Management Reviews Metrics Defect Prevention Work Management Structure

PL gets the project plan reviewed, approved and version controlled after each revision


Plan for Maintenance Work Requests

The Maintenance projects Will have an over all project plan for the

project Get the work in the form of Work Requests

Work requests with an effort greater than 5 calendar days, will have a Work Request Plan [WRP]For work requests with an effort less than 5-calendar days, WRP is optional the activities for these requests can be

scheduled and tracked using the MS project


Objective Met

A comprehensive plan for the project is documentedThe project plan forms the basis for project tracking and monitoring


Project Tracking and Monitoring

project planning qms training. mahindra satyam confidential 2 objective to define a comprehensive...

Documents

project estimates

project planplan

project tracking

project planexecute

project type

project initiation

project specific activities

identified project activities