Requirements & Remote Working ยท Lesson 1 of 2

Clarifying ambiguous requirements

Study notesAbout 3 minutes. A full lesson with quick checks is on its way.

In short

If a requirement could mean two things, ask before you build. A short question beats days of rework.

In your work

A client asks for 'members to see their history'. You ask: bookings, payments or both, how far back, and can staff see it too? The answers change the data you need, and the privacy checks.

What the UK rules say

  • UK GDPR's data protection by design means questions about personal data are best settled before you build, not after.
  • The BCS Code of Conduct asks IT professionals to work with due care and diligence.

What to do

  1. Restate the requirement in your own words and confirm it.
  2. Ask about edge cases, users, data and what 'done' looks like.
  3. Write the answers into the ticket.

Watch out for

  • Guessing because you don't want to look unsure.
  • Agreeing details on a call and not writing them down.

In your organisation

How does your team capture requirements and get them signed off by clients?

Your employer's own policies come first.

Sources

UK law and guidance, explained for learning. Not legal advice.