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. […]
Flashback
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-11-17]
A look back at the best from a year ago.
Requirements
Posted on:
Abstraction And “Requirements”
I don’t know how many of our readers have reached a conclusion to this debate, but we have for now. Thanks to everyone who has contributed to, enjoyed, or at least tolerated this ongoing discussion. Roger had some good comments in our previous article – we’ll try and address one of his points here. His point, I believe, is that using the word “requirements” to describe multiple levels of abstraction in the definition of a product is a bad thing.
Product Management / Requirements
Posted on:
Valuable and Functional Requirements
Roger asked some interesting questions on one of our previous posts about market and product requirements. In a couple recent articles, we presented some specific examples to clarify the semantics and language of different types of requirements. Roger asks six questions about functional and non-functional requirements in the comments on the last article. In this article, we answer them.
Product Management / Requirements / Requirements Models / ROI / Use Cases
Posted on:
Verify Correct Requirements with Use Cases
The next piece in the puzzle of how and why we apply use cases to product management. Verification of requirement correctness.
Interaction design / Product Management / Requirements / UX
Posted on:
Writing Valuable Requirements
One of the ten big rules of writing a good MRD is writing valuable requirements. How do we determine what requirements are valuable? To whom are they valuable? When a requirement represents a continuum how much is enough? What is too fast, what is too scalable? To whom must the requirement be valuable?