The product backlog is a great tool. But using it effectively can be difficult. One of the challenges is to get the level of detail right. An overly detailed backlog is unwieldy and hard to manage. But a product backlog that is too coarse-grained is also not helpful: It provides too little guidance for the development team. This post helps you strike the right balance between too much and too little detail. It shows you how determine the right amount of detail for your product backlog.Read More
Tag archive for "grooming"
User stories are a simple, yet effective way to communicate how a user or customer employs a product. But writing user stories that help a team build great software can be challenging. The post shares five common user story mistakes and how to overcome them.Read More
Find out when it’s the right point in time to groom your product backlog: Before or after more development work is carried out.Read More
Discover five essential steps that will ensure that your product backlog facilitates innovation and drives the work of the development team.Read More
This posts discusses a user-centric, iterative, and collaborative design process for Kanban and Scrum teams.Read More
Using the product backlog can be challenging, and many product owners wrestle with overly long and detailed backlogs. This blog post provides ten tips that help you work with your product backlog effectively.Read More
High-priority product backlog items must be ready to be transformed into working software. Find out what does “ready” means and benefit from Yoda’s advice.
The product owner is a key role in Scrum. But many teams and many organisations struggle to fully understand and to effectively apply the role. This post wants to help you get it right by providing a concise overview of what it means to be the product owner.Read More