Change Management Scenarios

This document provides high-level scenario descriptions and links to elaborated scenarios that have been identified by the working group as prioty scenarios to be defined in specification and validated by product implementations.

Priority Scenarios

Collaborative ALM

• OSLC-CM 2.0 (scoping):
  • (in scope) Streamlined developer task management in an IDE
  • (in scope) CmScenariosReporting
  • (in scope) Change Management of Requirements
  • (stretch) Change Request linked to a source control change set resource
    • See related work done in SCM domain ScmWorkItemIntegrationStory
  • (stretch) Code Review
  • (stretch) CmScenariosApplicationAnalysisTools

• OSLC-CM 1.0:
  
  • Find and Fix a Defect
  • Plan Change Requests in an Agile Planning Tool
  • Setup and configuration

• Others (possibly fold into "Plan Change Requests" scenario):
  • Add a new, high priority plan item with a link to a storyboard
  • Sprint planning utilizing the linked storyboard
  • Create Sprint backlog and add Sprint goals
  • Scrum master moves the agreed items from the Product backlog to the Sprint backlog
  • Create tasks linked to the story sketch, estimate the work, link tasks to requirement details
  • Link to the Sprint Backlog stories from the test plan (determines scope of test effort)
  • The scrum master moves the agreed items from the Product backlog to the Sprint backlog
  • Another view TechnicalViewOfScenarios

Aggregation of Change Requests from disparate sources

• Streamlined developer task management in an IDE
• CmScenariosReporting

Feedback

Specification comments and issues

References

• Collaborative ALM Scenarios for Rational Team Concert
• List of scenarios for possible future specification