Upload
ramveer-singh
View
200
Download
0
Tags:
Embed Size (px)
Citation preview
©CyberQ ConsultingPCMM/LEMTRICS/1
SOFTWARE METRICS
Recap…….Process Taxonomy
Strong Moderate Strengths Weak
RA SD Code Test
Project Support Processes
RA SD Code Test
Project Planning
Estimation Configuration Mgt.
Reviews
Organization Process Deployment
Training
Organization Support Processes
Project Line Processes
Risk Management
Project Monitoring
Metrication
©CyberQ ConsultingPCMM/LEMTRICS/3
Why Measure?
Need for measures
©CyberQ ConsultingPCMM/LEMTRICS/4
Exercise
1. Why do we need measures?
_______________________
_______________________
_______________________
_______________________
©CyberQ ConsultingPCMM/LEMTRICS/5
Why Measure?
• If you don’t know where you are going, any road will do - CHINESE PROVERB
• If you don’t know where you are, a map won’t help - WATTS S. HUMPHREY
©CyberQ ConsultingPCMM/LEMTRICS/6
Why Measure?...contd.
• Management implies measures / quantitative control
• Think of all management functions• Measurement has been the Basis of all
Scientific & Engineering progress
What you cannot measure, you cannot manage - DRUCKER
©CyberQ ConsultingPCMM/LEMTRICS/7
Why Measure?...contd.
Do we have the answers to the following:
1. How much did we produce?2. Are our products of high quality?3. Are we improving?4. How well do we compare with other
companies?
Can we really do without measures?
©CyberQ ConsultingPCMM/LEMTRICS/8
Why Measure?...contd.
A management view:
Dashboard • Tells at a glance• When Situation is out of Control• Key Elements to focus on• Understand what they are doing• Know quality and productivity levels
©CyberQ ConsultingPCMM/LEMTRICS/9
Why Measure?...contd.
An engineering view:
Measures help to:
– better understand attributes of software that we have produced
– assess the quality of our product
©CyberQ ConsultingPCMM/LEMTRICS/10
It is not really a question of “Why measure?” but “Why not measure?”
©CyberQ ConsultingPCMM/LEMTRICS/11
However, Management Dilemma
1. Information Overload– Low level data– Too many measures
2. Selecting key indicators:– Quality?– Size? – Progress?
©CyberQ ConsultingPCMM/LEMTRICS/12
But Who Needs Measures?
_______________________
_______________________
_______________________
_______________________
©CyberQ ConsultingPCMM/LEMTRICS/13
Everybody needs Measures• Top Management• Project Managers• Testers• Quality Assurance• Auditors• Marketing • Software developers
Who needs, most of all?
©CyberQ ConsultingPCMM/LEMTRICS/14
Ideal Metrics:
• Simple , Precise, Definable• Objective• Easily Obtainable • Valid • Robust
©CyberQ ConsultingPCMM/LEMTRICS/15
A few examples of metrics
©CyberQ ConsultingPCMM/LEMTRICS/16
Product Metrics
– Measurement of Size• Function Points• Lines of code• Many others..
– Measurement of Quality • Based generally on defects data
©CyberQ ConsultingPCMM/LEMTRICS/17
Defect Metrics
• Life cycle metric
• Extremely valuable for describing product “health” and process improvement opportunities
• Derived from Quality Control activities
• A large no. of such metrics
©CyberQ ConsultingPCMM/LEMTRICS/18
Defect Severity Metric
IBM’s Severity Code:
Severity 1 System inoperableSeverity 2 Major functions
disabled / incorrectSeverity 3 Minor functions
disabled / incorrectSeverity 4 Superficial functions
©CyberQ ConsultingPCMM/LEMTRICS/19
Defect Age
Time from Introduction to Detection
• Can be done in terms of time
• Can also Normalize this Metric
e.g.. Phase Numbers Method
Average Age = Phase (Detected - Introduced)
Number of Defects
©CyberQ ConsultingPCMM/LEMTRICS/20
Defect Density
• Defects per KLOC (Kilo Lines of Code)
• Defects per Function Point
• Defects per module / program
Points to Error Prone Module
©CyberQ ConsultingPCMM/LEMTRICS/21
Defect Removal Efficiency
• Points to QC effectiveness before shipment
• DRE = No. of Defects found prior to delivery/Total No. of Defects
Good companies have DRE > 90%
How do you find Total No.?
©CyberQ ConsultingPCMM/LEMTRICS/22
Process Metrics
Key processes that we will focus on:
• Project Management
• Estimation
• Quality Control
• Quality Assurance
• Configuration Management
©CyberQ ConsultingPCMM/LEMTRICS/23
Project Management Metrics
• Schedule slippage
Completion (Actual - Planned)
No. of planned elapse days • Effort overrun
Effort (Actual - Planned)
Planned effort in mandays• Productivity = Size / Effort
©CyberQ ConsultingPCMM/LEMTRICS/24
Project Management Metrics
Similarly,
• Cost overruns
• Human resource utilisation
• Project Management Effort overrun
• Frequency of major replanning
• Frequency of major adverse impacts to project
©CyberQ ConsultingPCMM/LEMTRICS/25
Estimation Process Metrics
• Changes to size estimates– either FPs or LOCs or others– initial estimate / reestimate– Re estimate with same scope of
work– Re estimate with altered scope
• Changes to effort schedule estimates
©CyberQ ConsultingPCMM/LEMTRICS/26
Customer Satisfaction
• Once in a while activity
• Requires active soliciting
• May be done by other than project personnel
• Impact may go beyond product
©CyberQ ConsultingPCMM/LEMTRICS/27
An Interesting Metric
• Combine Customer Satisfaction and Defect Data
Defects
Customer satisfaction
Something else is wrong
Excellent!
Deep Trouble How do you do it, guys!!
©CyberQ ConsultingPCMM/LEMTRICS/28
REMEMBER!
• WHAT YOU CANNOT MEASURE, YOU CANNOT MANAGE
• STORY OF THE THREE BLIND MEN AND THE ELEPHANT
©CyberQ ConsultingPCMM/LEMTRICS/29
When To Do ?
• Throughout the project
PAs – Measurement and Analysis
Also, OPF / OPD and Engineering PAs
+ PAs at Level 4 and Level 5
Recap…….Process Taxonomy
Strong Moderate Strengths Weak
RA SD Code Test
Project Support Processes
RA SD Code Test
Project Planning
Estimation Configuration Mgt.
Reviews
Organization Process Deployment
Training
Organization Support Processes
Project Line Processes
Risk Management
Project Monitoring
Metrication