Difference between revisions of "Sprint retrospective"
| Line 1: | Line 1: | ||
[[Sprint retrospective]] is a [[meeting]] to overview a completed sprint, discuss and, possibly, document [[lessons learned]] i.e. find what activities and "things" the team has done well, what activities should be continued, and what "more" can be done to improve the next sprint. | [[Sprint retrospective]] is a [[meeting]] to overview a completed sprint, discuss and, possibly, document [[lessons learned]] i.e. find what activities and "things" the team has done well, what activities should be continued, and what "more" can be done to improve the next sprint. | ||
| + | |||
| + | ==Definitions== | ||
| + | According to the [[Agile Extension to the BABOK Guide|Agile Extension to the BABOK Guide (preview)]], | ||
| + | :[[Sprint Retrospective]]. The Sprint Retrospective is the main mechanism for taking the visibility that Scrum provides into areas of potential improvement, and turning it into results. | ||
| + | |||
| + | [[Category: Business Analysis]][[Category: Agile]][[Category: Articles]] | ||
Latest revision as of 19:40, 9 July 2020
Sprint retrospective is a meeting to overview a completed sprint, discuss and, possibly, document lessons learned i.e. find what activities and "things" the team has done well, what activities should be continued, and what "more" can be done to improve the next sprint.
Definitions
According to the Agile Extension to the BABOK Guide (preview),
- Sprint Retrospective. The Sprint Retrospective is the main mechanism for taking the visibility that Scrum provides into areas of potential improvement, and turning it into results.
