Learning Scrum - The Product Backlog

转载 2011年10月16日 06:39:37


The Product Backlog is the master list of all functionality desired in the product. When using Scrum, it is not necessary to start a project with a lengthy, upfront effort to document all requirements. Typically, a Scrum team and its product owner begin by writing down everything they can think of easily. This is almost always more than enough for a first sprint. The Product Backlog is then allowed to grow and change as more is learned about the product and its customers.

Product backlog items can be technical tasks ("Refactor the Login class to throw an exception") or more user-centric ("Allow undo on the setup screen"). My preference is to express the product backlog in the form of user stories, which are a technique borrowed from Extreme Programming, another agile process.

The product owner shows up at the sprint planning meeting with the prioritized product backlog and describes the top items to the team. The team then determines which items they can complete during the coming sprint. The team then moves items from the Product Backlog to the Sprint Backlog. In doing they expand each Product Backlog item into one or more Sprint Backlog tasks so they can more effectively share work during the Sprint. Conceptually, the team starts at the top of the prioritized Product Backlog list and draws a line after the lowest of the high priority items they feel they can complete. In practice it is not unusual to see a team select, for example, the top five items and then two items from lower on the list but that are associated with the initial five.

An example Product Backlog from a real project appears as the following:

product backlog

This Excel spreadsheet shows each product backlog item assigned a general priority (Very High, High, etc.) by the Product Owner. Estimates have been developed by the developers but it is understood that they are very imprecise and are useful only for rough assignments of tasks into the various sprints.

【原创】Scrum中Product Backlog和Sprint Backlog的区别

  • jelin
  • jelin
  • 2012年03月09日 10:48
  • 6858

白话SCRUM 之二:product backlog

在SCRUM方法中明确要求了3个文档:          1 product backlog          2 sprint backlog          3 burn-down chart ...
  • dylanren
  • dylanren
  • 2011年12月15日 09:27
  • 8790

如何看待Scrum Sprint Backlog冻结和变化?

最近常常碰到的一个问题是 如何看待和处理迭代中的backlog的变化?Scrum对Sprint backlog范围在Sprint中坚持不变,这与瀑布里面冻结需求的做法较为接近。这样的迭代待办事项的冻结...
  • zhangmike
  • zhangmike
  • 2017年04月07日 16:46
  • 502

白话SCRUM 之三:sprint backlog

Sprint Backlog就是任务列表,如果映射到传统的项目管理理论中就是WBS(work breakdown structure),而且是典型的采用面向交付物的任务分解方法得到的WBS。比如有一个...
  • dylanren
  • dylanren
  • 2012年02月27日 16:48
  • 6568


2010-12-21 14:13 宗子城 每次我们看敏捷开发Scrum都是从技术角度,今天我们尝试从管理角度来看这个问题。 Scrum Scrum近几年已经成为最有影响的软件开发过程,从...
  • HorkyChen
  • HorkyChen
  • 2012年10月15日 22:57
  • 1900

SCRUM浅谈,User Story,Sprint,Burn Down Chart

什么是SCRUM首先要知道SCRUM是敏捷开发的方法论之一。 在学习SCRUM之前我们需要简单储备一下基本的知识。 什么是敏捷开发? 敏捷开发(Agile Development)是一种...
  • johnstrive
  • johnstrive
  • 2015年06月15日 21:50
  • 7013


1,目的 本流程是公司过程体系文件的一部分,用于描述软件系统敏捷开发过程,包括过程中涉及的角色和职责、主要的活动以及输出的主要工作产品...
  • xust999
  • xust999
  • 2014年08月30日 14:38
  • 649

Scrum 之 product Backlog

Scrum 之 product Backlog 转载自周金根 [ http://zhoujg.cnblogs.com/ ] Scrum的基本概念其实并不复杂,但是想做好并不容易,大家都...
  • wikiWang
  • wikiWang
  • 2012年03月27日 08:42
  • 612

敏捷开发中,Product Backlog 是否足以实现需求管理?

敏捷方法指导团队将产品需求置于Product Backlog中管理,并按照优先级对每个产品需求进行必要的排列。在计划会(Planning Meeting)之前,由Product Owner从Produ...
  • superbence
  • superbence
  • 2013年01月11日 08:59
  • 6974


  • leangoo
  • leangoo
  • 2016年07月13日 11:33
  • 1542
您举报文章:Learning Scrum - The Product Backlog