An ever-evolving list of product requirements, prioritized by the customer (or customer representative), that conveys to an Agile team which features to implement first. Agile projects typically employ a top level backlog, known as a product backlog or release backlog, and each Agile team working on a project typically creates a backlog for each development iteration, known as an iteration backlog or sprint backlog.

At either the release level or iteration level, a backlog typically comprises features or requirements, often expressed in terms of user stories, that may be assigned estimates (e.g., in points or hours) by the development team. The customer or customer representative prioritizes the items in the backlog (and may assign them business value).

This entry was posted in b. Bookmark the permalink.

2 Responses to Backlog

  1. Pingback: Being a Product Manager | Bryan Friedman: Clouding Up

  2. Pingback: From Component Teams To Feature Teams

Leave a Reply

Your email address will not be published. Required fields are marked *