requirtis

Requirtis is a term used in theoretical discussions of software development and requirements engineering to describe a persistent pattern in which stakeholders repeatedly request additional requirements, changes, or constraints after initial scope has been defined. It is not a medical diagnosis; the suffix -itis is used humorously to imply an inflammatory, ongoing condition within project cultures. In practice, requirtis functions as a cautionary label for behavior that amplifies scope creep and delays decision making.

Common signs include repeated requests for new features or changes without clear prioritization, escalation of questions across multiple cycles, and growing backlogs that outpace delivery capacity. Teams may experience slower sign-off, endless refinement, and misalignment between stakeholders’ expectations and the product vision.

Causes are typically structural and cultural: unclear product goals, divergent stakeholder incentives, weak governance, insufficient early validation, and cognitive biases such as over-optimism or fear of committing to a concrete plan. Poor change-control processes can also contribute.

Diagnosis in real practice is descriptive rather than clinical: project managers and product owners describe requirtis when backlog items accumulate and release plans stall. Management approaches emphasize strong product vision, explicit prioritization, lightweight change control, and iterative delivery to counteract it.

Prognosis depends on organizational response. With disciplined prioritization, transparent communication, and sprint-based delivery, the effects can be mitigated. Without intervention, it can lead to chronic delays, budget overruns, and diminished stakeholder confidence.

See also: scope creep, requirements engineering, backlog management, agile methods.