Often writing requirements can be stressful if you do not know what you or the client is expecting.

I have put together a list of questions that I like to ask myself while creating a Business Requirements Document (BRD):

  1. Is this a business, user, function, non-functional, or another type of requirement?
  2. Does the requirement meet the business, client, or project need?
  3. Does the requirement add value to your project or application?
  4. Does the requirement add, or modify the current project?
  5. Is the requirement what the Client asked for?
  6. Does the requirement fit the project budget and timelines?
  7. Does the requirement fit the project?
  8. Does the requirement make sense for your project/organization?
  9. Is your requirement possible with the current technology?
  10. Is your requirement fully explored and defined, is there any black holes or assumptions?
  11. Can you break down the requirement into detailed statements if the requirement is too vague?
  12. Does your requirement contain the solution?
  13. Can your requirement be measured?
  14. Did I stress the importance or priority of the requirement?
  15. Could I have written it better?

Think about these 15 questions and even create your own when writing any type of requirement. Creating a checklist of questions to ask each time you are creating requirements documents or during the requirements gathering and elicitation phase can help any business analyst complete their requirements activities.

By Morgan

CBAP and PMI-ACP with over 20 years of Project management and Business Analysis experience.