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.

Estimation Telecon, 2009-05-15

See Estimation and Measurement Meetings for meeting logistics.

Agenda

Review updated data model

We'll review the data model changes based on last week's discussion.

Start specifying one resource and service

Let's pick one part of the Monitoring and Controlling use case and specify the resources and services to support it.

Minutes

Attendees

AndyBerner, AndrewCanham, ArthurRyman, ChuckWells, Jim Koslow, LeeFischman, ScottBosworth, SteveAbrams, StevePitschke

Regrets

MurrayCantor

Planning for F2F? at RSC

LeeFischman requested an agenda and background material for the meeting that MurrayCantor is organizing for RSC. The meeting will be held Wed. at 8AM.

ACTION: MurrayCantor to provide agenda and details in advance of the meeting.

Review of Data Model Updates

ArthurRyman reviewed the updates.

We probably need to model the different types of effort expanded on a project, e.g. analyst, architect, developer, tester, etc. since the total effort is broken down by these roles.

LeeFischman asked is the REVISION attribute of ARTIFACT_REVISION included the concept of major and minor revisions. ArthurRyman said that the goal is to keep track of the series of changes made to an artifact, and that the COMMENT attribute could be used to describe the change. It is outside the scope of this group to define how revisions are implemented. The Dublin Core includes a isVersionOf concept and that may be all we need.

We need to qualify the metric with dimensions like role, severity, etc. For example, when estimating effort, we have a metric called effort, the unit of measure would be person-months or person-years, but the metric would have other dimensions like the specific type of effort, e.g. analyst, tester, etc. Similarly a quality metric like defect count would have a dimension such as severit, e.g. high, normal, low.

Start Resource Definition


ArthurRyman proposed doing the Re-Estimating use case first since that is the steady state and involves interaction between the project management tool and the estimation tool. Project properties, constraints, and actuals are send to the estimation tool. The estimator creators a new estimate to completion for the project and sends it back to the project management tool. Arthur will propose resource definitions for next week.

SteveAbrams requested more concrete details in use case. LeeFischman offered to flesh out the use case. AndyBerner will coordinate the discussion between Lee and Steve.

Comments

Add your comments here:

 
Topic revision: r2 - 15 May 2009 - 15:28:13 - ArthurRyman
 
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