Professional Documents
Culture Documents
C-40, Sector 59
Noida 201 307
(U.P.), India
http://www.rsystems.com/
Quantitative Project
Management
Document Id.: Qproc044A
This document of R Systems International Ltd. is for internal circulation. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means – recording,
photocopying, electronics and mechanical without prior written permission of R Systems International Ltd.
DOCUMENT CONTROL SHEET
Document History
Ver. Release DCR Description of Change Authore Review Approve
No. Date Ref d/ ed By d By
Revised
By
1.0 17/12/10 DCR Release Version Prabhas Metrics NK Garg
/318 Dash Council
2.0 01/02/11 DCR Updated to include Sanjay Prabhas NK Garg
/323 Quantitative Project Rana Dash
Management flowchart
and modified section
“Tasks” and name
changed to “Quantitative
Project Management”
2.1 28/08/12 DCR Reclassification of QMS QA SEPG NK Garg
/351 documents- changed from Group
‘restricted’ to ‘internal’
2.2 16/01/13 DCR Updated References to QA SEPG NK Garg
/356 include Agile Goal Group
Tracking Sheet
2.3 16/12/13 DCR Updated Section 7.7 to QA SEPG NK Garg
/371 elaborate composition Group
2.4 01/01/14 DCR RSI Logo Updated QA SEPG NK Garg
/373 Group
2.5 03/10/16 DCR Reviewed as per ISO QA SEPG NK Garg
/390 9001:2015 requirements Group
and Risk Matrix (Section 6)
added.
2.5 03/10/16 NA Yearly review on 10/11/17 QA SEPG NA
and no changes made Group
2.5 03/10/16 NA Yearly review on 03/12/18 QA SEPG NA
and no changes made Group
Notes:
Only controlled hardcopies of the document shall have signatures on them.
This is an internal document. Unauthorized access or copying is prohibited.
Uncontrolled when printed unless signed by approving authority.
1 Purpose ....................................................................................................................................... 4
2 Scope .......................................................................................................................................... 4
3 Acronyms and Definitions ............................................................................................................ 4
3.1 Acronyms ............................................................................................................................ 4
3.2 Definitions............................................................................................................................ 4
4 References .................................................................................................................................. 5
5 Responsibilities............................................................................................................................ 6
6 Risk Matrix................................................................................................................................... 6
7 Entry Criteria ............................................................................................................................... 6
8 Inputs .......................................................................................................................................... 7
9 Tasks........................................................................................................................................... 8
9.1 Set a Goal for the Project Objectives ................................................................................... 9
9.2 Select or Build a PPM .......................................................................................................... 9
9.3 Run the POS for the Y metric (For the project having historical data for Y) .......................... 9
9.4 Select Applicable Processes, Sub-processes and suitable Metrics ...................................... 9
9.5 Identify critical sub-process................................................................................................ 10
9.6 Set Goal for the Critical Sub-processes ............................................................................. 10
9.7 Compose the Sub-process ................................................................................................ 10
9.8 Monitor the Sub-process using XmR chart......................................................................... 11
9.9 Perform CAR ..................................................................................................................... 11
9.10 Validate/Calibrate PPM...................................................................................................... 11
10 Exit Criteria ................................................................................................................................ 11
11 Measurements ........................................................................................................................... 11
12 Outputs ...................................................................................................................................... 11
©R Systems International Limited. Internal Quantitative Project Management
1 Purpose
2 Scope
3.1 Acronyms
Abbreviation Description
ANOVA Analysis of Variance
CSAT Customer Satisfaction
GQM Goal Question Metric
LSL Lower Specification Limit
MC Metrics Council
PCB /MBR Process Capability Baseline/Metrics Baseline Report
PPM Process Performance Model
RSI R Systems International Ltd.
SD Standard Deviation
SEPG Software Engineering Process Group
SPC Statistical process Control
USL Upper Specification Limit
3.2 Definitions
Process
A set of activities performed to achieve a given purpose.
Sub Process
A process that is part of a larger process. A sub-process can be decomposed into
sub processes and/or process elements.
Process Elements
The fundamental unit of a process. A process can be defined in terms of sub
processes or process elements. A sub process can be further decomposed into sub
processes or process elements; a process element cannot. (See also “process” and
“sub process.”)
Each process element covers a closely related set of activities (e.g., estimating
element and peer review element). Process elements can be portrayed using
templates to be completed, abstractions to be refined, or descriptions to be modified
or used. A process element can be an activity or task.
PPM
PPM stands for Process Performance Model. It is a statistical model that can be
used to statistically monitor and control the corresponding process. It provides insight
into the effect of process changes on process capability and performance .It can also
provide a basis for analyzing possible effects of changes to controllable and non-
controllable process elements
Controllable
“Controllable” implies that a project has direct or indirect influence over the factor
prior to or during the project execution. Controllable can be factors that can be
selected or changed for a given project and controlled by Project Manager during
planning and execution of the projects – (i.e. - Competency skills & Average
experience of resources, Review & testing Efforts etc.)
Un-Controllable
“Uncontrollable” implies that a project has no direct or indirect influence over the
factor prior to or during the project execution. In can include factors that are
unchanging for a given project but can be changed for future projects (i.e. - Project
Size, Requirement Volatility etc.)
4 References
5 Responsibilities
The responsible authorities for identifying, process /sub-process, building process
performance model at organization and account /project level with respect to business
needs are indicated below:
S. No. Task Responsibility
1 Identify Project goals PM
2 Prepare PPM at the Project Level/Adopt Org level MC along with PM
PPM
3 Do What if Analysis PM
4 Validate Project PPM PM
5 Validate/Calibrate Project PPM MC along with PM
6 Risk Matrix
7 Entry Criteria
8 Inputs
Organization goals
Customer objectives
Metrics Procedure
Project database repository/Measurement Data
Metrics Baseline Reports
9 Tasks
No
Yes
CAR Report
DECOMPOSE THE SUB-PROCESS No Is Sub-Process Capable?
Yes
Look for clients input (an objective and a goal for it).
Look for Organizational current performance baseline at Organizational level.
If the project has historical data, consider those.
PM can decide a new objective and a goal for it if the project type is new.
Neither customer has provided any input nor does the organization have a
suitable objective and a goal for that.
Case I: If the project does not have historical data, adopt the Organization
PPM as Project PPM for the chosen objective. The Organizational PPM is
calibrated for the Probability of Success (POS) greater than the defined
threshold limit. The threshold limit for POS has been defined at 80%.
Case II: If the project has historical data, and the organization PPM is not
appropriate for the project, then the PM may build project level PPM by taking
help from Metrics Council.
9.3 Run the POS for the Y metric (For the project having historical data for Y)
If the project has at least 5 historical data points for Y, run the POS for the Y
metric and if it is above the organization threshold of 80% then select the critical
sub process and keep statistically monitoring the chosen sub process.
controllable in nature
critical in nature
early in the lifecycle
sensitivity of the parameter or the coefficient of the sub process in the PPM
Case, if the project has historical data then it is assumed that the project will
use its historical data for setting the goal for the critical sub-process. First of
all, POS will be checked using the project’s historical data.
If the POS>80% (Organizational threshold limit), then the project will take
the control limits of the project’s historical data and set the goal. The goal
can be set tighter from the past performance also. The reason for setting
tighter goal should be documented.
The specification limits for the critical sub process will be set with best fit
values resulted from the What-if analysis, with regards to the specification
limits of the Y.
While composing the sub process, the method wise performance should be used
for different sub processes. For e.g. If the composition of code review sub process
is done and there are three baselines available for code review efforts, one with
peer review, second one with group review and third one with peer plus group
review, while doing composition project has to select one of these baselines and
do simulation to see the predictability of achieving objectives.
PM tracks and compares predictions from PPM with project actual results to
validate and if required to calibrate the process-performance models. (run paired-t
test or sample t test). POS can also be used to validate the PPMs at regular
intervals, data outputs from POS run should be recorded in the projects. PPMs
shall be recalibrated (i.e. same variables with different data) or remodelled (new
variables, modified/deleted existing variables and data), if
10 Exit Criteria
QPM implemented
11 Measurements
12 Outputs
PPMs
What if results
Actions based on What if
PPM calibration and validation reports