How do you approach a project when requirements are unclear or constantly changing?

• A. Seek clarification, define a flexible scope, create iterative plans, and maintain stakeholder alignment.
• B. Wait for perfect requirements before starting.
• C. Avoid stakeholder input to prevent scope creep.
• D. Apply a rigid project plan and avoid changes.

Answer: (A)

When requirements are unclear or constantly changing, you keep momentum by staying flexible and closely aligned with stakeholders. Start by seeking clarification to reduce ambiguity and confirm what truly matters for the outcome. Define a flexible scope rather than locking in a fixed set of deliverables, so you can adjust priorities as new information emerges. Build plans in iterations, delivering small, usable increments and using each cycle to learn, validate assumptions, and adapt. Maintain ongoing stakeholder alignment through regular updates, clear decisions about changes, and a visible backlog that reflects current priorities.

This approach works well because it accommodates uncertainty and learning as the project progresses. Waiting for perfect requirements stops progress, avoiding stakeholder input removes essential reality checks and buy-in, and a rigid plan can’t absorb changes without derailing the project.