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

Compare with Current View Page History

« Previous Version 7 Next »


Source: https://drive.google.com/file/d/1_e0enf-Df1uEoS-lakzaUTCkcKrTPl31/view?usp=sharing


  1. Each new idea that was not yet presented to the MIB will be pitched by the proposer
    1. Short pitch, 5 min presentation and 5 min questions
    2. Formerly pitched ideas won't be presented again (we expect MIBs to remember)
  2. The board briefly discusses the available ideas
    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
  3. It is checked if there are any risks that might put the implementation of the idea in danger
    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
  4. The MIBs prioritise all not blocked ideas 
    1. The goal is to select four ideas
    2. Each MIB got 4 votes, which might be differently weighted
    3. Additionally, two ideas will be selected for the TIM programme with the same procedure
    4. Proposal voting sheet: TII Activity Priority Template
      1. The vote should be anonymous
      2. Maybe use doodle as a tool
    5. Votes are conducted after the meeting, the MIBs have 48 hours to vote
  5. The votes of the MIBs are checked and assessed
    1. The assessment metric is not fixed
      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
  6. 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
  7. A list of four activities is proposed to the MIB & ALs, and proposer(s) (stakeholders)
  8. 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
  9. 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


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

  • No labels