agile42

Tag archives: backlog

Product Backlog: Requirements or Stories

One of the "assumption" that is often made, when starting to adopt Scrum, is that there will be a Product Owner and there will also be a Product Backlog. Well, it happens that the Product Backlog quality is one of the major responsible for the outcome of what the team will produce in terms of software, and is absolutely one of the most difficult things to work out. There are many problems related to having a right Backlog in place, and as you may guess there is no "one recipe" for the right Backlog, only some important ingredients to mix up in the right way ;-)

On
7 July 2008
In
Tags
agile, backlog, product owner, scrum

Product Backlog: Requirements or User Stories?

Hi there, spending some extra time at the airport (thanks to lovely pilot strikes) gives me the chance to write a bit about Scrum and the Product Backlog. A Product Backlog is a stack of "features" prioritized by Business Value, which means that on top of the stack there is always the most valuable item for the customer/client.

The owner of the Product Backlog is the Product Owner and as such should be the one and only authorized to make changes to the Product Backlog, given also the fact that the main responsibility ...

Latest entries

Product Mastery by Geoff Watts

Our review of "Product Mastery" by Geoff Watts

 

Your opinion needed about the Canadian Regional Scrum Gathering

We are gathering information about the upcoming Regional Scrum Gathering® Canada 2018

 

HR people need to know and apply Agile practices

Agile has become a mainstream way of working in most companies. This is not only in ...

 

Article in Leading Dutch Magazine Elsevier

An interview with agile42 on was published in a special edition of the Dutch weekly Elsevier ...

 

How to Plan the “Perfect Retrospective” - a.k.a. Ditching a Good Plan

Planning too far ahead is a waste: it is best to stay flexible and decide as ...