Differentiate hard requirements from soft requirements in project planning and how they influence scope.

• A. Hard requirements are optional; soft requirements must be met.
• B. Hard requirements are must-haves; soft requirements are desirable; influence prioritization and contract.
• C. Soft requirements have higher priority than hard ones.
• D. Hard requirements do not affect scope.

Answer: (B)

Differentiating hard from soft requirements centers on what must be delivered versus what would be nice to have. Hard requirements are the must-haves that define the baseline scope. They specify the minimum functionality, performance, compliance, or other conditions that the project must meet to be considered complete. Soft requirements are desirable features that can add value but are negotiable; they can be prioritized, deferred, or traded off against time and budget.

In planning, hard requirements anchor the scope and drive the acceptance criteria, contract terms, and resource decisions. They determine what is non-negotiable in the current phase and what must be delivered to achieve success. Soft requirements influence prioritization and change control: they help decide which features to include now, which to push to a later release, and how to negotiate scope with stakeholders.

For example, a software release might have a hard requirement for security controls and core data reporting, while a soft requirement could be an optional dashboard customization. The hard items stay in the current scope, while the soft items guide prioritization and potential future work.

Why the other ideas don’t fit: hard requirements aren’t optional—they define the minimum deliverables. Soft requirements don’t inherently outrank hard ones; they are evaluated against constraints to decide what's included now. And hard requirements do affect scope by establishing what must be delivered.