Content
View differences
Updated by Rosanna Sibora about 1 month ago
**As a** Scrum Master or agile team member
**I want** a sprint board to be automatically created and configured when I start a sprint
**So that** I can immediately begin tracking work without manual setup and my team can visualize sprint progress from day one
## Business Context
Sprint boards are the central hub for daily team collaboration during active sprints. Automating their creation eliminates setup workload, ensures data reliability, and allows users to focus on delivering value rather than configuring tools.
## Acceptance Criteria
### Automatic Board Creation
* [ ] When user clicks "Start Sprint" from the backlog, system automatically creates a dedicated sprint board (based on status boards within OpenProject)
* [ ] User is automatically forwarded to the active sprint board
* [ ] Board is named using convention: "\[Project ID\] \[Sprint Name\]" Sprint \[Number\]" (e.g., "ABC Sprint 23")
\[open\] How do we handle naming of multi-project boards / sprints in future?
* [ ] Board is immediately accessible via the project's board section
* [ ] In the boards section users should see only boards of active sprints.
* [ ] Board creation happens seamlessly without additional user prompts or configuration steps
### Default Board Configuration
* [ ] Columns map to appropriate workflow statuses from the project work packages' workflows. We show automatically all statuses in columns. No status mapping at that stage (will follow in next iterations). project's workflow
* [ ] Board's filter automatically include:
* All issues assigned to the active sprint
* All issue types enabled for the project
\[open\] (TBD: Should epics be included per default? Should we allow to add epics to sprints? default?)
* [ ] Board shows sprint goal prominently at the top (if defined)
### Board Visibility & Access
* [ ] Board inherits project permissions automatically
* [ ] All project members can view the board immediately
* [ ] Board is marked as "Active Sprint Board" with visual indicator
* [ ] \[open\] Would it be possible to always use the same URL for the active Previous sprint board within a project? Use case: users often bookmark the URL. Working in scrum you want to always use the same board. Only the scope changes every two weeks. boards remain accessible but marked as "Completed" (TBD)
### Sprint Information Display
* [ ] Board header shows:
* Sprint name and number ("\[Project ID\] \[Sprint Name\]" Sprint \[Number\]" (e.g., "ABC Sprint 23"))
* Sprint duration (start date - end date)
* Days remaining in sprint
* Sprint goal
* [ ] Board displays real-time sprint metrics:
* Number of issues in each column
* Total number of story points in each column
### Out of scope
Will be handled using different work packages.
* [ ] Swimlanes
* [ ] Defining quick filters in the board Custom sprint name
* [ ] Status mapping Defining quick filters in the board columns
**I want** a sprint board to be automatically created and configured when I start a sprint
**So that** I can immediately begin tracking work without manual setup and my team can visualize sprint progress from day one
## Business Context
Sprint boards are the central hub for daily team collaboration during active sprints. Automating their creation eliminates setup workload, ensures data reliability, and allows users to focus on delivering value rather than configuring tools.
## Acceptance Criteria
### Automatic Board Creation
* [ ] When user clicks "Start Sprint" from the backlog, system automatically creates a dedicated sprint board (based on status boards within OpenProject)
* [ ] User is automatically forwarded to the active sprint board
* [ ] Board is named using convention: "\[Project ID\] \[Sprint Name\]"
\[open\] How do we handle naming of multi-project boards / sprints in future?
* [ ] Board is immediately accessible via the project's board section
* [ ] In the boards section users should see only boards of active sprints.
* [ ] Board creation happens seamlessly without additional user prompts or configuration steps
### Default Board Configuration
* [ ] Columns map to appropriate workflow statuses from the project work packages' workflows. We show automatically all statuses in columns. No status mapping at that stage (will follow in next iterations).
* [ ] Board's filter automatically include:
* All issues assigned to the active sprint
* All issue types enabled for the project
\[open\]
* [ ] Board shows sprint goal prominently at the top (if defined)
### Board Visibility & Access
* [ ] Board inherits project permissions automatically
* [ ] All project members can view the board immediately
* [ ] Board is marked as "Active Sprint Board" with visual indicator
* [ ] \[open\] Would it be possible to always use the same URL for the active
### Sprint Information Display
* [ ] Board header shows:
* Sprint name and number ("\[Project ID\] \[Sprint Name\]"
* Sprint duration (start date - end date)
* Days remaining in sprint
* Sprint goal
* [ ] Board displays real-time sprint metrics:
* Number of issues in each column
* Total number of story points in each column
### Out of scope
Will be handled using different work packages.
* [ ] Swimlanes
* [ ] Defining quick filters in the board
* [ ] Status mapping