Essential Elements of Change Request Process for Grid Operations Tools

The Grid Ops Tools (SAM/FCR, SAM Admin's page, CIC portal, GOC DB, GGUS, GStat) each need to have at least a basic Change Request (CR) process in place. These CR processes must contain the following elements (as decided by the ROC managers on 22 May 07):

  1. Single point of entry to the process
    • For example, email address, web form, etc.
    • CRs arriving by any other route will be rejected
  2. Standard form/template so that it is clear for the requestor what information they must provide:
    • Name of requestor
    • e-mail of requestor
    • VO of requestor
    • Title/summary of request
    • Full description of request
    • Priority from requestor's point of view
  3. Publicly viewable list of new (unprioritized) requests, i.e. a "wish list"
    • Web page, etc.
    • CRs should be given a unique ID
  4. Regular review of requests by stakeholders (incl. ROC managers)
  5. Publicly viewable list of prioritized requests (schedule of work)
    • Web page, etc.
    • Each item should include:
    • Level-of-effort estimates
    • Estimates of completion date
    • Indication of progress made
  6. Clear contact point for questions, feedback, etc.

-- Main.thackray - 05 Jun 2007

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2007-06-05 - unknown
 
    • 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