backlog là gì

From Wikipedia, the không tính tiền encyclopedia

Bạn đang xem: backlog là gì

Within agile project management, product backlog refers to lớn a prioritized list of functionality which a product should contain. It is sometimes referred to lớn as a to-do list,[1] and is considered an 'artifact' (a size of documentation) within the scrum software development framework.[2] The product backlog is referred to lớn with different names in different project management frameworks, such as product backlog in scrum,[2][3] work item list in disciplined agile,[3][4] and option pool in lean.[3] In the scrum framework, creation and continuous maintenance of the product backlog is part of the responsibility of the product owner.[5]

A sprint backlog[6] consists of selected elements from the product backlog which are planned to lớn be developed within that particular sprint.

In scrum, coherence is defined as a measure of the relationships between backlog items which make them worthy of consideration as a whole.[7]

Xem thêm: drawer là gì


The agile product backlog in scrum is a prioritized features list, containing short descriptions of all functionality desired in the product. When applying the scrum or other agile development methodology, it is not necessary to lớn start a project with a lengthy, upfront effort to lớn document all requirements as is more common with traditional project management methods following the waterfall model.[citation needed] Instead, a scrum team and its product owner will typically begin by writing down every relevant feature they can think of for the project's agile backlog prioritization, and the initial agile product backlog is almost always more kêu ca enough for a first sprint. The scrum product backlog is then allowed to lớn grow further throughout the project life cycle and change as more is learned about the product and its customers.

A typical scrum backlog comprises the following different types of items:[clarification needed]

Xem thêm: strengthening là gì

  1. Features
  2. Bugs
  3. Technical work
  4. Knowledge acquisition