Few areas which are least understood and could be improved are listed below:
- Assumptions: Make sure you have a clear understanding of each of the topics of the document. For ex. If there is an Assumption section then to make sure that the assumptions are minimal and purely related to the requirement analysis activities instead of the project activities. Also the exact meaning of Assumption is “a thing that is accepted as true or as certain to happen, without proof”. If your statement clears this test then it is considered as an assumption.
- Functional Specification: In the name of functional specification, sometimes the stakeholders are tempted to provide step-by-step and task-by-task description so that the information is not taken out of context. Make sure that the specifications do not contain step-by-step information. For ex: Do this once you have done this.
- Business Rules: These are policy statements which do not change over the period of time. It only changes when business changes the way they are doing business.
- Business Metrics: Be cautious about the business metrics as it should not include project metrics. Rather it should capture the metrics which would be impacted because of the new/updated business needs.
- Repeating: Sometimes the stakeholders become overcautious and they would like to state the same thing in different words in different parts of the document. Make sure that you communicate and emphasize the importance of information overloading.
These were some of the areas which I thought need to be watched carefully while you are dealing with different stakeholders. I am sure there will be several different areas like the above where the business analysts need to be cautious about the content. The idea over here was to provocate thoughts in your mind on this topic.
Don't forget to leave your comments below.