...
| Page properties | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Entities involved in the procedure
| Entity/Role | Description |
|---|---|
| Auditor | The person running the audit. Typically this is the CHM Process Manager |
| Auditee | The person representing the organisation running the EGI branded service who are running their own internal Change Management process |
Triggers
The CHM Process Manager becomes aware that an organisation running an EGI branded service is running their own internal Change Management process
Steps
| Step# | Responsible | Action | Prerequisites, if any | |
|---|---|---|---|---|
| 1 | Auditor | Arranges a meeting with the auditee. This may be by video conference | None | |
| 2 | Auditor | Ensures that the essential requirements of ISO20k with respect to change management (listed in the Overview) are being met | None | |
| 3 | Auditor | Records the meeting and audit findings in this procedure | None | |
Organisations in EGI Foundation running their own Change Management process
| Organisation | Date | Auditor | Auditee | Notes |
|---|---|---|---|---|
| IASA |
| Marios Chatziangelou <mhaggel@iasa.gr> | All three essential requirements are currently being met. Changes are discussed within a bi-weekly internal team meeting. In addition, ad-hoc meetings are run during the week to evaluating changes. The team currently use GitLab as a tool for recording changes https://gitlab.iasa.gr which are partially synchronized with the public (https://github.com/IASA-GR . For each change, the team collectively discusses what could go wrong and tests on their development environment in the days/weeks running up to the change. Although there is no formal Post Implementation Review, if there are problems following a change, these are recorded in the weekly meeting minutes. If appropriate, issues are tracked on GitLab. Everything is recorded, including who did the changes, when the changes were done, in GitLab. It was re-iterated that IASA are free to choose to use the central CHM if they wish, and they are obliged to if changes are done which directly affects other EGI services. AppDB (provided by IASA) has now moved under the scope of the EOSC-hub CHM and so IASA no longer provide any services under EGI CHM. As such, CHM within IASA need no longer be considered within EGI CHM, until and unless they provide services within scope in the future. |