The product owner and the ScrumMaster are two separate agile roles that complement each other. To do a great job, product owners need a strong ScrumMaster at their side. Unfortunately, I find that there is often a lack of ScrumMasters who can support the product owner. Sometimes there is confusion between the roles, or there is no ScrumMaster at all. This post explains the differences between the two roles, what product owners should expect from their ScrumMaster, and what the ScrumMasters are likely to expect from them.
Working with a sprint goal is a powerful agile practice. This post helps you understand what sprint goals are, why they matter, how to write and how to track them.
This post explains how to write user stories at the right level of detail, and how to derive small, ready stories from big, coarse-grained epics.
This post introduces my Product Canvas, a simple but powerful tool that helps you create a product with a great user experience and the right features. It combines Agile and UX by complementing user stories with personas, storyboards, scenarios, design sketches and other UX artefacts. It’s designed to work with Scrum, Lean Startup, and Business Model Generation. The canvas supports Lean UX by combining user centred-design and agile techniques.
Grooming the product backlog helps you make the right product decisions by integrating new insights into the backlog, and it helps you get the product backlog ready for the next sprint. In this post, I share a systematic approach to carrying out the grooming work that takes into account new feedback and data, leverages a collaborative approach, and comprises of key five steps.
Applying the product owner role can be challenging, as no two products are the same. While products and projects vary, I have found two common ways to employ the role: Asking the customer or a customer proxy such as a product manager to take on the product owner role. This post discusses when which option is more appropriate.
Are you struggling with your product backlog? Then try my Product Backlog Board, a structured hierarchical product backlog that helps make sure you have ready items, capture non-functional requirements, and integrate your requirement models.
This blog posts explores four useful factors to prioritise the product backlog: value; risk and uncertainty; releasability; and dependencies.