If you do not have a clear idea on where you are going, you will certainly have the difficulty of knowing when you’d get there. The same happens in business; you won’t be able to know if you have succeeded in achieving your objective if you don’t have one. This is why the process of business requirements gathering is the most integral piece of any application development project.

It is the business analyst’s responsibility to gather accurate business requirements from the clients or the sponsors of the project. Various methods can be used to gather information about the client’s business requirements. The business analyst must be able to gain the trust of the clients so that he can get open and honest opinions and requirements from them. To do this, the analyst must exert effort and take time in knowing the clients’ business. He must also know how to easily communicate with them and show them that he is really interested in understanding the business challenges and the project being developed. Unfortunately, not all business analysts are good in establishing rapport with their clients. This is because effective communication skills are simply not derived from textbooks. It can be advantageous to attend business requirements training where effective requirements gathering communication techniques are given more focus.

More often than not, clients and Information Technology designers do not see eye to eye. A good business analyst must also know how to write business requirements in words that both the clients and the IT designers can understand. This would mean eliminating technical jargons in writing business objectives, problem statements, requirements list and reporting specifications.

Comments are closed.