User stories are probably the most popular agile technique to capture product functionality: Working with user stories is easy. But telling effective stories can be hard. The following ten tips help you create good stories.
User stories are a powerful agile technique to describe requirements from the perspective of the customers and users. Unfortunately, I find it not uncommon that user stories are applied unsuccessfully and fail. This post describes two common failure causes and discusses how you can avoid them.
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.
The Product Canvas is a simple, yet powerful tool that helps you create a product with a great user experience and the right features. This post explains how you can create your initial canvas using a collaborative workshop.
This post discusses nonfunctional requirements such as performance, robustness, and interoperability, and the Ford Shelby Mustang GT500.
The product backlog is an important tool: It lists the ideas and requirements necessary to create a product. But is it always the right tool to use? This post discusses the strengths of a traditional product backlog together with its limitations. It provides advice on when to use the backlog, and when other tools may be better suited.
User stories are great at capturing product functionality in isolation. But they are not well suited to describe the relationship between different features and capture user journeys and workflows. This blog posts shows how context and activity diagrams can be successfully used to model interactions in user story context.
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 post provides a tongue-in-cheek collection of common product creation mistakes. Combined they are a recipe for certain failure and provide a lesson in how not to develop products. Sadly, they are not made-up but based on my experience working with different companies and teams. I hope that listing the mistakes helps you avoid them thereby increasing your chances of developing a successful product.
Many product backlogs are too long, detailed and complex. This is in stark contrast to what the product backlog should be: a simple artefact listing the outstanding work to bring the product to life. This blog post discusses lean techniques to make the backlog concise and focussed by avoiding variation and overburden.