DRAFT: LCG Planning, Monitoring and
Management Board Membership
See MB: http://lcg.web.cern.ch/LCG/Boards/MB/mb.html
- Each project should provide a
plan with milestones.
- Templates are provided to
help and to foster consistency.
- Would be good to have a
milestone every 1 or 2 months, and more frequent milestones would be
better. Milestones should specify in detail what it means to have
something "released" or "installed".
- Describe the deliverables of
each milestone: form and status of the deliverable, features that will be
provided, which performance values to be reached.
- Specify details on how a
milestone will be verified (format, availability, capacity).
- Hyperlinks should be used to
reference separate notes, bug reports, and other useful information about
- Dependencies among milestones
are managed separately, with hyperlinks and manually (for now).
- The dates of the milestones
can be changed. A "change request" (template available) is
submitted and dependencies are taken into account. The impact of each
change on other projects is evaluated by the PO
and the project leaders involved.
The PO reports to the MB at the weekly meeting all changes relevant at
global project level, or whenever a management decision is needed.
- In addition to the
milestones, each project manages an "action list" for recently
added and outstanding issues. Each "action request" describes
new issues (bugs, changes, etc.) and the project leader prioritizes them,
taking into account relevance for the users and impact on the project.
- A general plan for global
LCG milestones ("WLCG high level milestones") will be maintained
by the PO.
Monitoring and Reporting
- Weekly follow-up and contact
with the projects. Report to MB, if needed, by the PO.
- Monthly reports to the MB
with summary of main achievements and decisions (PO).
- Each project (site, area
projects, experiment task forces) provides a quarterly report.
- The QR will be lighter and
more structured than then in the past. It will only require to comment the
milestones of the quarter, provided, by the PO,
to each project leader:
- past milestone with
- outlook for coming
- comments on each
milestone and action of the quarter
achievements and issues
- Review initial plan.
Small team of users and specific plans reviewed by users.
Identify dependencies and critical paths.
- Review QR.
By the PO and 2 or 3 assessors. Permanent
reviewers and maybe others, changing every quarter, in order to match
specific skills and needs. The review also verifies the dependencies in
case of change of milestones.
- Review LCG Services.
Every 6 months. By domain experts?
- LHCC Referees, periodic updates.
Who should be part of it?
GDB Site Monitoring and Reporting
- The GDB is the body where
site monitoring and site reporting is handled on a monthly basis.
- The GDB chair should
summarize the major items, decisions and actions of each GDB meeting for
the next MB meeting.
- The GDB chair summarizes
decisions and achievements of each quarter in a QR.
- Site usage statistics:
Performance, jobs executed, success/failures.
- Status and configuration of
the services provided.
- Every site has updated
tables with: capacity, performance, services, versions, platforms, etc.
uptime/downtime, split by experiment.
- Report to the MB via the
- Technical progress is
reported at the GDB.
- Monthly reports on progress
(by the PO).
- Milestones and action list
of the projects.
- Quarterly Reports commenting
past and coming milestones.
Architects Forum (AF) is the body where the Applications Area is
- The AF
chair summarizes decisions and achievements of the quarter in a QR.
- The experiments “task
forces” are the channel for the planning and monitoring of all
experiments issues regarding the LCG services.
- The task force defines and
monitors the experiments milestones regarding the LCG services.
- Weekly update on the
progress and requests for other projects (features and fixes).
milestones to check capacity, services and operations.
- Testing critical
issues of each service.
- Develop acceptance
tests and applications.
- Reports, from time to time,
on progress and difficulties to the MB via the computing coordinator.
- Quarterly report covers
activities of the task force, actions and issues.
- Templates for all document,
reports and tables for all projects (experiments, sites, areas)
- Planning: One table
- Reporting: One table
- Templates for
request to “add/remove actions” and milestones “changes
- Distribute and present the
proposal and templates to the MB.
- Receive feedback from the MB
- Modify and publish this
proposal and the related templates.
- Projects leaders define
their plans using the templates
- Review and discuss
- Check for consistency
(e.g. make sure that the same milestones have the same name across projects/sites).
- Start using the plans and
monitor the project progress.
- Other activities will be
critical path analysis, dependencies and risk assessment.