# Epic AGILE-265 - Enable 2D boards with configurable axes (e.g. to support PI planning)

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

## Detailed specification

### Motivation and background information

**Expected Outcome**

Planning participants leave a session with work packages already correctly assigned - to the right team, iteration, sprint, or any other dimension the organisation cares about - without a separate data-entry step. The board is not a presentation layer on top of OpenProject; it is OpenProject, just experienced spatially.

**Why This Matters**

Today, teams often plan visually on external whiteboards or sticky-note tools, then manually transcribe the outcomes back into OpenProject. This creates duplication, lag, and errors. Decisions made in the room don't reliably make it into the system, and the system doesn't reflect what was actually agreed. Manual transfer of information is very time consuming.

When this epic is complete, a programme increment planning session, a sprint planning meeting, or a cross-team dependency review can happen directly in OpenProject. Moving a card is the action - not a signal that someone should go update a field somewhere else.

**Example Use Cases**

A facilitator sets up a board before a PI planning event. Y-axis is set to team (Crazy Bears, Dolphins, A-Team, etc.), X-axis is set to iteration (PI 1, PI 2). Work packages from the relevant epics appear as cards, pre-positioned where their current values place them. Cards not yet assigned to a team or iteration appear in the unassigned space at the bottom or side. During the session, teams drag cards into their lane and iteration column or adds new cards. When the session ends, all work packages carry the correct team and iteration values in OpenProject - ready for tracking, reporting, and dependency management.

A portfolio manager set ups a whiteboard for risk management showing only work package types "risk". On the X-axis there is probability, on Y-axis impact.

### Acceptance criteria

*   A facilitator can configure a whiteboard by selecting any two attributes as axes - for example, team on the Y-axis and iteration (e.g. PI, sprint) on the X-axis - without engineering involvement or custom configuration.
    
*   Within the whiteboard there is also a space for work package cards not assigned to any of the attributes.
    
*   Work packages matching a saved filter appear on the board as cards in the correct area, or in an unassigned space if they lack a value for one or both axes.
    
    *   The scope can be defined per filter. This allows the user to import the necessary cards only.
        
*   Users can also add new work package cards, bot in the unassigned as assigned space.
    
*   Dragging a card from the unassigned lane into an area automatically writes the corresponding axis values back to the work package - with no additional save step required.
    
*   Moving a card between areas updates both axis attribute values simultaneously and is immediately visible to other participants in the session.
    
*   The board state reflects the live state of the data; someone viewing the work package list sees the same values as someone looking at the board.
    
*   The board allows real-time collaboration of multiple users.
    
*   Teams doing PI planning, sprint planning, or dependency mapping can complete their planning session in OpenProject and walk away with no manual follow-up data entry.
    
*   There is a new global module for interactive whiteboards.
    

**Open question - naming of this solution**

Proposed ideas:

*   Interactive whiteboard
    
*   Whiteboard
    
*   Advanced board
    
*   Matrix board
    
*   Grid board
    
*   Matrix collaboration board
    
*   Axis board
    
*   X/Y-Axis board
    
*   2D board

### Out of scope

Topics handled within separate work packages: 

  - Showing and defining dependencies between cards <mention class="mention" data-id="75450" data-type="work_package" data-text="##75450" data-display-id="75450">\#\#75450</mention>

  - Presets of whiteboards, e.g. for PI planning, for assigning tasks, for sprint planning, for risk management <mention class="mention" data-id="75452" data-type="work_package" data-text="##75452" data-display-id="75452">\#\#75452</mention>

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

## Planning

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

## 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 | Joules (39703), Express (8754), CEP (38264), Home (224196000003952096) |

## Estimates and progress

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

## Description

**As a** facilitator, team or programme coordinator planning work across multiple teams and iterations,  
**We want** to arrange work packages on a configurable two-axis interactive whiteboard where moving a card automatically updates the underlying data,  
**So that** planning sessions, workshops or backlog refinements become visual, collaborative, and directly connected to the work - eliminating the gap between what is discussed on a board and what is recorded in the system.
