+27 31 566 8000 summerschool@immedia.co.za

Today we participated in a brief course on Project Management. This included the topics of scrum product backlog, sprint planning, the actual sprint and the final review.

In the most basic definition, the Scrum Product Backlog is basically a list of all things that needs to be done within the project. It takes over the traditional requirements specification artifacts. These items can have a technical nature or can be user-centric e.g. in the form of user stories. The owner of the Scrum Product Backlog is the Scrum Product Owner. The Scrum Master, the Scrum Team, and other Stakeholders contribute it to have a broad and complete To-Do list.

Working with a Scrum Product Backlog doesn’t mean that the Scrum Team isn’t allowed to make and utilise other artifacts. Examples for additional artifacts could be a summary of the many user roles, workflow descriptions, user story boards, UI guidelines or user UI prototypes. Though, these artifacts do not replace the Scrum Product Backlog but complement and detail its content.

The Scrum Product Owner utilises the Scrum Product Backlog during the Sprint Planning Meeting to describe the top entries to the team. The Scrum Team then determines which items they can complete during the coming sprint.

Each Scrum Product Backlog has certain properties that differentiate it from a simple to-do list:
.An entry in the Scrum Product Backlog always add value for the customer
.The entries in the Scrum Product Backlog are prioritized and ordered accordingly
.The level of detail depends on the position of the entry within the Scrum Product Backlog
.All entries are estimated
.The Scrum Product Backlog is a living document
.There are no action-items or low-level tasks in the Scrum Product Backlog

Similar posts: