Underlying Competencies

The underlying competencies are skills, knowledge and personal characteristics that
support the effective performance of business analysis. The underlying competency areas
relevant to business analysis include:

Analytical Thinking and Problem Solving supports effective identification of business

problems, assessment of proposed solutions to those problems, and understanding of the
needs of stakeholders. Analytical thinking and problem solving involves assessing a
situation, understanding it as fully as possible, and making judgments about possible
solutions to a problem.

Behavioral Characteristics support the development of effective working relationships

with stakeholders and include qualities such as ethics, trustworthiness, and personal
organization.

Business Knowledge supports understanding of the environment in which business

analysis is performed and knowledge of general business principles and available solu-
tions.

Communication Skills support business analysts in eliciting and communicating

requirements among stakeholders. Communication skills address the need to listen to and
understand the audience, understanding how an audience perceives the business analyst,
understanding of the communications objective(s), the message itself, and the most
appropriate media and format for communication.

Interaction Skills support the business analyst when working with large numbers of
stakeholders, and involve both the ability to work as part of a larger team and to help that
team reach decisions. While most of the work of business analysis involves identifying
and describing a desired future state, the business analyst must also be able to help the
organization reach agreement that the future state in question is desired through a
combination of leadership and facilitation.

Software Applications are used to facilitate the collaborative development, recording

and distribution of requirements to stakeholders. Business analysts should be skilled users
of the tools used in their organization and must understand the strengths and weaknesses
of each.
 BA Knowledge Areas

Business Analysis Planning and Monitoring Knowledge Area defines the tasks
associated with the planning and monitoring of business analysis activities, including:

2.1 Plan Business Analysis Approach

This task describes how to select an approach to performing business analysis, which
stakeholders need to be involved in the decision, who will be consulted regarding and
informed of the approach, and the rationale for using it.

2.2 Conduct Stakeholder Analysis

This task covers the identification of stakeholders who may be affected by a proposed
initiative or who share a common business need, identifying appropriate stakeholders for
the project or project phase, and determining stakeholder influence and/or authority
regarding the approval of project deliverables.

2.3 Plan Business Analysis Activities

Determine the activities that must be performed and the deliverables that must be pro-
duced, estimate the effort required to perform that work, and identify the management
tools required to measure the progress of those activities and deliverables.

2.4 Plan Business Analysis Communication

A business analysis communications plan describes the proposed structure and schedule
for communications regarding business analysis activities. Record and organize the
activities to provide a basis for setting expectations for business analysis work, meetings,
walkthroughs, and other communications.

2.5 Plan Requirements Management Process

Define the process that will be used to approve requirements for implementation and
manage changes to the solution or requirements scope.

2.6 Manage Business Analysis Performance

To manage the performance of business analysis activities to ensure that they are ex-
ecuted as effectively as possible.
Eliciting requirements is a key task in business analysis. Because the requirements
serve as the foundation for the solution to the business needs it is essential that the
requirements be complete, clear, correct, and consistent. Leveraging proven means to
elicit requirements will help meet these quality goals.

3.1 Prepare for Elicitation

Ensure all needed resources are organized and scheduled for conducting the elicitation
activities.

3.2 Conduct Elicitation Activity

Meet with stakeholder(s) to elicit information regarding their needs.

3.3 Document Elicitation Results

Record the information provided by stakeholders for use in analysis.

3.4 Confirm Elicitation Results

Validate that the stated requirements expressed by the stakeholder match the stake-
holder’s understanding of the problem and the stakeholder’s needs.
Requirements Management and Communication Knowledge Area describes the
activities and considerations for managing and expressing requirements to a broad and
diverse audience. These asks are performed to ensure that all stakeholders have a shared
understanding of the nature of a solution and to ensure that those stakeholders with
approval authority are in agreement as to the requirements that the solution shall meet.

4.1 Manage Solution Scope & Requirements

Obtain and maintain consensus among key stakeholders regarding the overall solution
scope and the requirements that will be implemented.

4.2 Manage Requirements Traceability

Create and maintain relationships between business objectives, requirements, other team
deliverables, and solution components to support business analysis or other activities.

4.3 Maintain Requirements for Re-use

To manage knowledge of requirements following their implementation.

4.4 Prepare Requirements Package

To select and structure a set of requirements in an appropriate fashion to ensure that the
requirements are effectively communicated to, understood by, and usable by a
stakeholder group or groups.

4.5 Communicate Requirements

Communicating requirements is essential for bringing stakeholders to a common un-

derstanding of requirements.
Enterprise Analysis Knowledge Area describes the business analysis activities
necessary to identify a business need, problem, or opportunity, define the nature of a
solution that meets that need, and justify the investment necessary to deliver that solution.
Enterprise analysis outputs provide context to requirements analysis and to solution
identification for a given initiative or for long-term planning. Enterprise analysis is often
the starting point for initiating a new project and is continued as changes occur and more
information becomes available. It is through enterprise analysis activities that business
requirements are identified and documented.

5.1 Define Business Need

Identify and define why a change to organizational systems or capabilities is required.

5.2 Assess Capability Gaps

To identify new capabilities required by the enterprise to meet the business need.

5.3 Determine Solution Approach

To determine the most viable solution approach to meet the business need in enough
detail to allow for definition of solution scope and prepare the business case.

5.4 Define Solution Scope

To define which new capabilities a project or iteration will deliver.

5.5 Define Business Case

To determine if an organization can justify the investment required to deliver a proposed

solution.
Requirements Analysis Knowledge Area describes the tasks and techniques used by
a business analyst to analyze stated requirements in order to define the required capa-
bilities of a potential solution that will fulfill stakeholder needs. It covers the definition of
stakeholder requirements, which describe what a solution must be capable of doing to
meet the needs of one or more stakeholder groups, and solution requirements, which
describe the behavior of solution components in enough detail to allow them to be
constructed. The tasks in this knowledge area apply to both stakeholder and solution
requirements.

6.1 Prioritize Requirements

Prioritization of requirements ensures that analysis and implementation efforts focus on

the most critical requirements.

6.2 Organize Requirements

The purpose of organizing requirements is to create a set of views of the requirements for
the new business solution that are comprehensive, complete, consistent, and understood
from all stakeholder perspectives.

6.3 Specify and Model Requirements

To analyze expressed stakeholder desires and/or the current state of the organization
using a combination of textual statements, matrices, diagrams and formal models.

6.4 Define Assumptions and Constraints

Identify factors other than requirements that may affect which solutions are viable.

6.5 Verify Requirements

Requirements verification ensures that requirements specifications and models meet the
necessary standard of quality to allow them to be used effectively to guide further work.

6.6 Validate Requirements

The purpose of requirements validation is to ensure that all requirements support the
delivery of value to the business, fulfill its goals and objectives, and meet a stakeholder
need.
Solution Assessment and Validation Knowledge Area describes the tasks that are
performed in order to ensure that solutions meet the business need and to facilitate their
successful implementation. These activities may be performed to assess and validate
business processes, organizational structures, outsourcing agreements, software
applications, and any other component of the solution.

7.1 Assess Proposed Solution

To assess proposed solutions in order to determine how closely they meet stakeholder
and solution requirements.

7.2 Allocate Requirements

Allocate stakeholder and solution requirements among solution components and releases
in order to maximize the possible business value given the options and alternatives
generated by the design team.

7.3 Assess Organizational Readiness

Assess whether the organization is ready to make effective use of a new solution.

7.4 Define Transition Requirements

To define requirements for capabilities needed to transition from an existing solution to a

new solution.

7.5 Validate Solution

Validate that a solution meets the business need and determine the most appropriate
response to identified defects.

7.6 Evaluate Solution Performance

Evaluate functioning solutions to understand the value they deliver and identify oppor-
tunities for improvement.