Five (5) key business analyst roles and responsibilities
“The price of greatness is responsibility.“— Winston Churchill
[bctt tweet="The price of greatness is responsibility. — Winston Churchill"]
Every time we apply for a job position its description has a section with a heading such as: “your mission“, “day to day” or simply “job description“. All these titles refer to the key business analyst roles and responsibilities . In this post I will list the 5 most important ones that the majority of companies who are looking for a business analyst will ask you to have.
1. Gather requirements.
This is the first step in the software development life cycle. It corresponds to the act of gathering all the information needed with the propose of identifying the client necessity. The two most common ways of getting it are:
- Meetings with the client. This is the most important way of getting information.
- Reading previous information about the business that could be taken from written legal procedures or simply from the documentation that the company has already made to fill some quality standard.
It is about analysing the already gathered information and designing the best solution to satisfy the client necessities.
It is also the process of understanding what needs to be done in order to offer the client the best software solution. This is the step where the creativity takes place.
3. Model solution.
This point refers to the documentation. Every project is different, even though most of the time you will use diagrams, the type will vary depending on the project. What is certain is that you will be required to be as clear as possible, and the use cases, user stories, UML notation and mock-ups are going to be your allies in reaching this clarity.
4. Ensure business integrity.
You will be required to be the person that ensures the alignment of what has been built with the new business requirements.
Basically, this is about making sure that your solution has consistency with what the company already has built and what it stands for. The consistency is not only going to be about matching your new solution with the infrastructure and technology but also with the company’s culture and principals.
5. Give support.
Eigter in the traditional or the agile software develoepement life cycle the business analyst role is not limited to talking with stakeholders. It is their responsibility to give support to programmers, testers, UI and UX area and any other role that may need to understand what the client needs are.
You might also like to read about one of the best business requirements document examples
And don’t forget to download the BA Methodology where you will learn how to execute the business analysis tasks in a professional and efficient way, even if you have no experience.
See you next soon 😉