© mahindra satyam 2009 project metrics qms training
TRANSCRIPT
© Mahindra Satyam 2009
Project Metrics QMS Training
2
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Objective
Better Project Planning - data from past projects helps in developing plans
for the new project and in setting realistic goals
Controlling a project's performance - Metrics provide accurate information
about the state of the project and thus can be used to take corrective actions
in a timely manner
Analyzing and improving organization processes - metrics measure the
capability of the organization processes, track the changes in capability of
the processes and identify the improvement opportunities
3
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Process
Prepare Metrics Plan
Collect Data
Consolidate and Analyze Data
Implement Corrective Actions
Submit End of Project Data
4
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Identify Measures
Identify Metrics Categories
Identification of Goal Metrics
Identification of Control Metrics
Setting of Goals
Documenting strategy for achieving Goals
Identify process performance models
Prepare Metrics Plan
5
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Inputs for metrics planning are organization baselines & goals, metrics
data from past projects
Generic measurement objectives and related measures are defined at
organization level, projects have to identify and define measures over
and above that, if any
Identify project specific measurement objectives
Identify measures for these objectives
Identify Measures
6
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Metrics are categorized as
Project goal metrics : Project goal metrics indicate the overall
performance level that a project aims to achieve. These are typically
computed at the end of the project
Project control metrics : Project control metrics are used during project
execution to control the performance of goal metrics
Data collection items : These metrics need not have a set goal. But data
needed to compute the metric is collected and the metric is computed
Identify Metrics Categories
7
© Mahindra Satyam 2009 Mahindra Satyam Confidential
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 Effort Variance 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 Effort
Variance goal.
Identify process performance models
8
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Goal metrics are the ones which quantify the project targets. There are
Mahindra Satyam mandated Goal metrics which are defined with
respect to effort, time, quality and, scope. Apart from the Mahindra
Satyam mandated metrics, PL/PM would capture additional metrics
when:
– There are any customer mandated metrics as per the Contract
– Corporate mandate (STARTRAC)
– Customer sets any Improvement targets for any of the project
performance parameters, like productivity improvement, defect
reduction, cycle time reduction, etc
Identification of Goal metrics
9
© Mahindra Satyam 2009 Mahindra Satyam Confidential
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 correlation analysis, relationship
between goal metrics and control metrics are identified.
Identification of Control Metrics
10
© Mahindra Satyam 2009 Mahindra Satyam Confidential
PL/PM shall
– Set the target values 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.
Setting of Goals
11
© Mahindra Satyam 2009 Mahindra Satyam Confidential
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.
Documenting Strategy for achieving goals
12
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Capture data required for computation of metrics (as per the metrics
which are specified in the metrics plan section) in Data Collection Form.
Data sources for these metrics are
– ONTIME for capturing effort
– OPTIMA for capturing schedule
– RESOLVE for capturing defects
– RISK tool for capturing risks.
Collect Data
13
© Mahindra Satyam 2009 Mahindra Satyam Confidential
PL analyzes the project’s metrics and consolidates the analysis results
– For maintenance - bug fixing, maintenance - minor enhancements
and maintenance - production support projects
• at end of every month considering data for all work requests closed in
the entire month
– For development
• at the end of each phase
• at end of each module / iteration / project
Consolidate and Analyze Data
14
© Mahindra Satyam 2009 Mahindra Satyam Confidential
If metrics analysis reveals that certain metric(s) is beyond the expected range,
a causal analysis is conducted to identify the root cause
The root cause analysis is conducted by the entire project team and facilitated
by the PL and QR
Appropriate corrective and preventive actions will be identified
The results of the metrics analysis will be recorded in the Metrics Analysis
Report
Consolidate and Analyze Data
15
© Mahindra Satyam 2009 Mahindra Satyam Confidential
PL sends the collected data and analysis outputs to PM for ratification
– PM also reviews metrics analysis results as part of project reviews
PL submits a copy of the ratified data collection form to the respective QR
– every month by the end of 5th working day of the month for maintenance -
bug fixing, maintenance - minor enhancements and maintenance -
production support projects
– within 5 working days of the scheduled date for data consolidation for all
other projects
QR validates the data and uses it for Unit level metrics analysis
Consolidate and Analyze Data
16
© Mahindra Satyam 2009 Mahindra Satyam Confidential
In case any metrics are operating outside the expected range
– identified corrective and preventive actions will be implemented
– the project's performance will be brought back to be within the set
norms
– the project risks may be revisited at this stage, as appropriate
Implement Corrective Actions
17
© Mahindra Satyam 2009 Mahindra Satyam Confidential
At the end of the project, a final metric analysis has to be done
This compares the project's actual performance against the set goals
In case of deviation outside the norms, a causal analysis has to be done
The consolidated data for complete project and all the metrics analysis
reports are to be submitted to Quality group for use in baselining and
incorporation in the process database
Submit End of Project Data
18
© Mahindra Satyam 2009 Mahindra Satyam Confidential
Better Project Planning - data from past project is used in planning the
new project and in setting realistic goals
Controlling a project's performance - Metrics are used to take corrective
actions in a timely manner
Analyzing and improving organization processes - the capability of the
organization processes is measured using metrics, changes in capability
of the processes are tracked and the improvement opportunities are
identified
Objective Met