Estimation and Measurement Telecon, 2010-04-09
See
Weekly Meeting Logistics for telecon information.
Previous telecon 2010-04-02
Next telecon 2010-04-16
Attendees
AndrewCanham,
AndyBerner,
ArthurRyman,
LawrenceMandel,
LeeFischman
Minutes
1. Implementation Status - All
LawrenceMandel has picked up the prototype previously development by Rational and will continue its development.
2. Review of REST API Data Models - ArthurRyman
We reviewed the following data models:
No issues raised.
No issues raised.
Baselining Across Subprojects
AndrewCanham: If a project has subprojects, how do you handled baselining across all the subprojects?
ArthurRyman: The EMS 1.0 spec does not provide a way to represent the project-subproject structure. It's limited to describing estimates and measurements for "atomic" projects, i.e. with opaque structure. The project-subproject structure would have to be handled by another tool, e.g. a project management tool, that was a consumer of the EMS 1.0 service. The consumer tool would use the EMS 1.0 REST API to individually baseline each of the subprojects in the master project.
Meaning of ems:isClosed
ArthurRyman: This is not a lifecycle state since that information should be represented in measurements of the project. It is an indicator that the project has been closed from a data update viewpoint, and that calibration tools can use the project as a stable source of historical data.
Write-Once Properties
AndyBerner: The ems:project property is conceptually write-once. However, the spec says it's read-write in order to allow for error correction. There should be separate admin mechanisms for correctly errors. I think making it write-once would be appealing.
ArthurRyman: I agree, and this particular case was one of the motivations for defining write-once properties. However, people may want to correct errors without needing admin assistance. If this property was write-once, a user would have to delete the scenario and recreate it with the correct project reference. I'd like to poll the others about how they feel about making this property write-once.
ArthurRyman: Since there is no strong preference to change this, let's revisit this after we complete the first pass of reviewing all the data models
Can Scenarios Span Projects?
LawrenceMandel: Can a scenario involve more than one project, e.g. doing a resource tradeoff between several projects?
ArthurRyman: No, a scenario represents an alternate way to run a single project. In your example, a portfolio management tools would have to create the alternate resource allocation scenarios for each project and manage their relations.
Comments
Add your comments here: