# Epic AGILE-267 - Provide pre-configured 2D board templates so users can start from a meaningful structure immediately

Project: Stream agile
Status: new
URL: https://community.openproject.org/work_packages/AGILE-267

## Detailed specification

### Motivation and background information

**Outcome**

Adopting structured planning practices in OpenProject stops being a configuration task and becomes a one-click decision. Teams who would not have invested time in setup can now benefit from the same board-based planning that more experienced users have configured manually. Best practices are embedded in the product, not locked in individual users' institutional knowledge.

**Use Cases**

  - Usage of pre-configured whiteboards for planning session.

  - Adding pre-configured whiteboards to dashboard, e.g. risk management.

**Background**

A powerful, flexible board is only valuable if people actually use it. For many users, the blank-slate configuration experience is the barrier. They know they want to do PI planning or a risk review, but they don't know which attributes to map to which axis, what filters to apply, or how to label their lanes. The result is that they fall back to external tools — spreadsheets, whiteboards, sticky notes - and the planning outcome never makes it into OpenProject.

Pre-configured templates solve this by encoding the answer to "how do I set this up" directly into the product. A team lead who has never run a PI planning session in OpenProject can select the PI planning template, point it at the right projects, and have a working whiteboard in front of their team within a minute.

### Acceptance criteria

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

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q3 |
| Date |  |
| Votes |  |
| List | RM Jira exit, SAFe |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance | Medium — Useful Mid-Term |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Rosanna Sibora |
| Feature Lead |  |
| Designer | Julia Racsko |
| Developers | OP Dev Polaris Team |
| Requested by |  |
| Interest by | Home (224196000003952096) |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | 50d 0h |

## Description

**As** a facilitator, planner, programme manager, or team lead setting up a planning session or a whiteboard in OpenProject,  
**We want** to choose from a set of ready-made whiteboard configurations that reflect common planning practices - rather than building axis, filter, and lane structure from scratch every time,  
**So that** the time between deciding to run a planning session or using a whiteboard and actually starting it is measured in seconds, not hours.
