The difference between a Product Backlog, Release Backlog,
and Iteration Backlog is as follows:
- Product Backlog: The product backlog is a list of all the
product backlog items, such as user stories, requirements, or features, that
need to be delivered for a solution. The items in the product backlog are
ranked in order of business value or importance to the customer and are
continuously updated throughout a product’s life cycle or a project’s duration.
The business analysis effort for any product backlog item focuses on making
sure that product backlog items meet the definition of ready. Making a product backlog item ready helps the team refine its
business understanding of that item to the point where it has enough
information to begin development.
- Release Backlog: The release backlog is a subset of the
product backlog that contains the items that the team has committed to
delivering in a specific release. The release backlog is created by selecting,
in prioritized order, those items that the team is about to commit to deliver
in an upcoming release. The release backlog is continuously updated throughout
the release cycle.
- Iteration Backlog: The iteration backlog is a subset of
the release backlog that contains the items that the team has committed to
delivering in a specific iteration. The iteration backlog is created by
selecting, in prioritized order, those items that the team is about to commit
to deliver in an upcoming iteration. The iteration backlog is continuously
updated throughout the iteration cycle.
In summary, the product backlog is a list of all the items
that need to be delivered for a solution, the release backlog is a subset of
the product backlog that contains the items that the team has committed to
delivering in a specific release, and the iteration backlog is a subset of the
release backlog that contains the items that the team has committed to
delivering in a specific iteration.
Note: You may fnd this course of value:
