Definition
The supposedly clear specifications of what a system, project, or product must do, which somehow always turn out to be neither clear nor complete when development begins. In tech, they're the sacred documents that stakeholders change weekly while insisting nothing has changed. The gap between what's written and what's actually wanted could swallow entire development teams.
Example Usage
The product manager delivered 47 pages of requirements, then asked why the developers kept bothering her with questions about the contradictions on every page.
Source: Common technical and project management terminology
Related Terms
Translate This Term
See “requirements” in Corporate Speak, Gen-Z Slang, Pirate Speak, and more.
Try the Translator