Expanding to Small Groups of Agile Teams

Teams should start feature (or epic) work with a problem definition step, which includes defining the user outcomes and success metrics. This step takes place ahead of any work that the team picks up and captures the context of the work that the team is about to engage in. Ideally, Agile teams work...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Hauptverfasser: Montalbano, Joe, Lehman, Brad, Lauren, Mix, Sandra, Dorr, Galm, Ed, Hohmann, Luke
Format: Buchkapitel
Sprache:eng
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:Teams should start feature (or epic) work with a problem definition step, which includes defining the user outcomes and success metrics. This step takes place ahead of any work that the team picks up and captures the context of the work that the team is about to engage in. Ideally, Agile teams work on a problem from the end to end, which is true in Human-Centered Agile as well. However, when scaling to a group of coordinated teams, having a single team work through the features end to end becomes increasingly challenging. The whole idea of Agile is for teams to manage themselves. However, before teams start work, a clear understanding of the management's expectations of what the team will deliver as well as an understanding of any constraints or limitations, such as other work they will be expected to perform.
DOI:10.4324/9781003188520-14