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)
• Metrics
• Performance Measurement

Related

• Monitoring
• Estimation
• Code Reviews

Addresses / Mitigates

• Operational Risk: Provides data to inform decision-making and improve operational efficiency.
• Feature Access 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.
• Software Dependency Risk: Creates dependencies on measurement tools and their accuracy.
• Complexity Risk: Collecting and analyzing data can add to the complexity of the project.
• Map And Territory 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.
• Scrum: Scrum uses various metrics like burndown charts to measure progress.

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.

See Also

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.

Scrum

An Agile framework for managing and completing complex projects.