Category Archives: Product Requirements

You have an idea. You write it down. Maybe you sketch it on a white board. You talk to some engineers. You write user stories. And away you go. You start building. That sounds right. Isn’t that what we are … Continue reading →

Do you have a bug management system with thousands of bugs? Do you have meetings to review high priority bugs? Do you argue over how to use priority and severity? Why? Bug management is a waste of time.  Bugs fall … Continue reading →

Yesterday, I was the guest speaker on the Global Product Management Talk hosted by Cindy Solomon. For yesterday’s show, Roger Cauvin was the co-host. We were discussing how to write compelling user stories. As many of you know, this is … Continue reading →

Over the last few weeks, we’ve taken a look at several aspects of user story writing. As the primary means of kicking off conversations between product and engineering in most Agile environments, user story writing is a critical skill to … Continue reading →

You’ve written your user stories, engineers have accepted them, development is in progress. Now what? More often than not, odds are you left off one of the most important parts of a user story – the acceptance criteria. Acceptance criteria … Continue reading →

Over the past couple of weeks, we’ve looked at how to write good user stories, how to use themes to manage your backlog, and how to measure and predict the impact of user stories. Today, we’ll take a high-level look … Continue reading →

On Tuesday, we looked at how to measure the impact of each user story, looking at both measuring the effectiveness of the mechanics of the feature and also the impact of the story on our overall product goals. Today, we’ll … Continue reading →

On Thursday, I wrote about how to use themes to stay focused on your product goals. But using themes is not enough. You also need to identify how you are going to predict and measure the impact of each user … Continue reading →