Link Search Menu Expand Document

Evaluating Scrum Processes

Improvements can be made at any stage of the Agile sprint from sprint planning to retrospective. With short development cycles of 2-3 weeks, Scrum teams have more frequent opportunities to evaluate how the development process is working than they would in a waterfall development environment. The team has the opportunity to look at their processes throughout the sprint cycle and at the end of each sprint during the retrospective. They can think about how things could be better and make changes to be better.

Some of the issues that teams might be having are mentioned in the following table as well as references to the section(s) with more information on how fix them.

Problem Cause Associated Ceremony
User stories not being completed Unclear acceptance criteria. Stories not sized properly Sprint Planning or Backlog Refinement
  Team schedules not considered Spring Planning
  Team members unaware of blocking issues Daily Scrum
SprintPlanning
Sprint Review
  Issues from previous sprints not addressed. Retrospective
Team delivers incorrect/unacceptable features Stories not appropriately prioritized Spring Planning
Backlog Refinement
Sprint Review
  Features designed inappropriately Sprint Planning
Daily Scrum
Sprint Review