User stories are great at capturing product functionality. But they are less suited to describe complex user interactions. This is where scenarios and storyboards come into play: Both are great tools to describe the interaction steps. In this post, I explain what scenarios and storyboards are, how they can be used effectively in an agile context, and how they relate to user stories.
This post discusses nonfunctional requirements such as performance, robustness, and interoperability, and the Ford Shelby Mustang GT500.
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 is your last chance. After this, there is no turning back. You take the blue pill – the story ends, you wake up in your bed and believe whatever you want to believe. You take the red pill – you stay in Wonderland, and I show you how deep the rabbit-hole goes,” says Morpheus to Neo in the movie “The Matrix”. This quote reminds me of the choice we face when dealing with a new product idea: Should we walk away from it, or should we implement it? To help you decide if and how to progress an idea, I have developed the Product Vision Board. In this post, I show how the board can be applied to kick-start the product discovery process and to create a new digital product.
Leverage the power of customer feedback, and use your product backlog as a learning tool. Discover the right product features and take advantage of emerging requirements by integrating customer a feedback into the backlog early and frequently.
Innovate successfully by creating a minimal marketable product, a product with just the right features. This allows you to launch quicker, reduce time-to-market, and start earning money sooner.
“Which project is best suited to pilot Agile?” is a question I get regularly asked. This blog post discusses the following six criteria that help you select the right agile pilot project: small, important, independent, collocated, software only, and new product development.
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.