There are eleven truths considered as parts of business requirement gathering.
The focus of business requirement gathering is understanding the business problem and then finding a solution.
Truth 4: There is an important difference between building a piece of software and solving a business problem. The former does not necessarily accomplish the latter.
It is very difficult for an individual user to understand the broader ramifications of deploying a piece of software. Typically software users do not know enough about the wider business to decide whether this incarnation of software will cause problems in some other part of the business.
Truth 11: BA will change the way users think about a problem. BA helps stakeholders understand and question the requirements.
When BAs have clear and measurable requirements, and when they reflect all this truth back to the stakeholders, it will change (for the better) their thinking about their business problem. Once people have a better understanding of the real meaning of their requirements, they are likely to see ways of improving them.
Truth 9: There is no silver bullet. Resources are not compensated on poor thoughts and workmanship. Judgement matters.
ReplyDeleteA meet can specify on what projects should the resources be spent and where the ideas won’t generate the requirement. This will automatically upgrade the results.
Truth 10: Implementation of requirements should be measurable and testable.
If some requirements are beyond the demand and some are coming as overstock. It can create unbalanced management of resources. So double checking the requirements is compulsory.
Truth 11: Business Analyst is the person who focuses on changing the way the user thinks about a problem either now or times to come. They also play a vital role in helping stakeholders understand and question the requirements.
Business analyst should develop a training plan that helps people adopt a change and make a smooth transition to new ways of doing thing for improvements
It is very true that there is a big difference in building a piece of software and solving a business problem. As an instance, Google maps was one of the revolutionary service launched by Google and now they are working to make it more better by using Google Earth software. Initially, GPS was used by US army but now they changed the living of people.
ReplyDeleteA Business Analyst plays a key role in projects. He makes requirements more clear to team and stakeholders and promote better understanding about requirements among stakeholders.
Truth 5 - The requirements do not have to be written, but they must become known to the builders. It is very important to clear all business requirements to the stakeholders or builders.
ReplyDeleteTruth 6 - Your customer won’t always give you the right answer. Sometimes it is impossible for the customer to know what he is right, and sometimes just doesn’t know what he needs.
Truth 7 - Requirements do not come about by chance. There needs to be orderly process for developing them.