Design-Free requirements are important for two reasons, and hard for two other reasons. Design-free requirements are hard because you “know what you want” when you should be documenting “why you want it.” Writing design-free requirements can be hard when you don’t trust your development team to “do the right thing” […]
Kano Analysis / Product Management / Requirements / Requirements Models
Posted on:
Kano Analysis for Product Managers
Kano Analysis, while initially created to understand customer satisfaction with features, can be used by product managers to better understand customer problems. I gave a presentation last week for the Product Management View webinar series on Kano Analysis for product managers.
Agile / Business Analysis / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Software development / Use Cases / User Stories
Posted on:
Concise Requirements
Concise requirements give your team a useful, easy to read and easy to change understanding of what must be done. Great requirements exist to do three things: Identify the problems that need to be solved. Explain why those problems are worth solving. Define when those problems are solved.
Ishikawa Diagram / Product Management / Requirements / Requirements Models
Posted on:
Valuable Requirements
Writing valuable requirements is important. It doesn’t matter how well your teams execute if they are off building the wrong products / capabilities / features. The right products and capabilities are the ones that have relevant value. Valuable requirements solve problems in your market. Valuable requirements support your business strategy. […]
Business Analysis / Product Management / Requirements / Requirements Models / User Stories
Posted on:
Writing Complete User Stories
User stories can make requirements management a lot easier. They shift some of the communication from up-front documentation to ongoing dialog. That’s the main reason they work so well for agile teams. And agile teams focus on “what’s next?” instead of an ever-changing “what’s everything?” The problem is, when those […]
Business Analysis / Interaction design / Interface Design / Prioritization / Product Management / Requirements / Software development / UX
Posted on:
User Goals and Corporate Goals
When defining requirements, you always start in the context of a goal – either a user goal or a corporate goal. You need to be aware of both. Having a positive user experience is important, and requires a user-centered understanding. Achieving your corporate goals might be in conflict with some […]
Book Reviews / Communication / Marketing / Prioritization / Product Management / Requirements / Reviews / Software development / UX
Posted on:
Personas Make Blue Ocean Strategy Proactive
Blue Ocean Strategy provides an interesting reactive analysis of companies and markets. Personas are used to understand your customer’s needs. Combining the two provides powerful proactive insights when positioning your product for market success.
Business Analysis / Product Management / Requirements
Posted on:
You Must Not Write “The System Shall…”
A lot of books and blogs and experts tell us to use “The System shall…” when writing requirements. Read on to find out why that’s not a very good idea.
Business Analysis / Prioritization / Product Management / Requirements / ROI
Posted on:
Product Growth Strategy
Growth is a make or break measurement for products and companies. Investment is often determined by expected value, which is based (in part) on expectations of growth. When you create a product, there are aspects of growth – how many people can use your product, and how many people do […]