Task: Update product backlog

Take scope changes into account for planning the next sprints.

Purpose

Updating the backlog and adjusting the planning, taking into account changes emerged since the last sprint.

Relationships

Roles	Primary Performer: Product Owner	Additional Performers: Scrum Team Stakeholder
Inputs	Mandatory: Product Backlog	Optional: None
Outputs	Product Backlog

Steps

Collecting changes

Anyone, even an external stakeholder, can suggest changes to be added to the backlog.
Bugs and enhancement requests coming from partial product tests done at the end of previous sprint are also used to update the backlog.

These items are analyzed by the product owner prior to next sprint planning.

Reprioritizing items

Added items since previous sprint are prioritized in the backlog by the Product Owner prior to next sprint planning.

Reestimating items

Point-based estimation of new items added to the backlog is done by the team, ideally during a brainstorming with the Product Owner, one or two days prior to Sprint review.

Existing items can also be reestimated.

Key Considerations

During a sprint, no one can modify the selection of backlog items, done at the beginning of the sprint: the sprint scope remains unchanged.

However, anyone, even a external stakeholder, can suggest new items for later. These items are studied and prioritized by the product owner prior to next sprint planning.
Bugs and enhancement requests coming from partial product tests done at the end of previous sprint are also used to update the backlog.

This program and its materials are provided under the terms of the "Eclipse Public License v1.0" license.