Content
View differences
Updated by Niels Lindenthal 5 months ago
**User story 1**
**As** a Scrum master project owner or project stakeholder
**I want to** have dedicated sprint objects be able to track work around planned cadences like sprints or program increments (PIs)
**so that** I don't have to train my team to use versions as work can planned in a workaround. more organised and consistent way across structures
**User story 2** #### **Acceptance criteria**
**As an** IT manager responsible for Jira
**I want to** * There is a new object called "Iteration"
* An iteration belongs to have a dedicated sprint object
**So project but can be shared across different projects, even outside of the current projet hierarchy
* This works similar to Versions today
* This ensures that I** an iteration is available at multiple levels: a team, a project (or an ART or Solution) and even at a project portfolio level
* Each iteration has a start and finish date
* Work packages can migrate my sprints from Jira only be linked to OpenProject without loss a single iteration
* Existing project and work package permissions apply; users can only view and edit work packages in an iteration that they have access to
* There are new permissions to create iterations
* _\[open\] What new permissions do we need?_
* Each iteration has an overview page that provides a helpful summary of data. the status of the iteration, including:
* Start and end dates
* Status (upcomming/planned, on-going, late)
* Progress:
* A progress bar of the share of % of work packages based on each status
* The possibility to include and excluding closed work packages
* The different projects using this iteration
**As** a Scrum master
**I want to** have dedicated sprint objects
**so that** I don't have to train my team to use versions as
**User story 2**
**As an** IT manager responsible for Jira
**I want to**
* An iteration belongs
**So
* This works similar to Versions today
* This ensures
* Each iteration has a start and finish date
* Work packages
* Existing project and work package permissions apply; users can only view and edit work packages in an iteration that they have access to
* There are new permissions to create iterations
* _\[open\] What new permissions do we need?_
* Each iteration has an overview page that provides a helpful summary
* Start and end dates
* Status (upcomming/planned, on-going, late)
* Progress:
* A progress bar of the share of % of work packages based on each status
* The possibility to include and excluding closed work packages
* The different projects using this iteration