[OASIS Issue Tracker] (OSLCPROMCO-3) Define change management scenario and model to be used in PROMCODE spec

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://tools.oasis-open.org/issues/browse/OSLCPROMCO-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37308#comment-37308 ] 

Masaki Wakao commented on OSLCPROMCO-3:
---------------------------------------

One scenario: 
1. At the status meeting in a project team, check the status of progress and quality.
  - Take a snapshot including all items.
  - Check actual end date of each Work Item, result of Measurement, and Issues status.
  - See differences between the latest and previous snapshot.
  - If necessary, update planned start and end date of Work Items
2. At the meeting with stakeholders (customers), check the status with the latest snapshot,
  - If necessary, update (remove, add, change) Scope Items and related items.

> Define change management scenario and model to be used in PROMCODE spec
> -----------------------------------------------------------------------
>
>                 Key: OSLCPROMCO-3
>                 URL: https://tools.oasis-open.org/issues/browse/OSLCPROMCO-3
>             Project: OASIS OSLC Lifecycle Integration for Project Management of Contracted Delivery
>          Issue Type: Improvement
>            Reporter: Masaki Wakao
>
> There are 2 different level of scenarios raised during meeting on April, 22.
> - Simple change log
> - Transactional change (baseline, change-set)
> We have to define our scenario and model for PROMCODE.
> There are candidate external definitions for each scenario:
> - TRS for simple change log
> - Configuration Management for transactional change



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)