Product Backlog
Last updated
Last updated
Goals
The second process step in the Application Development process is managing the product backlog. A product backlog in Scrum is a list of every task that must be done during the project timeline. The goal of this action is to use the information from the previous step (gathering the requirements) in order to create major tasks that can be included in the sprint planning. There are different methods that the team is using for organizing the product backlog. The important part here is that this is a continuous process step that starts over again after every sprint. And the timeline for the sprint execution is about 2 working weeks. Therefore, after this timeline, managing the product backlog starts again to ensure that the scrum team is using up-to-date information.
Scope
Working instruction covers enterprise application employees in Europe.
Responsibility
Product Owner: Manages the product backlog.
Manager: Discusses and analyses the product backlog. Also, he can be involved in the refinement session when the tasks are updated.
Scrum Development Team: Shares domain knowledge and can be involved in the backlog refinement session for a professional opinion.
Scrum Master: Participates in updating the product backlog items. (backlog refinement meeting)
Process
The Scrum Product Backlog is a list of everything that has to be accomplished as part of the project. The standard requirements specification artifacts are replaced by it. These elements could be of a technical nature, or they might be user-centric, such as user stories. In our case, the product backlog is separated into different methods, for example: creating a user story, story mapping, refinement session (grooming), and building a roadmap. The Scrum Product Owner is in charge of the Scrum Product Backlog. To have a comprehensive and extensive backlog, the Scrum Master, the Scrum Team, and the manager participate. Throughout the whole project, changes could be made to the Scrum Product Backlog. Existing requirements may be changed, modified, or even removed as required. New requirements may also be introduced.
