You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Contents

Methodology

This page describes the selection of ideas for an Incubator cycle. 

Ideas gathered during the year are listed and evaluated by the Main Incubator Board (MIB). Every proposer has to join a MIB meeting at least once to pitch his idea to the board.


Once this process has been completed, the Proposers are required to finalize the project description.

The remaining steps are described in the T&I Incubator Activity Process



Activities

Pitch Idea

Each new idea that was not yet presented to the MIBs will be pitched by the proposer (as part of a MIB meeting).  I.e. formerly pitched ideas won't be ppresented again. In general, a short pitch consists of a 5 min presentation and 5 min questions.

Discuss Idea

  1. The board briefly discusses all ideas gathered (MIB meeting)
    1. No in depth discussions, just specific questions or new insights
    2. Discussions should help to choose an idea for the next phase and not find technical solutions

Identify Risks

  1. It is checked if there are any risks that might put the implementation of the idea in danger (MIB meeting)
    1. Hardware/software/people not available
    2. GÉANT management decisions or legal conditions must be met first
    3. Parallel projects/tasks that need to be finished first

Prioritize Ideas

  1. The MIBs prioritise all not blocked ideas 
    1. The goal is to select four ideas for the next Incubator cycle
    2. Each MIB got four votes, which might be differently weighted
    3. Additionally, two ideas will be selected for the TIM programme with the same procedure
    4. Each member votes independently without knowing the voting results beforehand.
    5. Votes are conducted after the meeting, the MIBs have 7 days to vote

Check and Assess Ranking

  1. The votes of the MIBs are checked and assessed
    1. The assessment metric is not fixed yet, 
      1. The MIBs have four votes and must decide what's most important for them
      2. We don't tell them about any ranking or metrics we might use
    2. Ideas with a higher priority will be considered first, but ideas might still be skipped/selected for strategic reasons

Identify Pre-Requirements

  1. It is checked if the pre-requirements to start the activity are fullfilled
    1. Is the Proposer available and willing to took on the PI role in the next cycle?
    2. Is there enough knowledge in the Alpha/Omega team to work on the activity?
    3. Do we possess hardware or software necessary?
    4. Are any external dependencies/persons available within the next cycle?
    5. Is the service owner responsible available and interested in the project?
    6. Can the activity finalized within 6 months if started in the next cycle?
    7. Write down identified risks and high level mitigation as part of the activity proposal

Propose Activities

  1. A list of four activities is proposed to the MIB & ALs, and proposer(s) (stakeholders)

Review Selection

  1. The MIB has the opportunity to provide feedback on the selection
    1. Feedback must be provided within 7 days
    2. Any feedback will be considered, but it might not influence the decision

Review Feedback

  1. The feedback is reviewed and a final decision is made
    1. The final decision is made by the Incubator task leader in agreement with ALs
    2. The work package leaders have to approve the activity selection



  • No labels