Estimation and Measurement Telecon, 2009-10-23

See Weekly Meeting Logistics for telecon information.

Attendees

AndyBerner, ArthurRyman, LawrencePutnamJr, LeeFischman, ScottBosworth

Minutes

1. Software Metrics Definition Status - LawrencePutnamJr

LawrencePutnamJr reviewed the consolidated article on metric definitions.

In Schedule metrics, it may be useful to define standard phases, e.g for Rational Unfied Process the standard phases are Inception, Elaboration, Construction, and Transition. It may be useful to analyse other metrics, e.g. Effort, by phase. Phase is therefore a useful level of the Work dimension of a project.

In general, the metrics we define are either measures or dimensions. A measure is a quantity such as Effort. A dimension is an attribute such as Time or Role that is useful for analysing some measure. For example, it is useful to analyse Effort by Time period and by Role (i.e. what type of work is being performed).

Story Points are really a Size metric since you need to combine it with Team Velocity in order to compute Effort.

We should add Complexity and Productivity metric definitions, perhaps including them in the Size and Effort categories, or defining new categories.

We should cite the IEEE SWBOK Guide on Software Testing in the Quality category. The IEEE defines a fault or defect to be the portion of the source code that is incorrect, and a failure as an observed incorrect behavior. When testers report defects they are in fact usually reporting failures. Programmers inject faults into the code and testers find failures. Debugging traces the failure to the fault.

2. Primer Status - ArthurRyman

We timed out.

ACTION: Initiating a Project - Act 1. Setup is complete now. Everyone should review it and we'll discuss it next week.

3. Other Business

None.

Comments

Add your comments here: