Okuzeka
Project Management vocabulary · Scope & Requirements

Requirement

Meaning in project management, with examples

/rɪˈkwaɪərmənt/nounCore term

In project management, requirement means: Something that the final product or result must do or have, as agreed with the client or users, for example a function, a performance level or a legal rule.

In Turkish: gereksinim, gereklilik, ihtiyaç

How it is used

Requirements are gathered, documented, analysed, prioritised and approved. People often distinguish business requirements, functional requirements and non-functional requirements such as speed and security.

Example sentences

  1. One key requirement is that the system must work offline in the warehouse.

  2. We spent the first three weeks gathering requirements from the sales and finance teams.

Common collocations

  • gather requirements
  • business requirements
  • functional requirements
  • meet a requirement
  • requirements document
  • scopeAll the work, features and results that a project has agreed to deliver, and by extension what it will not deliver.
  • acceptance criteriaThe specific, agreed conditions that a deliverable or user story must meet before the client or product owner will accept it as complete.
  • user storyA short, simple description of a feature from the point of view of the person who will use it, often written as: As a [user], I want [something] so that [benefit].
  • change requestA formal request to change something already agreed in the project, such as the scope, schedule or budget. It is assessed and then approved or rejected.

This word in other fields

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

More terms: Scope & Requirements

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: