Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "VT Scientific Discipline Classification Change Management"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Template:ScientificDisciplineClassification_menubar}} {{TOC_right}}  
{{Template:ScientificDisciplineClassification_menubar}} {{TOC_right}}  


{{ VirtualTeamProject |
(Draft in progress)
EGI Scientific Discipline Classification
Change Management Policy


Abstract:
{{ Overview |
This document defines the policy regarding the ownership and management of the EGI Scientific Discipline classification to ensure it is both periodically reviewed and managed through defined processes. In addition, as the community evolves and potential adoption by other e-Infrastructures expands, the change management policy will provide clarity and transparency regarding its evolution.  
This page holds the policy regarding the ownership and management of the EGI Scientific Discipline classification to ensure it is both periodically reviewed and managed through defined processes. In addition, as the community evolves and potential adoption by other e-Infrastructures expands, the change management policy will provide clarity and transparency regarding its evolution.  
This document also satisfies recommendation #5 of the EGI Scientific Discipline Classification Virtual Team final report endorsed by EGI management for implementation.
This document also satisfies recommendation #5 of the EGI Scientific Discipline Classification Virtual Team final report endorsed by EGI management for implementation.
 
|
Table of Contents:
Roles and Responsibilities =
1 Roles and Responsibilities 3
Ownership =
1.1 Ownership 3
1.2 Hosting 3
1.2.1 Location 3
1.2.2 Technical Details 3
1.3 Change Manager 3
1.4 Change Advisory Board 4
1.5 Change Initiators 4
2 Change Management 4
2.1 Overview of Requirements 4
2.2 Processes and Procedures 5
2.2.1 Recording Changes 5
2.2.2 Classifying Changes 5
2.2.3 Assessment and Approval 5
2.2.4 Emergency/Urgent Changes 5
2.2.5 Decision Making 5
2.2.6 Schedule of Changes 5
2.2.7 Change Reversal 6
References 7
 
 
 
Copyright:
This work by members of the EGI-InSPIRE collaboration is licensed under a Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0). This license lets you remix, tweak, and build upon this work, and although your new work must acknowledge EGI.eu, you do not have to license your derivative works on the same terms. Reproductions or derivative works must be attributed by attaching the following reference to the copied elements: “Based on work by members of the EGI-InSPIRE collaboration used with permission under a CC-BY 3.0 license (source work URL: https://wiki.egi.eu/wiki/VT_Scientific_Discipline_Classification”).
 
1 Roles and Responsibilities
1.1 Ownership
As this classification has been developed by dedicated Virtual Team supported by the EGI-InSPIRE project for EGI-wide purposes and for implementation with a variety of its tools, EGI.eu will take ownership of the classification.
As this classification has been developed by dedicated Virtual Team supported by the EGI-InSPIRE project for EGI-wide purposes and for implementation with a variety of its tools, EGI.eu will take ownership of the classification.
However, as potential adoption of the classification expands, it will be essential to offer mechanisms in which other organisations with invested interest can take part in its future development.
However, as potential adoption of the classification expands, it will be essential to offer mechanisms in which other organisations with invested interest can take part in its future development.
1.2 Hosting
Hosting=
1.2.1 Location
Location=
In order to distribute the common scientific classification tree among the EGI services and beyond and keep them up-to-date on potential new changes (new additions, updates or even deletions), a single end-point needs to be created that will make the scientific classification available over a simple, developer-friendly, stable/reliable and well defined API.  
In order to distribute the common scientific classification tree among the EGI services and beyond and keep them up-to-date on potential new changes (new additions, updates or even deletions), a single end-point needs to be created that will make the scientific classification available over a simple, developer-friendly, stable/reliable and well defined API.  
Since the EGI Applications Database (appdb.egi.eu) service makes significant use of technologies related to APIs, actually the entire service has been built on the top of a RESTful (XML and JSON) API, it will be used as the central tool for hosting the classification.
Since the EGI Applications Database (appdb.egi.eu) service makes significant use of technologies related to APIs, actually the entire service has been built on the top of a RESTful (XML and JSON) API, it will be used as the central tool for hosting the classification.
The host of this service will be IASA.
The host of this service will be IASA.
1.2.2 Technical Details
Technical Details =
Marios to add technical details and update text.
Marios to add technical details and update text.
 
|
1.3 Change Manager
Change Manager =
The Change Manager for the SDC will be: EGI Strategy and Policy Manager or Senior Strategy and Policy Officer, unless otherwise agreed through the Change Advisory Board.
The Change Manager for the SDC will be: EGI Strategy and Policy Manager or Senior Strategy and Policy Officer, unless otherwise agreed through the Change Advisory Board.
The main duties of the Change Manager, some of which may be delegated, are:  
The main duties of the Change Manager, some of which may be delegated, are:  
• Receives, logs and allocates a priority to all requests for changes that are totally impractical.
*Receives, logs and allocates a priority to all requests for changes that are totally impractical.
• Tables all Request for Changes (RFCs) for a Change Advisory Board (CAB) meeting, issues an agenda and circulates all requests for changes to Change Advisory Board members in advance of meetings to allow prior consideration.
*Tables all Request for Changes (RFCs) for a Change Advisory Board (CAB) meeting, issues an agenda and circulates all requests for changes to Change Advisory Board members in advance of meetings to allow prior consideration.
• Chairs all CAB and ECAB meetings and convenes any urgent CAB meetings for urgent RFCs.
*Chairs all CAB and ECAB meetings and convenes any urgent CAB meetings for urgent RFCs.
• Authorizes acceptable changes, either alone or after a CAB has taken place.
*Authorizes acceptable changes, either alone or after a CAB has taken place.
• Issues change schedules.
*Issues change schedules.
• Liaises with all necessary parties to coordinate change building, testing and implementation, in accordance with schedules.
*Liaises with all necessary parties to coordinate change building, testing and implementation, in accordance with schedules.
• Updates the change log with all progress that occurs, including any actions to correct problems and/or to take opportunities to improve quality.
*Updates the change log with all progress that occurs, including any actions to correct problems and/or to take opportunities to improve quality.
• Reviews all implemented changes to ensure that they have met their objectives; refers back any that have been backed out of have failed.
*Reviews all implemented changes to ensure that they have met their objectives; refers back any that have been backed out of have failed.
• Reviews all outstanding RFCs.
*Reviews all outstanding RFCs.
• Analyses change records to determine any trends.
*Analyses change records to determine any trends.
• Closes RFCs.
*Closes RFCs.
• Produces periodic management reports.
*Produces periodic management reports.
1.4 Change Advisory Board
|
Change Advisory Board =
The Change Advisory Board (CAB) is an advisory body for handling changes to the classification. The CAB is a body that exists to support the authorisation of changes and to assist change management in the assessment and prioritisation of changes. As and when a CAB is convened, members should be chosen who are capable of ensuring that the change is adequately assessed from both a business and a technical viewpoint. To achieve this, the CAB needs to include people with a clear understanding across the whole range of stakeholder needs. The Change Manager will normally chair the CAB.
The Change Advisory Board (CAB) is an advisory body for handling changes to the classification. The CAB is a body that exists to support the authorisation of changes and to assist change management in the assessment and prioritisation of changes. As and when a CAB is convened, members should be chosen who are capable of ensuring that the change is adequately assessed from both a business and a technical viewpoint. To achieve this, the CAB needs to include people with a clear understanding across the whole range of stakeholder needs. The Change Manager will normally chair the CAB.
The current/active list of CAB members should be hosted on a dedicated page, which is publicly available.
The current/active list of CAB members should be hosted on a dedicated page, which is publicly available.
Line 118: Line 90:
R 2
R 2
EGI Scientific Discipline Classification (SDC VT Output) – https://wiki.egi.eu/wiki/VT_Scientific_Discipline_Classification_Classification
EGI Scientific Discipline Classification (SDC VT Output) – https://wiki.egi.eu/wiki/VT_Scientific_Discipline_Classification_Classification
|
VTP_Motivation =
EGI is a multidisciplinary e-Infrastructure where users belong to a variety of different scientific disciplines. EGI needs to categorise these users by disciplines through a number tools (e.g, AppDB, operations portal, training marketplace, CRM). Although a legacy classification was inherited from EGEE, different tools have adopted different classifications and the expanded user base has many virtual organisations falling into the "other" category. As EGI now operates within an open ICT ecosystem, it has become essential to agree on a common, coherent classification that is not only consistent across all tools, but allows for smooth inclusion of future user communities as well.<br>
EGI is a multidisciplinary e-Infrastructure where users belong to a variety of different scientific disciplines. EGI needs to categorise these users by disciplines through a number tools (e.g, AppDB, operations portal, training marketplace, CRM). Although a legacy classification was inherited from EGEE, different tools have adopted different classifications and the expanded user base has many virtual organisations falling into the "other" category. As EGI now operates within an open ICT ecosystem, it has become essential to agree on a common, coherent classification that is not only consistent across all tools, but allows for smooth inclusion of future user communities as well.<br>
|
|

Revision as of 11:47, 22 October 2013

VT Scientific Discipline Classification: Home • Scientific Disciplines • Change Management • Query API • Tasks/Actions/Plans • Meetings •


(Draft in progress)

Template:Overview

Retrieved from "https://wiki.egi.eu/w/index.php?title=VT_Scientific_Discipline_Classification_Change_Management&oldid=60961"