Assess Completeness
At the end of the iteration /project the team assesses their completeness. Are you ready to deliver?
This is a direct
copy of the
AssessScenario for the purposes of analyzing the detailed scenario and what can be accomplished with common vocabularies.
Scenario
- Assess development status
- All in-plan requirements are implemented
?oslc_cm.query= type="requirement" and assignedTo="{development line}" and status="implemented"
- All / expected Development tasks are complete
?oslc_cm.query= dc:type="task" and assignedTo="{development line}" and status="complete"
- Notify owners to close open tasks
?oslc_cm.query= dc:type="task" and assignedTo="{development line}" and status="open" & oslc_cm.properties=owner{*},status,dc:identifier,dc:title
- Repeat until expected completeness reached
- Assess test status
- Test execution complete per plan
?oslc_cm.query= dc:type="testexecution" and assignedTo="{development line}" and status!="closed"
- Notify owners to close open tasks
- Repeat until expected completeness reached
- Assess Exit Criteria
- Defects fixed / expected quality met
?oslc_cm.query= dc:type="defect" and assignedTo="{development line}" & oslc_cm.properties=status,dc:identifier,dc:title,
- Exit criteria met (if any)
- Assign tasks & owners to meet exit criteria.
- Repeat until expected completeness reached
- Identify possible assets to distribute
- Optional: Approve
- Optional: demonstrate iteration
Pre-conditions
Post-conditions
Possible Resource Definition
In reviewing the scenario above, we'll expand on this to define a common vocabulary to meet the needs of that scenario.
Example
ChangeRequest? :
<ChangeRequest>
<dc:identifier>Bug123</dc:identifier>
<dc:title>Some Bug Title</dc:title>
<status>closed</status>
<dc:type>defect</dc:type>
<assignedTo>release1.0_milestone3</assignedTo>
<owner rdf:resource="bob@myemail.here" />
</ChangeRequest