Who Can Change The Backlog During An Iteration

Who Holds the Power to Alter the Backlog’s Fate?

In the dynamic world of software development, the backlog holds the blueprint for your project’s future. But who wields the power to modify this sacred document mid-iteration? Join us as we unravel the mysteries and reveal the gatekeepers of the backlog.

Unraveling the Pain Points

Imagine the chaos if everyone could随意change the backlog on a whim. Unforeseen modifications would derail priorities, confuse team members, and leave the project in a perpetual state of uncertainty. Establishing clear guidelines for backlog alterations is crucial to maintain order and progress.

The Guardians of the Backlog

Within each Scrum team, certain individuals are entrusted with the responsibility to manage the backlog effectively. These individuals, known as the Product Owner and Scrum Master, collaborate closely to safeguard the integrity of this vital document.

Key Points to Remember

  • Product Owner: Ultimately, the Product Owner has the authority to decide on any changes to the backlog, ensuring that it aligns with the project’s vision and goals.
  • Scrum Master: The Scrum Master acts as a facilitator, guiding the team in following the Scrum process and ensuring that backlog modifications are handled smoothly and efficiently.
  • Team Collaboration: While the Product Owner and Scrum Master hold primary responsibility, the entire team should be involved in discussing and reviewing backlog changes to foster transparency and shared ownership.
Who Can Change The Backlog During An Iteration

Who Can Change the Backlog During an Iteration?

In agile software development, the backlog is a prioritized list of work items that need to be completed. During an iteration, the backlog can be changed to add or remove items, or to reprioritize the existing items.

Who has authority to change the backlog?

The following individuals or roles typically have the authority to change the backlog during an iteration:

  • Product Owner: The product owner is responsible for managing the backlog. They have the authority to add, remove, or reprioritize backlog items as needed to ensure that the team is working on the highest-priority items.

Product Owner

  • Scrum Master: The scrum master is responsible for facilitating the scrum process and ensuring that the team is following the agile principles. They can also make changes to the backlog if necessary, but they should typically consult with the product owner before doing so.

Scrum Master

  • Team: The team as a whole can also make changes to the backlog. However, these changes should typically be made through the product owner or scrum master.

When can the backlog be changed?

The backlog can be changed at any time during an iteration. However, it is generally best to avoid making major changes to the backlog during the middle of an iteration. This can disrupt the team’s flow and make it difficult to track progress.

How should the backlog be changed?

When making changes to the backlog, it is important to follow these best practices:

  • Communicate the changes to the team: Make sure that the team is aware of any changes to the backlog. This can be done through email, a team meeting, or another communication channel.
  • Document the changes: Keep a record of all changes made to the backlog. This will help to track progress and ensure that the changes are made in a consistent manner.
  • Consider the impact of the changes: Before making any changes to the backlog, consider the potential impact on the team and the project. Make sure that the changes will not disrupt the team’s flow or compromise the quality of the final product.


The ability to change the backlog during an iteration is a key aspect of agile software development. By following the best practices outlined in this article, you can ensure that your team is making changes to the backlog in a way that is efficient and effective.


  1. Who is responsible for prioritizing the backlog?
  • The product owner is responsible for prioritizing the backlog.
  1. Can the team make changes to the backlog without consulting the product owner?
  • Yes, but it is generally best to consult with the product owner before making any major changes to the backlog.
  1. How often should the backlog be reviewed?
  • The backlog should be reviewed regularly, but the frequency will vary depending on the project and the team.
  1. What is the best way to track changes to the backlog?
  • Use a tool such as a spreadsheet or a backlog management software to track changes to the backlog.
  1. How can I ensure that the backlog is always up-to-date?
  • Hold regular backlog grooming sessions to review the backlog and make any necessary changes.



You May Also Like