Did you ever disappoint someone even though you tried your best? It’s frustrating to see your efforts go unused and then find out that you are working on the wrong thing.
Expectations are an essential component of human relationships. They are often taken for granted. Expectations should not be taken for granted.
We have many tools and techniques that can help us understand and meet expectations in project management. Good requirements management helps us understand and meet those expectations.
Every stakeholder in a project has expectations. This includes the sponsor, team and customers. In many cases, even the top management. These expectations should be reviewed and may become requirements. This could lead to derived requirements which are solely designed to support the main requirements. What should be the outcome of this review? What is a good requirement for a particular project?
My own acronym was based on the SMART goal setting components and sources on soliciting great requests (see citations at end of article). These items are great! However, I must warn you that they are SOOT NUTS.
Documented! Documented! Documented!RankedPrioritize for when you can’t do it allEmpatheticNo conflicting requirements, understand diverse stakeholder needsSpecificClear, concise, to the pointOwnedWho’s expectation is being filled, and/or is an SME for this requirement?RealisticIs it feasible?Time-specificDependencies and timing taken into accountActionableIs this something you can execute on?Need-focusedFocus on needs, not preconceived solutionsUsefulWhat is the business justification?TestableHow do you know when the requirement is satisfied?SufficientEnough detail to tell what they really want?What factors do you look for in great requirements?
Sources and links: The Art of Requirements Gathering by George SpaffordEliciting software requirements, Presentation by Jesse Borschel, Sioux Empire PMI Chapter

Good Requirements are SORTA NUTS