...
It is the role of the Incubator to engage with new, yet relevant topics in the field of Trust and Identity for the Research and Education community.
New ideas are introduced by a proposer, who describes the idea in such detail that 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 Incubator collects all topic proposals in what is 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 (MIB). MIB representatives will evaluate and discuss the topics in the pipeline and provide feedback on their suitability and priority. The Work Package Leaders and the Incubator Task Leader will use this input to select new topics for the upcoming activity cycle.
Selected topics are then moved into the current activity cycle and the work on the activities is carried out using the T&I Incubator Development Process. During the development process, monthly intermediate results are showcased in Sprint Demos. PIs, MIBs, and other stakeholders or interested parties are welcome to join these meetings to provide feedback on the results so far.
...
New 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 Incubator. The idea is captured in the activity pipeline by filling in the Incubator Topic Template.
Information Gathering (APT-GET)
...
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 they can be acted upon by the team directly ('stories'). The Backlog will also contain less detailed tasks that will need further definition as the sprints progress ('epics').
...