#21 The Stale Product Backlog

Symptom: There is no enhancement of stories as the project progresses leading to a static product backlog and the team feeling that they are driving the project rather than the client.

Probable Cause: The product backlog may not be reviewed regularly by the product owner and there is a disconnection. Also new story ideas may not be captured effectively during the project.

Suggested Resolution: A static product backlog may seem to be the optimum, but with an empirical process, change is actively encouraged and for most projects it is needed in order to "grow" the product backlog into a real product concept. Without these enhancements to stories the product backlog becomes static and stale, which may well result in a waterfall like outcome - "it is what I initially asked for, but not what I need."

To promote an evolving product backlog where the product owner acts as a gardener by encouraging some aspects to grow whilst also pruning others back, try to capture new ideas as new stories during every project activity. This could be actively listening for new ideas during the daily stand ups or capturing feedback during a review and writing them as a new user story to be prioritised in the next prioritisation round for example.

Also try to hold regular product backlog discussions with the product owner and really encourage them to be the "gardener" and connect with the evolving product concept.

What you are really looking for is a constant evolution of stories and ideas that begin to converge on the real solution rather than just a static collection of stories that begin to go stale and smell as the project moves forward.

For more agile coaching options, check out agile coaching