Estimation and Measurement Telecon, 2009-08-14

See Weekly Meeting Logistics for telecon information.

Attendees

AndyBerner, ArthurRyman, LawrencePutnamJr, LeeFischman, ScottBosworth, SteveAbrams

Minutes

1. New Mailing List for Us

Please subscribe to http://open-services.net/mailman/listinfo/oslc-metrics_open-services.net and use it for discussions.

2. Faux Debate on Mapping Versus Standard Terms - LeeFischman, SteveAbrams

Should we define standard terms for use in XML representations, or should we define a mapping mechanism? Lee and Steve to present the alternate approaches.

SteveAbrams posted and presented his position. He advocated the use of agreed upon standards as opposed to any more complex mechanism, e.g. ontologies, for accomodating greater flexibility.

LeeFischman posted a briefer position in which he agreed with much of what SteveAbrams proposed but also felt that there would be a lot of variation in terminology among different development methods, and that OSLC should define several alternate vocabularies and a mapping among them, or to some canonical vocabulary. He suggested that instead of talking about automobilies, or use other analogies, that we work on defining standard terms for labor categories and activities.

We then proceeded to agree on standard terms for the concepts used in effort estimates. The table captured last week was updated as follows:

Encouraged by our success at agreeing on these three standard terms, we proceeded to repeat this exercise for role names. Refer to Role Names for the results. We did not achieve total agreement, in particular on the accounting practices associated with these roles and their associated effort estimates and labor costs. ArthurRyman proposed a set of accounting practices associated with roles. Everyone should review and comment on these accounting practices.

3. Continue Review of Representing Effort Estimates

• review Galorath and QSM sample data
• reviewXML representation of fact tables

4. Other Business

None.

Comments

Add your comments here: