Measurement

Quantitatively evaluating the software against benchmarks along some defined dimension.

Also Known As

• Analysis
• Burndown Chart (in Scrum)
• Definition of Done (in Scrum)
• Empirical Process Control (in Lean Software Development)
• Flow Metrics (in Scaled Agile Framework (SAFe))
• Flow Metrics (in TameFlow)
• Metrics
• Performance Measurement
• PI Objectives (in Scaled Agile Framework (SAFe))
• Predictability Measure (in Scaled Agile Framework (SAFe))
• Throughput Accounting (in TameFlow)

Related

• Monitoring
• Estimation
• Code Reviews

Addresses / Mitigates

• Operational Risk: Provides data to inform decision-making and improve operational efficiency.
• Feature Fit Risk: Helps in understanding the use of the system.
• Implementation Risk: Identifies areas of improvement in the implementation process.

Attendant Risks

• Funding Risk: Implementing measurement systems can be expensive.
• Reliability Risk: Creates dependencies on measurement tools and their accuracy.
• Complexity Risk: Collecting and analyzing data can add to the complexity of the project.
• Internal Model Risk: Focusing on the wrong measures can blind you to what's important.

Used By

• Lean Software Development: Lean uses empirical data to understand and improve the development process.
• Scaled Agile Framework (SAFe): SAFe measures progress through PI Objectives, velocity, and flow metrics.
• Scrum: Scrum uses various metrics like burndown charts to measure progress.
• TameFlow: TameFlow uses flow metrics like throughput, cycle time, and buffer consumption to measure performance.

Description

"Software measurement is a quantifiable indication of some aspect of a software product, process, or project." - Software measurement, Wikipedia

Measurement in software development involves collecting and analyzing data to evaluate various aspects of the software or development process. This practice helps in making informed decisions, identifying areas for improvement, and ensuring that the project meets its goals and objectives.

Variations

Measurement Type	Description	Reference
Code Coverage	Measuring the percentage of code exercised by tests.	Code Coverage, Wikipedia
Velocity	Measuring the amount of work completed per iteration.	Velocity, Wikipedia
Cycle Time	Measuring the time from work starting to completion.	Cycle Time, Wikipedia

Used By

Lean Software Development

An Agile software development methodology that emphasizes eliminating waste, building quality in, creating knowledge, deferring commitment, delivering fast, respecting people, and optimizing the whole.

Why: Lean uses empirical data to understand and improve the development process.

Uses:

• Empirical Process Control

Scaled Agile Framework (SAFe)

A set of organization and workflow patterns for scaling lean and agile practices across large enterprises.

Why: SAFe measures progress through PI Objectives, velocity, and flow metrics.

Uses:

• PI Objectives
• Flow Metrics
• Predictability Measure

Scrum

An Agile framework for managing and completing complex projects.

Why: Scrum uses various metrics like burndown charts to measure progress.

Uses:

• Burndown Chart
• Definition of Done

TameFlow

A management approach for knowledge work that integrates Theory of Constraints, Kanban, and Agile principles to optimize the flow of work, information, and value.

Why: TameFlow uses flow metrics like throughput, cycle time, and buffer consumption to measure performance.

Uses:

• Flow Metrics
• Throughput Accounting