...

Introduction

The Trust and Identity Incubator is a novel way for dealing of working with new and potentially disruptive T&I topics in the GÉANT the GN4-3 project. The incubator concerns itself scope of the Incubator is not only with on topics that focus on technical aspects, but may also include other topics areas around service development and improvement, like such as business case development, or e.g. improvements in privacy or and data protection, etc. During the course of the GÉANT 4.GN4-3 project, the Incubator runs will run a number of sequential cycles called "Activities". An activity typically lasts 6 months, iterations called cycles, which typically last 6 months. For each cycle, multiple Activities are chosen during which a team focuses on a number of topics. Once a topic specific topic with-well defined scope and goals. Once an activity is selected for an activity a cycle, it becomes part of the T&I Incubator Development Process. This document describes how new topics are introduced in an activity cycle and how evaluation of the topics takes placeis carried out. 

Methodology

It is the role of the Incubator to engage with new, yet relevant topics in the field of Trust and Identity in for the Research and CollaborationEducation community.
New ideas are introduced by a proposer, who describes the idea to in such detail that is it can be shared and understood. The Incubator provides a template for recording such new ideas. In this template the proposer is asked to describe various aspects of the idea, including:

• the The problem it seeks to resolve,.
• relevant Relevant stakeholders,.
• technical Technical details,.
• impact Impact on privacy and data protection,.
• a A potential business case and.
• how How the idea may be sustained in case it becomes a service.

Clearly, depending Depending on the idea and its maturity, it may not yet be possible to answer all of the above questions to with the same level of detail.

Proposers of new ideas may include Service managers participants of Tasks in the Trust and Identity task, the Trust and Identity task activity leadersthe T&I Work Package (WP5) e.g. service owners, task and team leads and other participants, members of the Main Incubator Board , who we will introduce shortly, and also NRENs may (MIB) etc. In general, other GÉANT project stakeholders such as NRENs may also suggest new topics directly. In all cases, it the topic objective must be clear topics are , sufficiently novel and potentially disruptive and as such cannot be developed as part of the regular service improvement work that is already taking place in the service delivery tasks of the Trust and Identity work package. When Service Activities propose new topics Work Package. When a proposed topic is related to a service delivered in the T&I Work Package it is expected that the work in the incubator will be done in close collaboration between the Service activity service team and the Incubator, where service teams are one of the activity stakeholders. In the case NRENs suggest a topicof topics suggested by NRENs, it is required such a suggestion is made that such suggestions be submitted  by at least 2 two collaborating NRENs, who must also provide one or more PI's Principal Investigators (PIs) to the incubator Activity (The PIs the PI’s time will be supported from through the Incubator).

The Incubator collects all topics topic proposals in what is called the Activity "pipeline". At each end of an known as the activity pipeline. During each preparation phase for the next incubator cycle, the topics in the activity pipeline are evaluated by the Main Incubator Board (MIBs), an advisory board made up of a number of senior members from the European NREN community. In addition, the advisory board also has a member from a non EU NREN (Internet2), a university CIO and a representative of the research communities. The MIBs MIB). MIB representatives will evaluate and discuss the topics in the pipeline , and based on that prioritize the topicsprovide feedback on their suitability and priority. The Work Package leader Leaders and the Incubator Task Leader will use this prioritized list input to select new topics for the upcoming incubator activity cycle.

Selected topics are then moved into the current activity cycle and the work on the topics activities is executed carried out using the T&I Incubator Development Process. During the development process, monthly intermediate results are showcased in so called Sprint Demo'sDemos. PIs, MIBs, and others other stakeholders or interested parties are welcome to join these meetings to provide feedback on the results so far.

After an activity cycle ends, the results of the topics are evaluated. The results of this evaluation may be one of the below:are evaluated, based on which a decision is made on whether to continue an activity and how it should be followed up, for example:

• The Activity An activity is continued, but with a different focus. The topic, with its new focus, is described in a template, and added to the activity pipeline;.
• The activity is moved into one of the existing Results of the Activity are used for a (new) service delivered in the Trust & Identity Service activitiesWork Package. Depending on size and impact, the Service Activity Manager a service owner may want to introduce this new features by using the GÉANT PLM process. This is out of scope for the T&I Incubator;The activity is moved into a new Trust & Identity Service activity. A (newly appointed) Service Activity Manager may want to introduce this new features by the results in a new feature for the service and using the GÉANT PLM process where applicable. This is out of scope for the T&I Incubator;.
• The activity Activity is moved out of the GÉANT project GN4-3project to be continued as a separate (open source) software project;.
• The activity Activity is stopped and will not be continued. Its results may still be found in

When a new cycle starts topics me be continued, or new topics may be introduced.

Figure 1 presents Figure 1 present a more detailed view of the various steps in the Incubator an Activity.

Image Modified

Figure 1: Incubator Activity activity steps and artifacts

Roles & Responsibilities

The following roles are important in the T&I Incubator planning and review process.

Main Incubator Board (MIB)

The MIB aims to represent a broad view on Trust and Identity related developments in R&E.  MIB members are senior subject matter experts from the European NREN trust and identity community. In addition, the MIB currently also includes a member from a non-EU NREN (Internet2), a university CIO and a representative of the research communities. They will evaluate new ideas and provide advice to the work package lead. They are also responsible for reviewing activities at the end of each incubator cycle and providing recommendations on how to proceed.

Incubator Team

The incubator team  will help the proposer formulate their idea and pitch it to the MIB. Although the MIB gives recommendations regarding proposed topics and whether they are fit to be included in an activity cycle, the final decision on this is made by the task leader. 

Proposer

A person who proposes an idea for a potential activity to the Incubator. A proposer can be any T&I community member backed by at least two NRENs or one of the members of the MIB.

Activity Steps

Propose

...

Idea (APT-BUILD)

The MIBs, Activity leads and Service leads are given the opportunity to add topicsNew topics may be proposed as described. This is an ongoing process which may happen at any time during the various phases in the Incubator.
A proposer describes a new idea for the incubatorIncubator.  The  The idea is captured in the Activity activity pipeline by filling in the Incubator Topic Template.

Information

...

Gathering (APT-GET)

About two months before the start of a new Incubator Activity cycleCycle, the Incubator pipeline is temporarily frozen. The information Information on all topics in the Activity activity pipeline is validated and, if needed, completed.

Pitch &

...

Discuss Idea (APT check)

MIB members will first individually review and prioritise topics in the Activity activity pipeline using the MOSCOW methodology. The Activity pipeline items are then discussed by the MIBs MIB in an Incubator Board meeting. MIBs may modify their MOSCOW score after discussion. Meeting.
The discussion yields a prioritized list of topics, by counting the number of Must, Could, Should and Wont statements from individual MIB members. This list is used as the recommendation from the MIBs to selecting topics into the new Incubator feedback on proposals and priorities , which is consolidated into   recommendations f that will be considered when selecting topics to be included in the new activity cycle.

Topic

...

Selection

The topics for the new Activity activity cycle are selected by the Incubator managementTrust and Identity Work Package Leader and Incubator Task Leader. Selection typically follows the recommendations of the MIB, however deviations may occur for operational reasons, e.g. in case of inability to resource certain topics.

Prepare

...

Activity (APT

...

Install)

In the preparatory phase of an activity, the Incubator management Task Leader will:

• Identify a POPrincipal Investigator (PI).
• Identify a Mentor.
• Assign an activity the Activity to a team (Alpha/Blue/Finland).
• Assess if skill set the skillset of the team is aligned with the subject matter

Once selected the PO of an activity will:

• Describe Activity Backlog items, including a definition DOD (Definition of Done)

• .

The above roles are described in more detail in the  T&I Incubator Development Process.

Following this, it is the responsibility of the PI to describe the Activity Backlog tasks, including acceptance criteria. This initial backlog is based on the activity description and shall include at least all tasks necessary to implement a minimum viable product according to the Activity’s goals.The Backlog will consist of a number of tasks that have been defined in such detail that The backlog will typically consists of a number of items that have been defined to such detail they can be acted upon by the team directly ('stories'). The backlog Backlog will also contain items defined in less detail which less detailed  tasks that will need further detail later on definition as the sprints are progressing progress ('epics').

Onboard New Activities

Once a new cycle startsAs soon as a backlog exists, the team will:

• Discuss the Backlog items with the PO
• Assign each item in the Backlog a number of points to indicate the (relative) amount of work. This is done for BOTH the stories as well as the epics. Clearly, estimating work for epics is indicative, but should give a rough idea of how much work an epic entails.

Onboard new activities

Once the sprint backlog is filled, a PO is selected and the stories all have story points a sprint is started by creating a sprint backlog. The process that starts now is described in the T&I Incubator Development Process.

Sprint

See the T&I Incubator Development Process.

Discuss existing activities

...

will start working on the prepared activities. A kick-off meeting will be held in which the PI presents the idea, concept and initial backlog to the team. The team ensures that the Backlog is sufficiently prepared and understood to be used in the first Sprint Planning. The team agrees on meeting slots and tools, if necessary. 

Sprints

Each activity cycle consists of six sprints, each generating a new activity increment. The process for a single sprint is described in the T&I Incubator Development Process.

Discuss Existing Activities

Once the last sprint of an activity cycle is completed, all activities are reviewed by the MIB. The results of an Activity will be presented comprehensively in the last Sprint Demo by the respective PI. Following this, the MIB discusses and recommends how to proceed with the Activity.

There are three possible outcomes to a completed activity once an activity cycle is completed:

• Transfer Activity
  The Activity is mature enough to be moved out of the Incubator to another (service) task, to the community that requested it etc.. See 4.9 for further details.
• Continue Activity
  If the Activity is not mature enough to be transferred, it may be granted another Incubator cycle, so it is proposed as a new topic in the activity pipeline. The proposed topic has to achieve new goals and might be led by a different PI.
• Stop Activity
  It is decided that the Activity will be discontinued, either because it was a one-time project, or because the idea did not produce the expected results or the results failed to convince the MIB. The results of the Activity and in this case the reasons for its termination are documented.

The task leader might define an alternative procedure if necessary for specific cases.

Transfer Activity

The results of successfully completed activities maybe transferred internally (to other GN4-3 tasks) or externally.

Internal transfer:

• Transferred to another GN4-3 task;
• Approval of work package and task leader of the target WP/Task is necessary;
• Handover of:
• All results produced;
• Comprehensive documentation; 
• Introduction to the results delivered by the team responsible.

External transfer:

• Transferred to any external party, for example another project, to an open source software project or perhaps another organisation to take care of the resulting artifacts.
• Needs to be approved by WP5 Leaders.

Once the handover is completed, the Incubator Task is no longer responsible for the activity. Any later requests regarding the Activity are out of scope unless reintroduced as a new topic within the activity pipeline.