The goal of this effort is to define a common set of resources, formats and RESTful services for the use in Change Management tools and use by ALM, PLM, Integrated Service Management (ISM) and DevOps tools.
Change Management (CM) resources define the change requests and tasks of the software and hardware delivery lifecycle. These resources relate and interact with many other resources such as projects, products, or categories.
Change Management Charter
The goal of this effort is to define a common set of resources, formats and RESTful requests for the use in Change Management tools and use by ALM and PLM tools.
Change Management (CM) resources define the change requests and tasks of the software and hardware delivery lifecycle. These resources relate and interact with many other resources, such as project, product, category, etc.
The Change Management Workgroup will produce:
- Scenarios – these will guide the priorities and specification contents within the WG
- Specifications – both maintenance of existing specifications, guidance on usage and new specification
- Supporting and enabling material – on an as-needed basis to support broad adoption
Relationship to other activities and workgroups
Certain specification needs may be found useful and needed by other domain workgroups and therefore may be adopted or endorsed by the Core Workgroup.
This Workgroup will be an active participant within the Core workgroup as well; the participant will be the workgroup lead or a delegate.
For more information, see the Workgroup Best Practices.
Target Specification Development Organizations (SDOs)
Specifications developed by this WG may be contributed to these SDOs:
This contribution to these SDOs is dependent on maturing the specifications within this WG and gaining consensus on the contribution. At that point, the WG would make a proposal to the OSLC Steering Committee for such a move. For more information, see the Workgroup Best Practices.
By agreeing to become a member of this WG, this implies some amount of time and contribution to assist in the development and promotion of the specification. There is no minimal amount of time or level of participation.
It is recommended that each member should expect to:
- attend the teleconferences
- participate in off-line mailing list discussions
- contribute and review scenarios
- participate in prioritization activities
- potentially lead the WG and/or meetings
- contribute specification content in the form of proposals and actual specification text
- edit and organize the specification
- address specification issues
- contribute to a test suite
- produce implementation feedback in form of implementation reports
Meetings Frequency and Communications
Meetings are conducted typically by teleconference. The frequency changes based on time of year and current cycle of specification development but should expected to be every two weeks. Additional meetings may be held by a subset of the workgroup on a more frequent basis to work on some focused activities.
Meetings should be announced at least 48 hours in advance. Meeting agendas should be set at least 24 hours in advance.
The mailing list and wiki should be used to capture all work and discussions; this provides workgroup members that can’t attend meetings the ability to participate and provide feedback.
Decisions within this workgroup are consensus driven, facilitated by the workgroup lead.
The WG members nominate a lead. WG members work to reach consensus to select who the lead or co-eads should be. Having more that one WG Lead is preferred but not required.
Members of this Workgroup agree to this Workgroup Participation Agreement.
Bit of a ghost town here