PROC02 Requesting change in DoA
|EGI-Engage project:||Main page||WP1(NA1)||WP3(JRA1)||WP5(SA1)||PMB||Deliverables and Milestones||Quality Plan||Risk Plan||Data Plan|
|WP2(NA2)||WP4(JRA2)||WP6(SA2)||AMB||Software and services||Metrics||Project Office||Procedures|
|Title||PROC02 Requesting change in DoA|
The procedure has been introduced to better coordinate process of requesting changes in the DoA.
For Deliverables and Milestones change requests should be sent no later than six months before submission deadline.
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Each request needs to be described as follow:
• Scope: deliverable/effort/other
• For deliverables:
o name of deliverable/milestone
o type of change: name/timeline/scope
• Current status in DoA
• New proposed
The following table describes
|Step#||Responsible||Action||Prerequisites, if any|
||Requester send request to WP leader
||Creates ticket in AMB queue in EGI RT system with prefix [DoA change request] and is writing proposal to WP1 mailing list
||Discussion during the next AMB meeting
||Proposes action plan to Technical Coordinator (TC)
||Technical Coordinator (TC)||Proposes for approval/rejection or ask for more explanation
||Administrative & Financial Coordinator (AFC)||Validate proposal or ask for more information|
||If change does not require a change in the DoA, TC submit the proposal to PMB for approbation
||If change requires a change in the DoA, AFC submit the proposal to CB for approbation
|9||PMB or CB||Approval or rejection|
||Once approved by the appropriate body (PMB or CB)
||Mail EC Office for approval
||approved by CB or PMB|
||Project office (PO) and QM
||Submit a formal amendment request to the EC and the QM update related documentation, PO add information in changelog for the amendment
||approved by CB|