Product Backlog
The Product Backlog is an ordered collection of all known work to be done for the product. It is dynamic and never complete, constantly changing to keep the product appropriate, competitive, and useful.
The more a product is developed and used, and feedback is provided, the backlog becomes better defined, including product features, enhancements and fixes.
The Product Owner is responsible for the Product Backlog management, with the Development Team responsible for all estimates of the work.
Sprint Backlog
The Sprint Backlog is a collection of the work selected from the Product Backlog, along with a plan for how the work will be completed and the Sprint Goal accomplished.
All work required to accomplish the Sprint Goal should be in the Sprint Backlog and can be added as new work is discovered. Work deemed unnecessary can be removed. There should also be at least one improvement identified in the previous Sprint Retrospective in the Sprint Backlog so that the team is continuously improving.
The Development Team is responsible for the Sprint Backlog and measured regularly at the Daily Scrum to determine progress through the selected work and towards the Sprint Goal.
Increment
The Increment at the end of a Sprint is the sum of the work completed from the Product Backlog in the Sprint and the Increments all previous Sprints.
The Increment must be potentially releasable and done with respect to the ‘Definition of Done’. It is the Product Owner’s decision whether the Increment is released at each Sprint.
Scrum Framework
Scrum Framework – Artifacts (Here)