Content
View differences
Updated by Rosanna Sibora about 1 month ago
The field "**Sharing**" for Sprints is quite ambiguous and doesn't clearly guide the user as to what it entails. The idea behind this field is for multiple teams across board to have access to a particular sprint. One shared goal but involving multiple teams because it has a broader scope. As a result, this field should reflect alignment and collaboration. It should also be easily understood as an Agile vocabulary.
**Field suggestions:**
* Cross-team with a drop-down list showing all teams to be involved.
* Collaborative
* Coordination or Coordinating with
* Multi-level
* Synchronized
* Cross-team sharing
* Share cross-team
* Applies to
Acceptance criteria:
* field was renamed (final naming tbd)
* add a help text explaining what it does
* "Indicates a sprint shared across certain teams or projects for synchronized program-level work, e.g. within SAFe Agile Release Train teams."
**Field suggestions:**
* Cross-team with a drop-down list showing all teams to be involved.
* Collaborative
* Coordination or Coordinating with
* Multi-level
* Synchronized
* Cross-team sharing
* Share cross-team
* Applies to
Acceptance criteria:
* field was renamed (final naming tbd)
* add a help text explaining what it does
* "Indicates a sprint shared across certain teams or projects for synchronized program-level work, e.g. within SAFe Agile Release Train teams."