Content
View differences
Updated by Jens Ulferts 2 days ago
**As** a Scrum Master or Team Lead
**I want to** independently manage my team’s execution lifecycle, sprint goal, and completion status within a centrally governed shared ART sprint cadence
**so that** my team can execute its sprint autonomously while remaining aligned with the common planning and governance framework of the ART.
# **Acceptance criteria**
* When sharing sprints e.g. within an ART/Program, a user having `share_sprints` permission can choose between two options on what that sharing includes:
* centrally managed - already existing
* team managed - new, this feature
* Sprints being team managed receive their own started at and completed at timestamps as well as their own status. Depending on the setting, a sprint's properties are either provided by the sharer or can be set by the receiver. If they are the same, changing them will change them for all receivers. This is what is currently done. The following table shows where the team managed sprints will be different.
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">Property</p></th><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">centrally managed</p></th><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">team managed</p></th></tr></thead><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">name</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers </p></td><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers </p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">start date (planned)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers </p></td><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">finish date (planned)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">status</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">started at (actual)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">completed at (actual)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">goal</p></th><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr></tbody></table></figure>
* On a team managed sprint, the following actions will only affect the sprint within the project the action is carried out on. The same sprint in other projects including the one shared from are not affected:
* Starting a sprint
* Completing a sprint and moving leftover work packages to a new destination.
* With either option, the planned start and finish dates, the cadence, is provided by the project shared from. Changing the dates in any project continues to be possible for people having the necessary permissions. Doing so will change it in all projects.
* The central vs team option affects all shared sprints. It is not possible to select different options between different sprints.
* Sprint reports based on a team managed sprint use the start and completion date of the project the report is generated for.
* The divergence from the centrally configured cadences is visible in a project (sprint report and backlogs view)
* \[open\] Sprint reports already show the difference. We might want to adopt the coloring schema already in place for overdue work packages. This might be useful regardless of this feature.
* Work packages continue to only be assignable to a sprint that is not completed. Since the completion state can now become different between projects it needs to be checked per project.
* The backlogs project setting ('Sprint sharing' tab) provides the two options. This is the place where the selection is made. The options are only displayed in case one of the two sharing options are active.
* Already existing sprints in receiving projects, are affected when changing the team vs centrally managed option in the project administration. option. The user is informed of the changes being carried out beforehand.
beforehand and needs to confirm a modal. The modal is only displayed if a conflict is identified.
* from centrally to team managed - receive the centrally managed dates and status as their own.
* from team to centrally managed - loose their own dates and status. This can change the currently active sprint. Work packages are not moved automatically.
# **Technical notes**
1. <mention class="mention" data-id="79179" data-type="work_package" data-text="###AGILE-412" data-display-id="AGILE-412">###AGILE-412</mention>is ideally carried out before.
# **Permissions and visibility considerations**
* `share_sprints` and `start_complete_sprint` are used for the actions same as before. But the project the permission needs to be granted on depends on whether a sprint is centrally or team managed.
# **Translation considerations**
Key terms to validate in the relevant UI translations:
* Sprint
* Sprint Goal
* Sprint Start
* Sprint Close
* Team Sprint
* Planning Interval
* ART (Agile Release Train)
# **Out of scope**
1. If sprints are team managed, there is guard agains a team starting a sprint out of order.
2. Definition of ART cadence structure.
3. Program Increment planning processes.
4. Portfolio-level planning and governance.
5. Cross-team metric aggregation and reporting.
6. Team capacity management.
7. Changes to sprint planning workflows unrelated to team-level sprint execution.
**I want to** independently manage my team’s execution lifecycle, sprint goal, and completion status within a centrally governed shared ART sprint cadence
**so that** my team can execute its sprint autonomously while remaining aligned with the common planning and governance framework of the ART.
# **Acceptance criteria**
* When sharing sprints e.g. within an ART/Program, a user having `share_sprints` permission can choose between two options on what that sharing includes:
* centrally managed - already existing
* team managed - new, this feature
* Sprints being team managed receive their own started at and completed at timestamps as well as their own status. Depending on the setting, a sprint's properties are either provided by the sharer or can be set by the receiver. If they are the same, changing them will change them for all receivers. This is what is currently done. The following table shows where the team managed sprints will be different.
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">Property</p></th><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">centrally managed</p></th><th class="op-uc-table--cell op-uc-table--cell_head" scope="col"><p class="op-uc-p">team managed</p></th></tr></thead><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">name</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers </p></td><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers </p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">start date (planned)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers </p></td><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">finish date (planned)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">status</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">started at (actual)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">completed at (actual)</p></th><td class="op-uc-table--cell"><p class="op-uc-p">same for all receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head" scope="row"><p class="op-uc-p">goal</p></th><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td><td class="op-uc-table--cell"><p class="op-uc-p">different between receivers</p></td></tr></tbody></table></figure>
* On a team managed sprint, the following actions will only affect the sprint within the project the action is carried out on. The same sprint in other projects including the one shared from are not affected:
* Starting a sprint
* Completing a sprint and moving leftover work packages to a new destination.
* With either option, the planned start and finish dates, the cadence, is provided by the project shared from. Changing the dates in any project continues to be possible for people having the necessary permissions. Doing so will change it in all projects.
* The central vs team option affects all shared sprints. It is not possible to select different options between different sprints.
* Sprint reports based on a team managed sprint use the start and completion date of the project the report is generated for.
* The divergence from the centrally configured cadences is visible in a project (sprint report and backlogs view)
* \[open\] Sprint reports already show the difference. We might want to adopt the coloring schema already in place for overdue work packages. This might be useful regardless of this feature.
* Work packages continue to only be assignable to a sprint that is not completed. Since the completion state can now become different between projects it needs to be checked per project.
* The backlogs project setting ('Sprint sharing' tab) provides the two options. This is the place where the selection is made. The options are only displayed in case one of the two sharing options are active.
* Already existing sprints in receiving projects, are affected when changing the team vs centrally managed option in the project administration.
1. <mention class="mention" data-id="79179" data-type="work_package" data-text="###AGILE-412" data-display-id="AGILE-412">###AGILE-412</mention>is ideally carried out before.
# **Permissions and visibility considerations**
* `share_sprints` and `start_complete_sprint` are used for the actions same as before. But the project the permission needs to be granted on depends on whether a sprint is centrally or team managed.
# **Translation considerations**
Key terms to validate in the relevant UI translations:
* Sprint
* Sprint Goal
* Sprint Start
* Sprint Close
* Team Sprint
* Planning Interval
* ART (Agile Release Train)
# **Out of scope**
1. If sprints are team managed, there is guard agains a team starting a sprint out of order.
2. Definition of ART cadence structure.
3. Program Increment planning processes.
4. Portfolio-level planning and governance.
5. Cross-team metric aggregation and reporting.
6. Team capacity management.
7. Changes to sprint planning workflows unrelated to team-level sprint execution.