From the course: Agile Software Development: Scrum for Developers
Unlock the full course today
Join today to access over 24,700 courses taught by industry experts.
Tracking retrospective items
From the course: Agile Software Development: Scrum for Developers
Tracking retrospective items
- [Instructor] Scrum does not enforce any specific approach to managing retrospective items. The only requirement per Scrum guide is to have a timeboxed sprint retrospective event with a goal to inspect individuals, interactions, processes, tools, and their definition of done. The Agile fitness team came up with an approach to document and track retrospective items separately in another backlog. They identified five retrospective items. The list includes backlog items such as fixing broken bills, improving the definition of done, et cetera. They picked two of the most important and actionable retrospective items and added those items to a board just for retrospective items. Many Scrum teams include retrospective items as backlog items in their regular sprint. You can also create retrospective items as regular tasks. As long as the retrospective items are actionable and are being tracked and managed efficiently, you should…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.