The EMI Project Boards
Collaboration Board (CB): is composed of the representatives of each beneficiary of
the grant agreement. The CB is responsible to coordinate any administrative activity
within the beneficiary home institute or company and to define the overall long-term
strategic objectives of the project. The chair of the CB is elected by the CB members
for a fixed duration and rotated according to the rules that will be established in the
Consortium Agreement.
Executive Collaboration Board (ECB): is a consulting committee within the CB
composed of two representatives from the CB for each of the participating middleware
consortia (ARC, gLite and UNICORE). The
ECB represents the CB in all the
situations where a full participation of all beneficiaries is not required and a faster
decisional process is necessary to assist the PD in short-term or urgent matters, mainly
on non-contractual issues concerning the relationships among the Middleware
Consortia. The
ECB is also the first escalation step in the resolution of grave technical
disagreements between the Project Director and other members of the project.
Project Executive Board (PEB): is responsible to assist the Project Director in the
execution of the project plans and in monitoring the milestones, achievements, risks
and conflicts within the project. It is led by the PD and is composed of the Work
Package Leaders, the Technical Director and the Deputy Technical Director.
Project Technical Board (PTB): is led by the TD and composed of the Technical
Area Leaders and a representative and is responsible to assist the TD in defining the
technical vision of the project and deciding on specific technical issues. The PTB
members are the coordinators of the project Technological Areas. The PTB can invite
experts (e.g. product team leaders, component developers, etc.) or delegate specific
tasks to appointed working groups as required.
Engineering Management Team (EMT): is lead by the Release Manager and
composed of the Product Team Leaders (or duly appointed representatives), a QA
representative, a Security representative, representatives of the Operations teams of
the major infrastructures (EGI, PRACE, etc.) and invited experts as necessary. The
role of the
EMT is to manage the release process and the 'standard‘ changes, that is all
the changes that are pre-approved based on established policies and do not need to be
individually approved by the PEB or the PTB. This includes software defects triaging
and prioritization, technical management of releases, integration issues, and user
support request analysis. The
EMT is therefore the natural aggregation point for all
PTs to discuss practical integration and release issues and is adapted to the largely
distributed nature of the project. This mechanism has been already successfully
employed in other very distributed projects like EGEE III. The Release Manager
reports to the SA1 Work package leader.
--
FloridaEstrella - 07-Jun-2010