EMI Product Teams Lifecycle Procedure

The development, maintenance and support of EMI products (services and components) are performed by dedicated teams of developers and testers, referred to as the 'Product Teams', with specific knowledge and expertise. Product Teams (PT) have the following characteristics:

  1. A PT is led by the Product Team Leader responsible to coordinate the team during all activities of development, maintenance, support, testing, etc. The PT Leader is an official member of the EMI Engineering Management Board (EMT). The PT Leader may delegate another person to attend EMT meetings.
  2. The activities of a PT span across different project work packages. They represent a vertical element responsible for one or more products across the product lifecycle. As such, PT members may report effort in SA1, SA2 or JRA1 depending on the specific tasks performed. This allocation is not fixed; it is dynamic depending on the status of the products at any given time. The correct allocation of effort between development and maintenance tasks is the responsibility of the PT Leader who oversees the priorities in consultation with SA1 and JRA1 leaders.
  3. A PT is responsible to provide technical support for one or more products using the GGUS system as user request tracker. To this end, the PT owns one or more Support Units in GGUS. A single Support Unit can be shared among different PTs; however this is not encouraged as PT performance tracking with respect to addressing user requirements will be difficult.
  4. A PT is not necessarily a permanent entity for the entire duration of the EMI project. The list of services and components managed by EMI changes over time; the PTs, and the allocation of people to PTs, will adapt accordingly.

The PT lifecycle scenarios depend on the Product lifecycle:

  1. A Product is developed and/or maintained for whole duration of the EMI project: the corresponding PT exists for the entire duration of the EMI project. PT membership may change over time
  2. A new Product is developed during the EMI project and cannot be assigned to any of the existing PTs: a new PT is created
  3. All Products of a PT reach their end-of-life deadline and are deprecated: the PT is closed and its members assigned to other tasks based on the needs of the project

Development of New Products and Creation of new Product Teams

  1. The Technical Director (TD), assisted by the Project Technical Board (PTB), is responsible to periodically assess the list of EMI products and ensure these products follow the agreed requirements and the technical roadmap.
  2. In case a new product must be developed, the PTB decides to assign it to an existing PTs or create a new PT
  3. If a new PT must be created, the PTB:
    1. Provides a description of the new Product(s) owned by the PT
    2. Provides an explanation why none of the existing PTs can take ownership of the new Product
    3. Identifies the PT Leader and PT size estimate
    4. Identifies the tasks or products that have to be stopped or delayed due to effort re-allocation
  4. Once all information is available and agreed by the PTB, the TD notifies the PEB of the decision. If the PEB has objections to the creation of the new PT, it must provide a motivated explanation within three (3) working days from the TD notification. After three working days without motivated objections, the PT is considered approved. In case of objections, they must be discussed and resolved within the PEB. If PEB is unable to come to a majority resolution, the Project Director (PD) escalates the issue to the Collaboration Board (CB)
  5. Once the new PT is approved, it enters into force. All required entries in TWiki, the public web sites, mailing lists, etc. are updated by the TD or by the PT Leader upon TD request

Cancellation of Products and Removal of Product Teams

  1. The TD, assisted by the PTB, is responsible to periodically assess the list of EMI products and and ensure these products follow the agreed requirements and the technical roadmap.
  2. In case a product must be canceled or is at the the end of its support lifetime (based on agreements with EMI customers and existing support policies) and the corresponding PT has no other products to develop or maintain, the TD notifies the PEB of the situation, providing a proposal on how the PT resources can be re-allocated to other PTs
  3. If the PEB has objections to the removal of the PT and the re-allocation of its resources, it must provide a motivated explanation within three (3) working days from the TD notification. After three working days without motivated objections, the PT is considered closed. In case of objections, they must be discussed and resolved within the PEB. If PEB is unable to come to a majority resolution, the PD escalates the issue to the CB
  4. When a PT is closed, the team ceases to operate. All PT-related entries in TWiki, the public web sites, mailing lists, etc. are updated by the TD and the PT Leader.

-- AlbertoDiMeglio - 08-Sep-2010

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2010-09-08 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback