Business Analyst Role

Business Analyst Role

The Business Analyst is using data to gain an understanding of the business. This will often lead to new projects based on their insights.

When to use

The Business Analyst uses the appropriate role based on the business conditions and their current area of assignment. With respect to projects, Business Analysts normally are heavily involved at the beginning to set the scope and at the end to verify completion.

Instructions

Virtually everyone in a business is involved in analyzing something. However, a Business Analyst (BA) is normally dedicated to a particular type of analysis based on the needs and concerns of the stakeholders. The BA is often looking for patterns and issues in the data that can be used by the organization to improve its products and processes. One consequence of this is that BAs are often creating requirements documents for new projects. This analysis is often the major factor when setting project scope.

The BA role is a flexible role that is used throughout the business, where data can be generated and analyzed. The BA will often be creating and maintaining operational dashboards. However, with respect to projects they are often found in these roles:

• Identifying stakeholders
• Gathering requirements from stakeholders
• Developing strategies
• Preparing documentation
• Analysing solutions
• Preparation of prototypes
• Clarifying risks and issues
• Preparing user manuals
• User training
• Driving change

This can be an eclectic and challenging position since the application of the BA’s work can be constantly changing. However, the one constant is that they are always focused on analyzing data.

Hints & tips

• The most significant hint or tip is in the area of communication. Bas will often be communicating with stakeholders who are in the midst of other issues and may not be fully engaged in the topic that BA is discussing.
• The communication issue can go both ways. The BA may be so focused on their data that they fail to understand what the stakeholders are telling them.
• The BA should not say “NO” to a request by a stakeholder but may say “NO” to the stakeholder’s favorite solution. The BA needs to use data to explain why other options are better suited to addressing the problem.
• Document all briefings, meetings, and conclusions. Not as a “gotcha” file but to improve communication for everyone affected by the information.