Product Backlog:
The product backlog is a look at what needs to be done for the product overall. It is a list made of all the different stories and epics(large stories) that must be implemented by the scrum team for the product to do finished properly.
Each backlog task has:
- An id based of its priority to the scrum team and client, along with the amount of effort the team estimates the stories to take
- A theme is assigned to each task, that relates different task
- Information on who as a user wants or needs this functionality
- What is wanted by the user in their story, and why the user wants to be able to do this with the product
- Notes by the scum team on the story
- Acceptance Criteria is whether or not task must be satisfied for the client to accept the product
- What sprint the task was added to, along with what sprint it was completed in
- An assigned story point value, which is the effort that is need to complete a task. The value is assessed by the scrum team.
Sprint Backlog:
The sprint backlog is specific to each sprint and contains a list of what different task need to be finished by the end of each sprint. During the sprint planning stage, the scrum team will fill the sprint backlog with tasks from the product backlog.
This helps to:
- Concentrate the scrum team on what they need to do for each sprint
- Makes it easier to break up a big project into smaller sprints or incremental steps
- Allows for client to see how different user stories are used to change or build the product
Overall, backlogs are there to help Agile teams to break up overbearing projects into smaller incremental steps. This allows projects to be worked on in an organized and scheduled manner.
Blog Citations:
Holzner S., Lest M., Moreira M. (2010). Agile For Dummies. Indianapolis, Indiana: Wiley Publishing.
No comments:
Post a Comment