Content
View differences
Updated by Rosanna Sibora 3 days ago
Builds up on <mention class="mention" data-id="75445" data-type="work_package" data-text="##75445" data-display-id="75445">##75445</mention>
* These whiteboards can be added as widgets to the workspace overview, e.g. risk matrix, in order to be always visible on the start page for all team members.
* When creating a new board, a user is offered a template gallery alongside the blank-canvas option. Templates are grouped by planning practice (e.g. agile delivery, portfolio governance, risk management) and show a brief description of what the board is for and what axes it pre-configures.
* Selecting a template creates a board pre-populated with the appropriate axis configuration, lane labels, and suggested filters - which the user can adjust before or after creation without losing the template structure.
* Available templates for first iteration:
* A PI planning multi-team / multi-project template is available that pre-sets Y-axis to project/assignee (users can decide within the board between the two views: project or assignee) and X-axis to iteration/PI, with an unassigned lane, and a filter scoped to the relevant backlog.
* A risk management template is available that maps work packages to a likelihood-impact grid, placing them in quadrants that correspond to risk level, so that moving a card updates the relevant risk attributes on the work package.
* Users and administrators can save a configured board as a custom template, making it reusable across projects or teams within the instance.
* Users can adjust the whiteboards created based on templates.
* Templates are starting points, not locked configurations. A user who selects the PI planning template and then changes the X-axis to something other than iteration has not broken anything - they have customised it. The template is responsible for reducing the time to a useful first state, not for enforcing a process.
* Open question: should we allow whiteboard owners to lock templates, so that they cannot be changed in some cases?
* Open question: should we allow global admins to set some templates to not-editable at all and allow them to apply changes to the whiteboards which were created based on the locked, non-editable templates?
* There are two types of templates:
* Templates maintained by OpenProject, updated as planning practices evolve
* Custom templates, owned by the team or admin who created them
* These whiteboards can be added as widgets to the workspace overview, e.g. risk matrix, in order to be always visible on the start page for all team members.
* When creating a new board, a user is offered a template gallery alongside the blank-canvas option. Templates are grouped by planning practice (e.g. agile delivery, portfolio governance, risk management) and show a brief description of what the board is for and what axes it pre-configures.
* Selecting a template creates a board pre-populated with the appropriate axis configuration, lane labels, and suggested filters - which the user can adjust before or after creation without losing the template structure.
* Available templates for first iteration:
* A PI planning multi-team / multi-project template is available that pre-sets Y-axis to project/assignee (users can decide within the board between the two views: project or assignee) and X-axis to iteration/PI, with an unassigned lane, and a filter scoped to the relevant backlog.
* A risk management template is available that maps work packages to a likelihood-impact grid, placing them in quadrants that correspond to risk level, so that moving a card updates the relevant risk attributes on the work package.
* Users and administrators can save a configured board as a custom template, making it reusable across projects or teams within the instance.
* Users can adjust the whiteboards created based on templates.
* Templates are starting points, not locked configurations. A user who selects the PI planning template and then changes the X-axis to something other than iteration has not broken anything - they have customised it. The template is responsible for reducing the time to a useful first state, not for enforcing a process.
* Open question: should we allow whiteboard owners to lock templates, so that they cannot be changed in some cases?
* Open question: should we allow global admins to set some templates to not-editable at all and allow them to apply changes to the whiteboards which were created based on the locked, non-editable templates?
* There are two types of templates:
* Templates maintained by OpenProject, updated as planning practices evolve
* Custom templates, owned by the team or admin who created them