In theory, a “Business Analyst” (or “BA”) is the intermediary between business people and the Information Technology staff. It is his/her responsibility to interpret and define the information requirements of the business, and devise a suitable system to solve the need, be it a packaged solution or in-house development (or both). Years ago, this function was commonly referred to as a “Systems Analyst,” but this dropped out of vogue in the 1980’s as “Software Engineers” became the rage. “Systems Analyst” was eventually replaced by “Business Analyst” as a way of distinguishing the differences of systems and software. Yet, when you read a BA job description today, it calls for knowledge of such things as SQL, Oracle, Agile development, or programming languages. In other words, they are not true Business Analysts.
This makes me wonder if the industry really grasps the duties and responsibilities of the BA. The industry talks about such people, but have we standardized a job description? We wrote several such descriptions as part of our “PRIDE” Methodologies for IRM and based on this, let me see if I can establish a standard job description:
BUSINESS ANALYSIS (“BA”)
SCOPE OF FUNCTION
The purpose of this function is to design reliable information systems that satisfy the information requirements of the enterprise and are easy to modify and maintain in the most cost effective means possible.
SPECIFIC DUTIES AND RESPONSIBILITIES
* Reports administratively to Systems Resource Management on all activities, and to Project Management on all project specific activities.
* Maintains a line of communication with Enterprise Engineering, Program/Software Engineering, Data Engineering, User Management, Operations, and support functions.
* Reviews pertinent deliverables resulting from pertinent design methodologies with Project Management and the support functions (e.g., QA).
* Prepares project scopes subject to Project Management approval.
* Documents existing information systems.
* Interviews end-users to specify information requirements.
* Analyzes and details information requirements.
* Reviews formal and informal deliverables resulting from pertinent design methodologies with users for accuracy.
* Develops system solutions that can satisfy information requirements in the most cost effective means possible. This includes preparing complete rough designs of systems, and the evaluation of purchased packages to satisfy the requirements.
* Participates in project planning activities, including estimating and scheduling, and cost evaluation.
* Performs system design; this includes breaking systems into sub-systems (aka “Business Processes”).
* Prepares complete examples (illustrative) of outputs and inputs for users to review/approve.
* Performs sub-system design; this includes breaking sub-systems into procedural work flows.
* Prepares administrative procedures for users to execute the manual aspects of systems.
* Works with Program/Software Engineering in providing specifications regarding computer procedures.
* Educates users in the operation of new or modified systems.
* Develops system test plans and performs the tests in cooperation with Program/Software Engineering.
* Designs the logical data base models for applications. This includes defining the “objects,” “views,” and data elements required by information systems. Data Engineering serves in an advisory capacity.
REQUIRED KNOWLEDGE/SKILLS/EXPERIENCE
* An in-depth understanding of in-house methodologies, standards, tools, and techniques.
* The ability to estimate BA activities within tolerances as established by the installation.
* Good interpersonal relations/communications skills.
* Effective writing skills.
* Possess good analytical and problem solving skills.
* Must be results oriented.
* The ability to prepare and conduct project review meetings and participate in those reviews in a professional manner.
* A thorough understanding of development functions.
* The experience and ability to assume responsibility for performing assigned tasks and meeting objectives within time and cost constraints.
* An in-depth understanding of the user organization being served; this includes the information required by users to function properly.
* A perceptive listener, able to suggest areas where information and systems can provide additional benefits to the user.
* The ability to distinguish between real and imagined business needs and diplomatically point them out to the user.
* Capable of discussing user information needs in business terminology, avoiding the use of technical terms where possible.
* Sensitive to the needs of the user and understands the role of the new system in achieving the user’s objectives.
* General understanding of the use of computers to meet system processing requirements.
EVALUATION OF PERFORMANCE
The following list is intended as a guide to evaluate the performance of the BA function. Evaluation will be based upon observation by Systems Resource Management, Project Management, User Management, Program/Software Engineering, and Quality Assurance.
* BA personnel adheres to all pertinent policies and procedures.
* BA personnel have a thorough understanding and knowledge of all development related functions and responsibilities.
* Systems Resource Management, Project Management, Program/Software Engineering, and support functions are aware of all BA activities.
* BA personnel assume responsibility for performing assigned tasks and achieves them within time and cost constraints.
* BA activities are performed according to approved plans.
* BA staff produces quality work (few mistakes).
* BA Works closely with the various development support functions to assure that all pertinent standards are properly followed.
* BA work is thorough and professionally prepared.
* Systems are standardized and controlled; they are also easy to modify and maintain.
* Systems are designed correctly, according to specifications, and are reliable.
* Information requirements accurately reflect users needs.
* System designs are creative and practical.
* Application logical data base designs are correctly defined.
* Writes effectively and clearly.
* Systems are well tested and free of known defects.
FUNCTIONAL RELATIONSHIPS
Function is administratively subordinate to Systems Resource Management and operationally subordinate to Project Management for project activities. Maintains a lateral working relationship with Program/Software Engineering, Data Engineering, Enterprise Engineering, User Management, and support functions (e.g., QA).
If the company has standardized on a methodology, I would add the phases and activities the BA is responsible for executing, reviewing, and approving.
Maybe this is a good starting point to bring uniformity to Business Analysis. By the way, you will notice there is no mention of programming and DBMS skills. They have their place, but it certainly isn’t with Business Analysis.
Keep the Faith!
Note: All trademarks both marked and unmarked belong to their respective companies.
Tim Bryce is a writer and the Managing Director of M&JB Investment Company (M&JB) of Palm Harbor, Florida and has over 30 years of experience in the management consulting field. He can be reached at [email protected]
For Tim’s columns, see: timbryce.com
Copyright © 2014 by Tim Bryce. All rights reserved.