Each requirement you write represents a single market need, that you either satisfy or fail to satisfy. A well written requirement is independently deliverable and represents an incremental increase in the value of your software. That is the definition of an atomic requirement. Read on to see why atomic requirements […]
Business Analysis / Ishikawa Diagram / Kano Analysis / Product Management / Requirements / Requirements Models
Posted on:
Verifiable Requirements
Writing Verifiable Requirements should be a rule that does not need to be written. Everyone reading this has seen or created requirements that can not be verified. The primary reason for writing requirements is to communicate to the team what they need to accomplish. If you can’t verify that what […]
Business Analysis / Ishikawa Diagram / Product Management / Requirements / Requirements Models / ROI
Posted on:
Attainable Requirements
Unless you live in a world filled with unicorns and rainbows, writing realistic requirements is critical. When you set unattainable goals, the best result you can hope for is a frustrated engineering team. Write requirements that are attainable, and your team will surprise you with what they can achieve.
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. […]
Agile / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Software development / Testing
Posted on:
Failure To Launch (Your Product)
Jump forward in time to the day of your next big product launch (first release, new features, new market segment, etc). And your site/application crashes due to the “unexpected” demand. All you can do now is look for a bucket of water to put out the fire. What could you […]
Agile / Ishikawa Diagram / Product Management / Requirements / Requirements Models / Software development
Posted on:
Agile Product Management: Providing Context
Agile development methodologies succeed because they help development teams be as effective as possible. Development teams do not, however, work in complete isolation. The company they work for has a strategy. The company manages a portfolio of products, and targets a particular product at specific market problems. Within that context, […]
Ishikawa Diagram / Marketing / Product Management
Posted on:
Buyer Personas And User Personas
A lot of people stand up a variation of “If you build it, he will come” (from Field of Dreams) as a copy-writing hook for whatever they are about to tell you about creating products/services/whatever. We’re no better. We’re going to tell you that there is a big difference between […]
Austin TX / Business Analysis / Ishikawa Diagram / Product Management / Requirements / Requirements Models
Posted on:
Defining Problems at ProductCamp Austin 1
Jun 14th was the first productcamp in Austin (and the second one anywhere). It was a great event, and here’s the presentation that I did on how to define the strategic problems that drive our products.