The iteration retrospective is used by Agile teams to reflect on the iteration just completed and to derive new ideas to improve the team’s process. When issues have been identified, root cause analysis is performed, potential corrective actions are discussed, and improvement Stories are entered into the Team Backlog. The qualitative part discusses the team practices and the specific challenges that occurred during the last iteration or two. The quantitative review gathers and evaluates any metrics the team is using to measure its performance. Timeboxed to an hour or less, each retrospective seeks to uncover what’s working well, what isn’t, and what the team can do better next time.Įach retrospective yields both quantitative and qualitative insights. The Iteration Retrospective is a regular event where Agile Team members discuss the results of the Iteration, review their practices, and identify ways to improve.Īt the end of each iteration, Agile teams that apply ScrumXP (and many teams who use Kanban) gather for an iteration retrospective. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |