Linked Knowledge Nuggets: arrow_forward "What is the GQM method?"
personAuthor: Process Fellows
The Goal-Question-Metric (GQM) Method is a structured approach used to define and measure goals in a systematic way, especially in software engineering and quality management.
Summary of the GQM Method:
Goal:
Define a clear and specific objective you want to achieve. This goal should be aligned with business or project needs.
Question:
Formulate questions that help assess whether the goal is being met. These questions explore different aspects of the goal.
Metric:
Identify metrics or data that can answer the questions. These are measurable indicators used to evaluate progress or success.
Simple example:
Goal: Improve software reliability
Question: How often do critical bugs occur in production? The reliability of the software decreases as the number of critical bugs increases.
Metric: Number of critical bugs reported per release during the first 3 months after the release.
Remark: This example illustrates an absolute metric. However, when comparing across different projects or systems, it is often more effective to use derived metrics. For instance, measuring "reliability relative to software complexity"—such as reliability per lines of code (LOC)—enables meaningful comparisons between different software products, regardless of their size or scope.
arrow_forward "What is the difference between a "metric" and a "KPI"?"
personAuthor: Process Fellows
The difference lies mainly in their strategic relevance and purpose.
Metric
A metric is a measurable value used to quantify a specific aspect and then typically used to track and monitor this aspect. For example metrics can be process / activity oriented, or they can be used to measure a product characteristic. Metrics provide data and help you understand what is happening.
They can be operational, tactical, or analytical.
Not every metric is critical for strategic success.
Metrics answer the question: “What is going on?”
Examples of metrics:
Website visits
Number of support tickets
Production cycle time
Employee training hours
SW defect density (#defects/ #lines of code)
KPI (Key Performance Indicator)
A KPI is a specific type of metric that is directly linked to a strategic objective. KPIs measure how effectively an organization is achieving its key business goals.
All KPIs are metrics.
Not all metrics are KPIs.
KPIs answer the question: “Are we achieving our strategic goals?”
Example
Imagine a company whose strategic goal is to increase customer satisfaction.
Metric: Average response time of customer support
Metric: Number of resolved tickets
KPI: Customer Satisfaction Score (CSAT) with a target of 90%
Why?
The response time and resolved tickets are useful metrics. However, the CSAT score is the KPI because it directly measures whether the strategic objective (improving customer satisfaction) is being achieved.
Simple Summary Metric = Any measurable value KPI = A strategically important metric tied to a business goal
In short: A KPI is a metric that matters most.
# PROCESS PURPOSE
The purpose is to collect and analyze data relating to the development results and processes implemented within the organization and its (Project = Endeavor with defined start and finish dates undertaken to create a product or service in accordance with specified resources requirements.), to support an effective management of the processes.
# PROCESS OUTCOMES
O1
The (Measurement = The activity to find the size, quantity or degree of something.) (Information need = The need for characterizing process or product related effectiveness and efficiency (used by MAN.6 and PA 4.1).) that are necessary to evaluate the achievement of process objectives and the achievement of desired work products are identified.
O2
An appropriate set of (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.), driven by the (Information need = The need for characterizing process or product related effectiveness and efficiency (used by MAN.6 and PA 4.1).), are identified and/or developed.
O3 (Measurement = The activity to find the size, quantity or degree of something.) activities are identified and performed.
O4
The required (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) are collected, stored, analyzed, and the results interpreted.
O5 (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) are used to support decisions and provide an objective basis for communication.
# BASE PRACTICES
BP1
Identify the information needs. (
O1 )
Identify the (Measurement = The activity to find the size, quantity or degree of something.) (Information need = The need for characterizing process or product related effectiveness and efficiency (used by MAN.6 and PA 4.1).) that are necessary to evaluate the achievement of process objectives and work products. Note 1: (Information need = The need for characterizing process or product related effectiveness and efficiency (used by MAN.6 and PA 4.1).) may change over time. Therefore, the (Measurement = The activity to find the size, quantity or degree of something.) process may be used in an iterative way. Note 2: The (Information need = The need for characterizing process or product related effectiveness and efficiency (used by MAN.6 and PA 4.1).) should be aligned with the stakeholders and decision makers.
BP2
Specify metrics. (
O2, O3 )
Identify and develop an appropriate set of (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) based on the (Measurement = The activity to find the size, quantity or degree of something.) (Information need = The need for characterizing process or product related effectiveness and efficiency (used by MAN.6 and PA 4.1).). Note 3: (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) may be related to processes or development results.
BP3
Collect and store the metrics. (
O3, O4 )
Collect and store both base and derived (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.), including any context information necessary to verify and understand the (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.). Note 4: Base (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) in the context of this process are directly gathered (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) like “number of defects found” or “number of lines of code”, where derived (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) are two or more (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) that are brought in relation to each other like “number of defects found per line of code”.
BP4
Analyze the collected metrics. (
O4, O5 )
Analyze, interpret and review the measured values to support decision-making.
BP5
Communicate the analysis results. (
O5 )
Communicate the analysis results to all affected parties.
BP6
Use metrics for decision-making. (
O5 )
Make accessible and use information from the collected (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) and analysis results for any decision-making process for which it is relevant.
# OUTPUT INFORMATION ITEMS
15-51
Analysis results (
O1, O4, O5 )
Results of analysis of an object or (Task = A definition, but not the execution, of a coherent set of atomic actions.).Identifies:
Object under analysis
Analysis criteria
Selection criteria or prioritization scheme
Decision criteria
Quality criteria
Includes:
Decisions and selections performed
Assumptions and constraints
Evaluation criteria, for example correctness, completeness or consistency to a work product
Examples and references:
Verifiability analysis results, for example when a test machine becomes defective
Results of a feasibility analysis
Used by these processes:
ACQ.4 Supplier Monitoring
HWE.1 Hardware Requirements Analysis
HWE.2 Hardware Design
MAN.5 Risk Management
MAN.6 Measurement
MLE.1 Machine Learning Requirements Analysis
MLE.2 Machine Learning Architecture
PIM.3 Process Improvement
SWE.1 Software Requirements Analysis
SWE.2 Software Architectural Design
SYS.1 Requirements Elicitation
SYS.2 System Requirements Analysis
SYS.3 System Architectural Design
03-03
Benchmarking data (
O4, O5 )
Data resulting out of performance (Measurement = The activity to find the size, quantity or degree of something.) to establish a comparison of performance values.Identifies:
(Measurement = The activity to find the size, quantity or degree of something.) of current performance
Historical and current values
Criteria and information to be benchmarked
Includes:
References to (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.)
References to their purpose, for example: goals, process, product or involved market
Used by these processes:
MAN.6 Measurement
03-04
Customer satisfaction data (
O4, O5 )
Active and passive feedback information of a customer.Identifies:
Related products and services
Mechanism to collect data, for example field performance, survey, interview, meeting minutes, product demo
Includes:
Notes
Observations
Trend data
Opportunities
Level of customer satisfaction
Used by these processes:
MAN.6 Measurement
07-51
Measurement result (
O3, O4, O5 )
Outcome of gathering qualitative or quantitative data.Identifies:
Data sources
Data ownership
Evaluation and (Measurement = The activity to find the size, quantity or degree of something.) workflow
Conformity requirements, for example on data protection
(Approval = Written statement that a deliverable is fit for its intended use, compliant with defined criteria.) and acceptance criteria
Includes:
Benchmarking needs
Copyright
(Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) references, for example to process, (Project = Endeavor with defined start and finish dates undertaken to create a product or service in accordance with specified resources requirements.) or quality (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.)
Examples and References:
Quality (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) could be identified in survey of the end customer, for example for usability, reliability efficiency.
Field failure (Measurement = The activity to find the size, quantity or degree of something.) for performance of 5D cycle time.
(Project = Endeavor with defined start and finish dates undertaken to create a product or service in accordance with specified resources requirements.) (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) for (Project = Endeavor with defined start and finish dates undertaken to create a product or service in accordance with specified resources requirements.) management, for example resource utilization against plan.
Used by these processes:
MAN.6 Measurement
03-06
Process performance information (
O4, O5 )
(Measurement = The activity to find the size, quantity or degree of something.) about quantitative or qualitative measurable indicators, that match information for performance evaluation.Identifies:
(Measurement = The activity to find the size, quantity or degree of something.) (Metric = A quantitative or qualitative measurable indicator that matches defined information needs.) for the calculation of the quantitatively or qualitatively measurable indicators
Efforts
Time
Data
Includes:
Performance level definition, for example usage of defined capacity, agreements.
Targets definitions, for example throughput
Utilization data of resources, for example up time service outage time
Time schedules
(Task = A definition, but not the execution, of a coherent set of atomic actions.) completion criteria, for example: job run time
Quality of process and work products, for example non conformances ratio
References and Examples:
Process performance respective deliveries, service level, operational performance
MAN.6
Measurement
