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):
- Is this a business, user, function, non-functional, or another type of requirement?
- Does the requirement meet the business, client, or project need?
- Does the requirement add value to your project or application?
- Does the requirement add, or modify the current project?
- Is the requirement what the Client asked for?
- Does the requirement fit the project budget and timelines?
- Does the requirement fit the project?
- Does the requirement make sense for your project/organization?
- Is your requirement possible with the current technology?
- Is your requirement fully explored and defined, is there any black holes or assumptions?
- Can you break down the requirement into detailed statements if the requirement is too vague?
- Does your requirement contain the solution?
- Can your requirement be measured?
- Did I stress the importance or priority of the requirement?
- 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.