Who am I? Defining What a Business Analyst Really Is.
Different types of business analysts exist.
There is a difference between the techniques they practice and the domain knowledge they must possess.
Within each of these categories, IIBA has attempted to provide common job titles that might exist within an organization, such as “Management Consultant” in the generalist category. “Agile Business Analysts,” “Business Intelligence Analysts,” “Product Managers” and “Systems Analysts” are all examples of specialists. Common hybrid roles are “Project Manager,” “Developer,” “Quality Assurance Manager” and “Graphic Designer.” The definition and scope of each of these roles often varies by organization for a variety of reasons. For example, as a consultant for Catapult Systems, my responsibilities are dependent upon the project scope and my role within that project. With my background in database programming and analysis, I have the ability to fulfill the need for a specialized business intelligence analyst. However, based on staffing needs, my background in project management may also be required and I will be dually tasked as both the business analyst and the project lead, which fits more of the hybrid role definition.
So now that we have a framework for describing the role, what is it that business analysts actually do day to day? Communication is a critical element of our job as we have to work with multiple layers of the business, from the technical subject matter expert to the executive management team. Possessing the ability to translate needs and requirements across that diversity is crucial, as well as being able to effectively analyze the information gathered. In this, the ability to rapidly absorb information and extract vital elements is important. This is particularly true of consultants who are often brought in to evaluate their client’s business but initially lack the specific context of the problem they are being asked to solve. Group facilitation, authoring, negotiation, and a whole host of other business skills are also necessary to effectively function as an analyst.
To supplement these general skills, business analysts are required to apply a variety of techniques to elicit requirements, analyze them and provide the resulting recommendations. Examples of these techniques are: Brainstorming, interviews, process mapping, cause-and-effect diagramming, statistical analysis and others. Not all techniques are applicable on all projects. For example, writing use cases or performing usability analysis is most traditionally associated with software development and may not be appropriate for a manufacturing process improvement project. Factors that influence the choice of techniques vary such as the type of project, project phase, organizational maturity, intended audience or other considerations. However, the fundamental skills needed to select the appropriate techniques and competently execute them are core to the definition of an expert analyst.
However, even with techniques in hand, an expert analyst will not succeed without an understanding of the business they are evaluating. As stated in the IIBA Competency Model, a generalist may not have specific domain knowledge and may be reliant on other subject matter experts (SMEs) to provide a better understanding. Even specialists who have a depth of knowledge on a given subject may lack a broader understanding of other business practices which affect the project and may require additional sources for this information. These sources range from formal training to informal resources such as customer documentation, whitepapers or online forums. Often this learning is done prior to the project initiation or “on the job” as part of the analysis activities.
So who can be a business analyst? There is no hard and fast rule. Business analysts tend to come from an educational background in business administration or transition into the role based on a given technical path that lent them sufficient domain knowledge to specialize in an area of the business. The techniques described above are often evolved over time by the practitioner. At some point in that evolution, an analyst might develop sufficient experience to transfer those skills to other different operational areas or project types. Fundamentally though, they should all possess critical thinking skills and a desire to solve problems.
 A Guide to the Business Analysis Body of Knowledgeâ (BABOKâ Guide), 2.0 ed., International Institute of Business Analysis, Toronto, Ontario, Canada, 2009, pg. 3
 IIBAâ Business Analysis Competency Model, 2.0 ed., International Institute of Business Analysis, Toronto, Ontario, Canada, 2010, pg. 6