Definition of a Business Analyst

February 6th, 2012 by admin No comments »

According to Dictionary.com website a Business Analyst (BA) analyze the organization and design of businesses, government departments, and non-profit organizations. BAs also evaluate business models and their integration with technology.

Fundamentally, the responsibilities and activities performed by a business analyst are varied, but the most significant objective is always to advance the communication between the stakeholders and the project developers. Business analysts become more successful when they have undergone appropriate requirements training that educate them how to become efficient communicators and how to gather and write the requirements of the stakeholders.

Business analysis has four tiers. These four tiers consist of planning strategically,operating or business model analysis, process definition and design and the technical business analysis.

LEVELS:

There are at least four tiers of business analysis:

Planning Strategically

The analysis of the organization’s strategic business needs of the organization

Operating/Business Model Analysis

The BA definitions and analyzes the organization’s policies and market business approaches

Process Definition and Design

In this level tier refers to the business process modeling (often developed through process modeling and design)

IT/Technical Business Analysis

The BA assists in the interpretation of business rules and requirements for technical system

As you can see, there are a number of characteristics which identify the role of the Business Analyst including:

The analyst works with the business to recognize opportunities for enhancement in business achievements and procedures.

The analyst is involved in the design or modification of business systems or IT systems.

The analyst interacts with the business stakeholders and subject matter experts in order to understand their problems and needs.

The analyst gathers, documents, and analyzes business needs and requirements.

The analyst solved business problems and, as needed, designs technical solutions.

The analyst documents the functional and, sometimes, technical design of the system.

The analyst interacts with system architects and developers to ensure system is properly implemented.

The analyst may help test the system and create system documentation and user manuals.

ALTERNATIVE DESCRIPTIONS

We proposes the following definition of a business analyst: “An interior consultancy position that has responsibility for inspecting industry structures, identifying opportunities for humanizing business systems and correlating the desires of the business with the use of IT.” The International Institute of Business Analysis (IIBA) describes the role as: “a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.” The Certified Software Business Analyst (CSBA) Common Body of Knowledge defines this as: “uniquely placed in the organization to provide a strong link between the Business Community and Information Technology (IT).”

The role of Business Analyst has evolved from someone who was a part of the business operation and worked with Information Technology to improve the quality of the products and services being delivered by the IT organization to someone who apart from gathering Business Requirements, also assists in Integration and Acceptance Testing, supports the development of training and implementation material, participates in the implementation, and provides post-implementation support. Business Analysts today are also involved in the development of project plans and often provide project management skills when these skills are not available in other project participants.

A Day in the Life of a Business Analyst

February 6th, 2012 by admin No comments »

Ever wondered how a day in the life of Business Analyst would look like? Well, in basic terms, the daily duties of a Business Analyst on any given day in his designation would typically involve the following:

1) Understanding of the project: This means understanding through questioning and clarification with the client, what his expectations and needs are from the project.

2) Describing existing state: A description of the existing systems in the clients’ premises will ensure a good idea of why and how the client expects the new system to be developed by the technical team.

3) Specification of project: This would mean defining the client’s problems that need to be resolved through the project, in a format that the technical team of software developers and programmers identify with, so that they can start the project.

4) Supervising the work: This indicates that once the technical team has started doing the project, and the programmers and coders are working on the client’s project, a Business Analyst, should duly supervise their work, so that he is aware of the progress they are making and be around to help them out with any queries or problems that they may have, with regards to the project.

5) Execution of the project: Once, the software team has finished the project, the project has to be executed to check if it is running fine and as per the expectations of the client. This is done by the Business Analyst and then communicated to the software team of programmers and coders about the results of their work.

6) Checking for bugs: while running the project’s code, there may be some errors or bugs as they are called in technical language that may crop up. These have to be resolved with the help of the technical team, and then ensured that they won’t cop up again in future.

7) Mapping the project to client expectations: The resultant software developed by the software team, needs to be mapped with the client’s expectations so as to check if there is a proper match. The Business Analyst is responsible for a proper match.

8) Checking for modifications: Sometimes, it may be found that there is a slight or some other degree of mismatch with the clients expectations from the project and the software developed by the technical team. In this case, medications in the project code may be required and has to be done.

9) System Run: Finally the system is then ran under test conditions in front of the client, and later in live conditions, as per client’s approval, to check if the system is working fine.

10) Project Completion: If the system is found to be working fine, as per client’s expectations, then the project can be declared as completed, to the client’s satisfaction.

This is of course a very rough and basic idea of how a day in the life of a Business Analyst would be. On a typical day in the life of a Business Analyst, the Business Analyst could be in any one of these phases.