Requirement Verification Flashcards
INVEST
Independent - of internal and especially external dependencies (3rd parties)
Negotiable - flexible scope; none specific language is used in; explain the intention, not implementation
Valuable - value is clear to everyone; persona matches Benefit&Goal; will deliver the benefit; avoid technical/role specific language
Estimatable - it is possible to estimate the needed resources for the delivery of the task
Small - clear and concise explanation; easily fits into a Sprint (i.e <20% of velocity and definitely NOT >33% of velocity)
Testable - can be automated; avoid external/long test suits
Atomic
self-contained and capable of being understood independently of other requirements or design
Complete
enough to guide further work and the appropriate level of detail for work to continue. The level of completeness required differs based on perspective or methodology, as well as the point in the life cycle where the requirement is being examined or represented.
Consistent
aligned with the identified needs of the stakeholders and not conflicting with other requirements.
Concise
contains no extraneous and unnecessary information.
Feasible
reasonable and possible within the agreed-upon risk, schedule, and budget, or considered feasible enough to investigate further through experiments or prototypes.
Unambiguous
the requirement must be clearly stated in such a way to make it clear whether a solution does or does not meet the associated need.
Testable
abale to verify that the requirement or design has been fulfilled. Acceptable levels of verifying fulfillment depend on the level of abstraction of the requirement or design.
Prioritized
ranked, grouped, or negotiated in terms of importance and value against all other requirements.
Understandable
represented using common terminology of the audience.
