Increase the level of transparency
The Sprint Backlog increases the transparency of information about what is the work planned and accomplished for the next Sprint by the Development Team.
In fact, the Sprint Backlog is a highly visible, it represents a snapshot of the work that the Development Team plans to accomplish during the next Sprint.
In general, when an artifact is easily inspected it means that a good level of transparency has been reached.
The elements of the Sprint Backlog
The Product Backlog items that are in scope for the Sprint represent the “What”. Whereas the plan of the Development Team used to accomplish the Sprint Goal represents the “How”. Moreover, each item of the Sprint Backlog has a description and an estimate. In fact, the Sprint Backlog is also called forecast.
It is important to notice that the Sprint Backlog also will contain at least one high improvement requirement related to the way the team works.
The process to manage the Sprint Backlog
The Sprint Backlog is maintained from Sprint Planning until the Sprint Review. The Development Team learns more about the work and modifies the Sprint Backlog accordingly during the Sprint. This process allows the Sprint Backlog to emerge during the Sprint.
The Sprint Backlog is owned only by the Development Team. As a result only the Development Team can change the Sprint Backlog. While work is performed or completed, the Development Team keeps updating the estimated remaining work.
Keep in mind
During the Sprint, the Development Team could find out that they have underestimated or overestimated a Product Backlog item. It can happen and it is pretty common. So, when a new work is required, the Development Team adds it to the Sprint Backlog. Whereas the elements of the plan that are considered unnecessary are removed. The Development Team modifies the Sprint Backlog throughout the Sprint.