When requirements are ambiguous for a reporting feature, what is a recommended approach?

• A. Clarify with stakeholders, define MVP scope, build skeleton API and mocks.
• B. Wait for explicit specs before acting.
• C. Add as many features as possible to cover ambiguity.
• D. Cancel the project.

Answer: (A)

When requirements are unclear, the best path is to align with stakeholders and establish a small, testable plan. Clarifying goals, success criteria, data sources, and what the report must show helps everyone agree on what “done” looks like. Defining a minimal viable product keeps scope focused and enables early validation, while building a skeleton API and mocks lets frontend and integration work progress in parallel without waiting for every backend detail. This approach reduces risk, accelerates feedback, and avoids overbuilding or stalling.