Contents
What are product backlog features?
A product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes or other activities that a team may deliver in order to achieve a specific outcome. Those that a team will work on soon should be small in size and contain sufficient detail for the team to start work.
Which are three properties of a product backlog?
Roman Pichler (Pichler 2010) and Mike Cohn coined the acronym DEEP to summarize several important characteristics of good product backlogs: Detailed appropriately, Emergent, Estimated, and Prioritized.
What are the characteristics of good product backlog?
Good Product Backlog Characteristics
- Detailed Appropriately. The product backlog items will differ in their level of detail.
- Emergent.
- Estimated.
- Prioritized.
- Release Flow Management.
- Sprint Flow Management.
- What Is a Product?
- Large Products—Hierarchical Backlogs.
What does a healthy backlog look like?
A healthy backlog typically includes stories at various levels of refinement. I recommend that your backlog include some ready stories at the front of the line, as well as some in-refinement stories that are further out. Ready stories have been fleshed out with enough detail that a team could work on them immediately.
What’s the difference between product backlog and release backlog?
Work items. Product backlogs contain product features. A product feature is a slice of business functionality that has a corresponding benefit or set of benefits for the product’s end user. Release backlogs also contain product features. These are pulled from the product backlog.
What does a backlog mean in agile development?
In agile development, a product backlog (often referred to simply as a backlog) is a list of all things — new features, bug fixes, improvements, changes to existing features, and other product initiatives — that product teams must prioritize and deliver in order for a product to strategically come to life.
How does the product backlog fit into the Big Picture?
How does the product backlog fit into the big picture? 1 The product strategy is a high-level overview of how the company vision will be achieved. 2 The product roadmap dictates how the strategy will be executed. 3 The product backlog contains the task-level details required to develop the product as outlined in the roadmap.
How is the number of features in a backlog determined?
The release date and number of features included in a release backlog is determined by past velocity and resources available. User stories are estimated in story points or time. The development team uses their past velocity and current capacity to determine a max story point number or time value for each sprint.