A BA quality checklist 🗓

“I’ve written project requirements, but I’m not sure they’re good. How do I check?”
Here are three things mentors will look for straight away:

✔️ Atomicity (one requirement = one function/behavior)
Bad: “The system must support users and send notifications.”
Good: “The system must send an email after a user registers.”

✔️ Unambiguous wording (only one way to interpret it)
Bad: “The interface must be user-friendly.”
Good: “The Save button must be placed in the top-right corner of the modal window.”

✔️ Testability (QA can verify it)
Bad: “The website must load fast.”
Good: “The homepage must fully load in under 3 seconds.”

🤝 Your next step:

Pick any requirement from your document and run it through this checklist. Rewrite it if needed.

🧠 Ask AI:

“Here’s my functional requirements document for a mobile app. Check each requirement for atomicity, clarity, and testability. Tell me which points should be rewritten and suggest improved versions: [paste your text].”

@andersen_courses ✈