This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

Attendees

Andy Berner, Kishore Gagrani, Joakim Waltersson , Larry Putnam, Lee Fischman

My appologies to anyone who missed the e-mail with the changed phone number for this week only.

Notes:

(unedited notes from the meeting---I will organize and revise later--ajb)

Metrics:

SLOC is a standard term:

Different approaches can often be converted from one to another-key is understanding how the code was counted

KLOC and ESLOC are NOT standard! (ESLOC = Effective Source Lines of Code)

Lee contributed a detailed definition

May be estimated from architect or technical resources; during construction pulled out from scm system; tied to history of the project

SLOC may be derived from other size measures

Potential differences between tools: tools may differ in what they convert to

SEI has code counting standard

Project manager knows the size metric as "the target"

Specific metric matters when you're doing the estimate

Project manager wants to know "how much" of the metric has been completed

Size metric may change over course of the project

Alternate size metrics: size metrics may change (agree???), and multiple size metrics may be used (agree??? Not much agreement---QSM found this, Galorath and Price not so much)

Percent complete of task is not the same as percent complete of size

Identified at least two places where there is communication about size metric: Input to estimate (may be updated)-i.e. "target size" "estimated size at completion", and "tracking"---how much of the expected size is completed

From proj. mgr. point of view: (Kishore) project mangers prefer function points, architects maybe use cases

List we've talked about so far: Common size metrics: SLOC, Function Points (IFPUG), Cosmic function points (george simons??) (lee will put link in wiki), IEEE Software Mag., Story Points (Scrum), Use Cases, Use Case Points, Predictive Object points (may be Price specific-may not be standard??)

We shouldn't limit ourselves to "standard" metrics---customers use a variety, some standard, some not: So we need "tag" (for what metric), and way to input value

BUT it must be a "size" metric (as opposed to task completed), must be numeric (???maybe not-analogy???)

Metrics are used as inputs and outputs.

Topic revision: r1 - 28 Apr 2009 - 14:30:43 - AndyBerner
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback