Content tagged with: product backlog
In this article, Brent Reid discusses the fact that in Scrum, the product backlog should be ordered and not prioritized. His point is that priority has a meaning only within a certain context. Thus what is high priority one day could be low priority in the future. Thus, the product owner must deliver a totally ordered Product Backlog, even if it is difficult to make such decisions. However, as Brent Reid wrote it: “this clearly places the responsibility of resolving the problem on the product owner instead of on the …
In this blog post, Borig Gloger presents an Excel spreadsheet that he has created to support Product Owners. This spreadsheet contains a very simple Product Backlog template. You can list your user stories with priority and their number of story point. The spreadsheet then helps you to calculate the amount of story points per Scrum sprint and produce a suitable Burn Down Chart.
Elena Yatzeck shares in this blog post her thoughts about “value spike”. A “spike” is a short piece of work within an agile project in which one or two programmers may be assigned to do outside of the iteration structure. The goal is to investigates unknown technology problems well enough so you can estimate them. In the same intent, a “value spike” is time that the Product Owner takes to assemble the right Subject Matter Experts (SME) for a meeting to determine the authorship and impact of a requirement whose …
In this blog post, Maurits Rijk explains the importance of a prioritized backlog to deliver business value as quickly as possible in a Scrum project.
‘In Programming, the hard part isn’t solving problems, but deciding what problems to solve’. In this famous quote, Paul Graham sums up one of the great challenges of software development, namely, how do we pick the right problem to solve, the right feature to deliver, the right bug to fix?
This video shows how to specify the application’s requirements using user stories and a product backlog in Microsoft Visual Studio 2010.
This article explains how product backlog grooming works, shares advice on discovering and describing product backlog items, and on structuring the product backlog. ScrumMasters, coaches, team members will also benefit from reading the extract as managing the product backlog is teamwork in Scrum.