A product roadmap is a high-level plan that shows how a product is likely to grow over time. This creates a continuity of purpose, aligns stakeholders and facilitates prioritisation. Unfortunately, many product owners and teams struggle with their product roadmaps. The roadmaps are often dominated by features, and the features are sometimes regarded as a commitment by senior management.
Agile Scrum backlog grooming and management
Business Analysis (BA) is a growing profession which is helping organisations to manage business transformation in an ever changing and complex world. Business analysts work across the business change lifecycle; they develop early understanding of business needs so that the right projects are funded for the right reasons and ensure that the solutions are developed that meet these needs. As a result, the Agile philosophy and techniques are fundamental to business analyst’s work.
Managing the product backlog and prioritizing the user stories if one of the main responsibilities of the product owners in Scrum. In this blog post, Andy Carmichael explains how to assess the priority of product backlog items using the cost of delay.
When a Scrum team starts its sprint, it needs to have user stories with the right size so that they can be completely developed at the end of the iteration. The art of slicing larger stories and epics that exists in the backlog to right-sized item for a sprint is not easy.
In this short video, Ken Rubin shares his thoughts on product backlog grooming in the Scrum agile project management approach. He wrote in his book “Essential Scrum: A Practical Guide to the Most Popular Agile Process” that “Product backlog grooming is essential for effective sprint planning and the resulting flow of features into a sprint. If the product backlog has been detailed appropriately, the items at the top of the backlog should be clearly described and testable.”
The prioritized product backlog is core to being Agile. A well prioritized backlog allows us to satisfy the customer through early and continuous delivery of valuable software at then end of each sprint in Scrum. Lean and Kanban may call it something else, but there too, prioritized work is key.
In a Scrum context, the definition of a “spike” is “a story or task aimed at answering a question or gathering information, rather than at producing shippable product.” In this article, Bill Ambrosini discusses how to manage them and when to use this activity.