Simple Scrum Process

Process

On the project level, a Product Backlog is managed in the governance repository.
The Product Backlog consists of Features. For each Feature, there is a Label in the issue tracker.
A Feature is broken down into Feature Parts. A Feature Part is represented as an issue in the tracker.
A Feature Part contains the following information in its description field, structured as Label + ": " + Value:
Owner: toolchain // the value is the name of the repository
Estimate: 25 // The estimate in SP
Priority: 5 // A priority value from 0 (lowest) to 10 (highest)
There may be a special Feature part with the title starting with "Summary:". This can be used to describe the featrue in detail, using Bernd's template. This Feature has no label-value pairs in its description.
A feature part can use a user story template as the title, e.g.: "As a {ROLE}, I want {GOAL}, [so that {BENEFIT}]" (optional)
For the time being, a Story Point corresponds to one Person-Day.

Each WP has a wiki page describing the interface to product backlog.
For each assigned Feature Part, there is a corresponding label in the format "##: ", where ## is the ID of the corresponding feature part ID in the governance tracker. The free text can be used to describe the feature part. (But the reporting tool will match labels by using the ID only).
The Feature Part is broken down into Backlog Issues, which are represented by tracker issues, that are labeled with the corresponding feature part label.
A Backlog issue contains the following label-value-pairs:
- Estimate: 5 // The estimate in SP
Milestones are used for tracking sprint cycles. They must be named as follows: Tool Sprint 15 (Ends 18-07-14). Backlog issues are assigned to Milestones.

To track progress, we need to know which organizations users are assigned to. There will be a dedicated wiki page with name-value pairs:

@jastram Formal Mind

@BerndHekele DB

Using these conventions, the following information will be available via reports (these are just examples):

For each WP: List of Feature Parts, ordered by priority, with their associated issues. The Project estimate and the sum of SPs from the issues is shown. A warning is shown if no label for a given Feature Part exists.
For each Partner: The breakdown of their effort for each sprint cycle by WP, and within the WP by Feature Part.
Up to date status of what every individual is working on