Contents
| Table of Contents |
|---|
Methodology
...
This page describes the development process used in the Incubator. The incubator . During the course of the GÉANT 4.3 project, the incubator runs a number of sequential cycles called "Activities". An activity cycle typically lasts 6 months. During such an activity cycle, an incubator activity team, or A-team, engages with a number of different activitiestopics, typically four to six, in parallel2 to 3, in parallel. The incubator has 2 A-teams working in parallel. As such, the Incubator can work on 4 to 6 topics in parallel during a 6 month activity cycle. The development process is loosely based on used for this engagement is a loose implementation of the Scrum development methodology, and roles and also some terminology used in this document are borrowed from this Agile methodology.
During the activity cycle the A-team uses Sprints too work on the topic. A sprint runs for 4 weeks. The Principe Investigator, or Magnum P.I., defines the work for a specific sprint, and its priorities. While the A-team itself is as stable as possible, a Mentor is a senior A-team member with specific expertise being brought in on a per activity basis to support the A-team as a subject matter expert. The A-team supports the PI by providing feedback to the work items defined. The team also makes estimates of how much work specific workitems are so the PI can decide priorities accordingly. In the spirit of the scrum methodology the A-team itself is responsible for planning of the work, based on the prioritized list of the PI.
During the activity, various artifacts are used to collect and report on the work being done. The Backlog holds all items the PI wants to work on. The PI may updated, change and (re)prioritize the Backlog at any given time, according to newly gained insights and priorities. The Sprint Backlog holds a selected set of Backlog items the A-team is working on for a specific sprint. The Sprint Backlog does not change over the course of a Sprint.
The Scrum methodology also includes a number of so called ceremonies, meetings who all have with a specific function.
on this Agile methodology.Below we describe the roles we use in the activity in more details, the structure of an activity, the artifacts we have in the activity and which ceremonies are part of the activity.
Contents
toc
Roles and responsibilities
Principal Investigator / Product Owner (Magnum P.I.)
The Magnum is the person mainly responsible to plan for defining the work and then prioritizing those tasks. The PI is clear on the goals of the activity and the contents of the productrepresents the stakeholders,e.g. the customer, market and organizations.
Main Incubator Board (MIB)
This board consists of many MIBs, who are senior members of the trust and identity community. The board helps the PIs to (better) articulate community and NREN needs. They will evaluate the results of each Sprint and provide feedback to the activity.
...
The members of the A-Team are the ones doing the real work within the activity. A team is typically made up of people with various skills and different expertise.
Scrum Master (SM)
The Scrum Master supports the activity by facilitating task communication, organizing meetings and allocating resources. Their major task is to keep organizational overhead away from the team and resolve impediments, so that the A-Team is able to focus on their actual work.
...
The Mentor is an experienced advisor who helps Magnum to plan the product and upcoming work by providing their technical knowledge and high-level view on the activity.
Activities
...
Plan Backlog
The Scrum Master, Mentor (optional) and Magnum meet at the start of each sprint to discuss the remaining work to be achieved within the Incubator cycle. New work items that were discovered will be added to the Activity Backlog as well as remaining items from the last Sprint.
Although it is fine to document future work, it should also be considered that it is possible to implement the backlog during the remaining time.
...