This document discusses quantitatively analyzing software project scope. It outlines benefits like more cost control, objective project reviews, and risk management. The approach allows benchmarking between projects and is not dependent on specific technologies, teams, or methodologies. Basic metrics to measure include software size, reuse, productivity, and quality requirements, along with additional metrics like defect numbers and removal rates. Contact information is provided for further discussion.

1. Managing Software Development
Scope
Hannu Lappalainen
30.09.2014
Albitech Consulting Oy

2. Quantative Analysis of SW Project Scope
30.9.2014 Albitech Consulting Oy 2

3. Benefits of Approach
• More cost control and predictability for management
• Reviewing project performance becomes more objective
• Enhanced project risk management
• Applicable to vendor management by assessing delivery efficiency
• Approach is not dependable on
• Technology
• Team experience
• Component reuse
• Development process or methodology (agile, iterative, staged).
• Enables benchmarking between projects, organizations and also
internationally (using objective functional size metrics)
• Enables flexible and efficient project scope change management while
not losing control on costs
• Metrics may be based on standards
• Results may be also used in portfolio management.
30.9.2014 Albitech Consulting Oy 3

4. Basic Metrics
Basic Metrics:
• Software size
• Reuse of software components
• Productivity rate
• Effect of software product quality requirements
• Effect team, development process and project enviroment factors
Additional Metrics:
• Number of defects
• Defect removal rate.
30.9.2014 Albitech Consulting Oy 4

5. Contact Info
Hannu Lappalainen
ICT Management Consultant
Albitech Consulting Oy
E-mail: hannu.lappalainen [at] albitech.fi
30.9.2014 Albitech Consulting Oy 5