Content
View differences
Updated by Rosanna Sibora 5 days ago
Currently, OpenProject supports only a single active sprint per project at any given time. This constraint limits teams that operate multiple workstreams, sub-teams, or parallel delivery tracks within the same project.
Teams that manage multiple workstreams or release tracks within a single project face the following pain points under the current model:
* Only one sprint can be marked as "active" at a time, forcing teams to merge distinct workstreams into a single sprint or create separate projects as workarounds.
* Creating separate projects for parallel tracks fragments backlog visibility, makes cross-track reporting difficult, and increases administrative overhead.
* Scaled Agile frameworks (SAFe) and multi-team setups require simultaneous sprint execution, which is not supported today.
* Sprint boards, burndown charts, and velocity reports cannot reflect the reality of teams running parallel iterations.
Teams that manage multiple workstreams or release tracks within a single project face the following pain points under the current model:
* Only one sprint can be marked as "active" at a time, forcing teams to merge distinct workstreams into a single sprint or create separate projects as workarounds.
* Creating separate projects for parallel tracks fragments backlog visibility, makes cross-track reporting difficult, and increases administrative overhead.
* Scaled Agile frameworks (SAFe) and multi-team setups require simultaneous sprint execution, which is not supported today.
* Sprint boards, burndown charts, and velocity reports cannot reflect the reality of teams running parallel iterations.