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.Read More
Tag archive for "prioritising"
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.Read More
This post explains how to write user stories at the right level of detail, and how to derive small, ready stories from big, coarse-garined epics.Read More
The Product Canvas is a simple, yet powerful agile 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.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
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.Read More
Are you struggling with your product backlog? Then try Roman’s 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.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.
This blog posts explores four useful factors to prioritize the product backlog: value; risk and uncertainty; releasability; and dependencies.Read More