A constraint is a requirement that limits the available solution or the way a team develops it.
A product constraint restricts the design or implementation of a system. For example, it may require a specific technology, database, interface, size, or operating environment. A process constraint, in contrast, restricts project work. It may define budgets, deadlines, methods, roles, or mandatory documents.
Some restrictions result from laws, regulations, contracts, or organizational policies. Therefore, teams cannot always negotiate them. However, teams should review assumptions and preferences that lack a binding reason.
Clear documentation should explain the restriction, its source, and its rationale. In addition, measurable acceptance criteria should support verification.
Well-defined constraints guide design decisions, reduce uncertainty, and prevent unsuitable solutions.
« Back to Glossary Index