Requirement

How it is used

Used in PRDs, specs and tickets. Teams gather, define, document, clarify and change requirements. Functional requirements describe behavior (users can reset their password); non-functional requirements describe qualities such as speed, security and accessibility.

Example sentences

1. One key requirement is that the page loads in under two seconds on mobile.

2. The requirements changed twice during the sprint, so the estimate is no longer valid.

Common collocations

• gather requirements
• business requirements
• functional requirement
• meet a requirement
• clarify the requirements

Related terms

• PRDShort for product requirements document: a document that explains what a feature or product should do, for whom and why, so the whole team works from the same plan.
• specShort for specification: a document that describes in detail how a feature should look and behave, so that designers and engineers can build it correctly.
• user storyA short description of a feature written from the user's point of view, usually in the form “As a [type of user], I want [goal] so that [benefit].”
• acceptance criteriaThe specific conditions a user story must meet before the team and the product owner accept it as finished and working correctly.
• edge caseAn unusual situation that happens only at the extreme limits of normal use, such as an empty list, a very long name or a lost connection during payment.

This word in other fields

The same English word can have a different meaning in another field:

• requirement · Software Engineering
• requirement · Project Management
• requirement · Military & Defence
• requirement · Job Interviews & Careers

More terms: Requirements & User Stories

• feature
• use case
• epic
• feature request