How to contribute to a Quarterly Report

At the end of each quarter, a Product Team is expected to provide a report summarizing the activity within the PT in that quarter.

Each contribution should be in text/plain format and be structured as follows:

  • Progress Summary

  • Issues and Mitigation
    Provide corrective actions taken for each issue reported

  • Plans for the next period

  • Main Project and Activity meetings attended
    Don't mention internal meetings.
    Provide date, location, title, # of participants, a short report on the outcome (this is mandatory).

  • Conferences/Workshops organised
    Provide date, location, title, # of participants, a short report on the outcome (this is mandatory)

  • Other Conferences/Workshops attended
    Only the main ones.
    Provide date, location, title, # of participants, a short report on the outcome (this is mandatory)

  • Publications
    Provide publication title, author(s), journal title, number/issue, date

More details on the format are available in the template.

In the preparation also consider the following guidelines:

  • for products under the responsibility of JRA1, all the activity reported in the QR, either in the Progress Summary or in the Plans for the next period, should be related to a task in the JRA1 workplan kept in Savannah.
    Ideally everything should be related to a product release, which should be included in the JRA1 Release Schedule. If some work is not directly related to a specific release, it should in any case be related to a non-release task of the JRA1 workplan kept in Savannah.
    If a reported work is not related to either a release or other task in the JRA1 workplan, then there is something wrong;

  • when reporting on a certain product release, report the version of that release as "ABC v. x.y.z-p" (or similar) and add a one-line description telling what that release is supposed to provide;

  • don't make the sentence depend on a task, patch or bug number (e.g. don't write "bug #1234 has been fixed"). If you wish, put that number in parenthesis for our convenience, but it will likely be removed from the final report;

  • be short, it's a summary;

  • use full and correct sentences (subject, verb, complement);

  • use the impersonal form (e.g. don't write "we have done");

  • use the same tense for verbs, prefarably the present perfect;

  • use appropriate capitalization (it is VOMS, gLExec, Argus, ...);

  • do not use abbreviations nor contractions (e.g. "it's" -> "it is").

Previous QRs

The previous contributions to the overall project Quarterly Reports are available in EDMS:

  1. May 2008 - July 2008
  2. August 2008 - October 2008
  3. November 2008 - January 2009
  4. Periodic report for the first year
  5. May 2009 - July 2009
  6. August 2009 - October 2009
  7. November 2009 - January 2010

-- FrancescoGiacomini - 21-Oct-2009

Topic attachments
I Attachment History Action Size Date Who Comment
Microsoft Word filedoc EGEE-III-NA1-TEC-1008479-QRRevisedProcess-v2.0.doc r1 manage 248.0 K 2009-10-21 - 18:08 FrancescoGiacomini Template for Quarterly Report (MSWord)
Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2010-02-22 - FrancescoGiacomini
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback