# Epic OP-7128 - Hybrid project management - combine traditional and agile project management

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-7128

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes | 2 |
| List |  |
| Target versions | Wish List |
| 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 |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

### User Problem

#### User

*What persona, persona segment, or customer type experiences the problem most acutely?*

  - Project manager
  - Project member
  - Product owner
  - Scrum Master
  - Scrum Team

#### Problem

*What problem or job does the user have?*

  - Traditional and agile planning does not work well together.

#### Pain

*What is the primary workaround that users perform that we could remove or replace? Why is it painful?*

  - Sprints are implemented as versions. But versions lack a lot of features
      - Are not shown in the Gantt chart
      - Can not be scheduled
      - Have no history
      - No email notifications
      - No customizations
  - When using work packages types e.g. Sprints for agile iterations we have the following limitatations
      - Agile iterations can not be easily added to an existing work breakdown structure

### Solution

*How do we solve the user’s problem. What is our “pain killer”? What must we achieve in the first version of the solution in order to achieve value for the user?*

  - We support several work breakdown structures per project
      - Traditional (hierarchical)
      - Agile (Iteration-based)
  - We have a  new paradigm for an "Iteration".
      - Milestone
      - Sprint
      - Step
      - Stage
      - ....
  - We can assign work packages to an Iteration
      - details view
      - full screen view
  - In-place creations of iterations (similar to versions)
  - We can manage iterations using boards (Actions iteratin board)

#### Out of Scope for the MVC

*What should NOT be in the minimal viable change, and can be considered for future iterations? Why? Please order them by importance.*

  - ...

#### Differentiation

*What do you believe will differentiate us from the current experience or competitive experiences?*

  - ...

#### Next iteration

*What is the next solution that would allow us to release meaningful customer value quickly?*

  - ...
  - 
### Launch and Growth

#### Measures

*How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?*

  - ...

#### Messaging

*If you were to write a press release, how would you describe the value to customers?*

<table><tbody><tr><th>Headline</th><td></td></tr><tr><th>First Paragraph</th><td></td></tr><tr><th>Customer Quote</th><td></td></tr></tbody></table>

#### Go to market

*How are you planning on getting this into users' hands?*
