1. Business analysis Lecturer: Kotlik Andrey Valeriyevich
Management and business department

2. Introduction to the Business Analysis (BA)
The essence and scope of BA
BA standards
Stages of BA & knowledge areas
Business analysts’ roles

3. The essence and scope of BA
Business analysis is a process of business needs identification and development of solutions to meet such needs on strategic, tactical and operational levels
Business analysis is the set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies, and operations of an organization, and recommend solutions that enable the organization to achieve its goals.

4. The essence and scope of BA
Problem (need)
Managerial tools BA
IT tools
Solution
Managerial tools are in priority

5. The essence and scope of BA

6. The essence and scope of BA

7. The essence and scope of BA
Initiation
Analysis
Design
Implementation

8. Published by The International Institute of Business Analysis (IIBA)
BA standards
Business Analysis Body of Knowledge™ (BABOK) is the written guide to the collection of BA knowledge reflecting current best practice, providing a framework that describes the areas of knowledge, with associated activities and tasks and techniques required.
Published by The International Institute of Business Analysis (IIBA)
Version 2.0 was released 31 March 2009

9. A domain is the area undergoing analysis.
BA standards
A domain is the area undergoing analysis.
It may correspond to the boundaries of an organization or organizational unit, as well as key stakeholders outside those boundaries and interactions with those stakeholders.

10. Context - is part of the environment that embraces change.
BA standards
Context - is part of the environment that embraces change.
Essentially context includes everything that is related to change, excluding the change itself. Context may also include elements such as culture, infrastructure, relationships and other, that is relevant to business changes. Context is an addition to the group of key concepts in version 3.0.

11. BA standards
A solution is a set of changes to the current state of an organization that are made in order to enable that organization to meet a business need, solve a problem, or take advantage of an opportunity.
The scope of the solution is usually narrower than the scope of the domain within which it is implemented, and will serve as the basis for the scope of a project to implement that solution or its components.

12. BA standards
The term “scope” is used to mean a number of different things, but two definitions predominate:
Solution scope is the set of capabilities a solution must support to meet the business need.
Project scope is the work necessary to construct and implement a particular solution.

13. BA standards
Most solutions are a system of interacting solution components, each of which are potentially solutions in their own right.
Examples of solutions and solution components include:
software applications,
web services,
business processes,
the business rules that govern that process,
an information technology application,
a revised organizational structure,
outsourcing, insourcing,
redefining job roles,
or any other method of creating a capability needed by an organization.

14. BA standards
Business analysis helps organizations define the optimal solution for their needs, given the set of constraints (including time, budget, regulations, and others) under which that organization operates.

15. BA standards
Change is defined as the controlled transformation of the organization Changes mean that the business analyst must:
prepare organizations and stakeholders to change;
trigger changes to meet business needs;
prevent changes when they are not required. «Changes» concept is occurred in version 3.0 of BABOK.

16. BA standards
A requirement is:
1) A condition or capability needed by a stakeholder to
solve a problem or achieve an objective.
2) A condition or capability that must be met or possessed
by a solution or solution component to satisfy a contract,
standard, specifcation, or other formally imposed
documents.
3) A documented representation of a condition or capability
as in (1) or (2).

17. BA standards
A requirement may be unstated, implied by or derived from other requirements, or directly stated and managed.
One of the key objectives of business analysis is to ensure that requirements are visible to and understood by all stakeholders.
When reading the BABOK® Guide, however, it is vital that “requirement” be understood in the broadest possible sense. Requirements include, but are not limited to, past, present, and future conditions or capabilities in an enterprise and descriptions of organizational structures, roles, processes, policies, rules, and information systems. A requirement may describe the current or the future state of any aspect of the enterprise.

18. BA standards
For the purposes of the BABOK® Guide, the following classification scheme is used to describe requirements:
Business Requirements
Stakeholder Requirements
Solution Requirements
Transition Requirements

19. BA standards
Business Requirements are higher-level statements of the goals, objectives, or needs of the enterprise.
They describe the reasons why a project has been initiated, the objectives that the project will achieve, and the metrics that will be used to measure its success.
Business requirements describe needs of the organization as a whole, and not groups or stakeholders within it. They are developed and defined through enterprise analysis.

20. BA standards
Stakeholder Requirements are statements of the needs of a particular stakeholder or class of stakeholders.
They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution.
Stakeholder requirements serve as a bridge between business requirements and the various classes of solution requirements. They are developed and defined through requirements analysis.

21. BA standards
Solution Requirements describe the characteristics of a solution that meet business requirements and stakeholder requirements. They are developed and defined through requirements analysis. They are frequently divided into sub-categories, particularly when the requirements describe a software solution:
Functional Requirements describe the behavior and information that the solution will manage. They describe capabilities the system will be able to perform in terms of behaviors or operations – specific information technology application actions or responses.
Non-functional Requirements capture conditions that do not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the systems must have. They are also known as quality or supplementary requirements. These can include requirements related to capacity, speed, security, availability and the information architecture and presentation of the user interface

22. BA standards
Transition Requirements describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state, but that will not be needed once that transition is complete.
They are differentiated from other requirements types because they are always temporary in nature and because they cannot be developed until both an existing and new solution are defined.
They typically cover data conversion from existing systems, skill gaps that must be addressed, and other related changes to reach the desired future state. They are developed and defined through solution assessment and validation.

23. BA standards
Version 3.0 also includes the concept of "value."   Business needs (requirements) should provide the potential value that can be measured in various ways:
increase in sales,
risk reduction
cost reduction,
process throughput time reduction,
increase opportunities,
increasing productivity, etc.

24. BA standards
A task is an essential piece of work that must be performed as part of business analysis.
Each task should be performed at least once during the vast majority of business analysis initiatives, but there is no upper limit to the number of times any task may be performed.
Tasks may be performed at any scale.
Each task may be performed over periods ranging from several months in time to a few minutes.
Task can be performed formally or informally.

25. BA standards
A task must have the following characteristics:
A task accomplishes a result in an output that creates value—that is, if we perform a task we agree that something useful has been done
A task is complete—in principle successor tasks that make use of outputs should be able to be performed by a different person
A task is a necessary part of the purpose of the knowledge area (KA) to which it belongs

26. BA standards
The BABOK® Guide does not prescribe a process or an order in which tasks are performed.
Some ordering of tasks is inevitable, as certain tasks produce outputs that are required inputs for other tasks.
However, it is important to keep in mind that the BABOK® Guide only prescribes that the input must exist.

27. BA standards
Each task in the BABOK® Guide is presented in the following format:
Purpose is a short description of the reason for a business analyst to perform the task and the value created through performing the task.
Description explains in greater detail why the task is performed, what the task is, and the results the task should accomplish
An input represents the information and preconditions necessary for a task to begin

28. BA standards
Task Input/Output Diagrams

29. BA standards
Requirements to inputs
Elements of a task describes key concepts that are needed to understand how to perform the task
Techniques
Stakeholders
An output is a necessary result of the work described in the task.

30. BA standards
Techniques provide additional information on different ways that a task may be performed or different forms the output of the task may take (examples: Brainstorming, Financial Analysis, Observation, Process Modeling etc.)
A task may have none, one, or more related techniques.
A technique must be related to at least one task.

31. BA standards
Knowledge areas define what a practitioner of business analysis needs to understand and the tasks a practitioner must be able to perform.
Business analysts are likely to perform tasks from all knowledge areas in rapid succession, iteratively, or simultaneously.
Knowledge areas are not intended to represent phases in a project.

32. BA standards
A knowledge area groups a related set of tasks and
techniques.
Techniques frequently apply to multiple KAs:
1) If the technique applies to significantly more tasks in one KA than any others, it will be described there.
2) If the technique applies to a similar number of tasks, it will appear in the first KA in which it is described

33. BA standards
A methodology determines which business analysis tasks
and techniques are used to solve a business problem.
Unlike a technique, which is leveraged by some of the tasks
performed, a methodology will generally affect all of the
tasks that are performed during the course of a project.

34. Stages of BA & knowledge areas

35. Stages of BA & knowledge areas

36. Stages of BA & knowledge areas
Business Analysis Planning and Monitoring describes how
to determine which activities are necessary to perform
in order to complete a business analysis effort. It covers
identifcation of stakeholders, selection of business
analysis techniques, the process we will use to manage
our requirements, and how we assess the progress of the
work in order to make necessary changes in work effort.
Purpose:
Plan the execution of business analysis tasks
Update or change the approach to business analysis as required
Assess effectiveness of and continually improve business analysis practices

37. Stages of BA & knowledge areas
Business Analysis Planning and Monitoring includes such tasks:
Conduct Stakeholder Analysis
Plan Business Analysis Activities (determine BA deliverables, scope of works, tasks, task dependencies and measures)
Plan Business Analysis Communication
Plan Requirements Management Process (who and how will state requirements, who will be informed about it etc.)
Plan, monitor and Report on Business Analysis Performance

38. Stages of BA & knowledge areas
Enterprise Analysis describes how we take a business
need, refine and clarify the definition of that need, and
define a solution scope that can feasibly be implemented
by the business. It covers problem definition and analysis,
business case development, feasibility studies, and the
definition of a solution scope.
Purpose
Identify and propose projects that meet strategic needs and
goals.

39. Stages of BA & knowledge areas
Enterprise Analysis includes such tasks:
Identify Business Need
Determine Solution Approach
Define Solution Scope (context diagram, product structure)
Develop the Business Case (the reasoning for initiating a project or task)

40. Stages of BA & knowledge areas
Elicitation describes how we work with stakeholders to find
out what their needs are and ensure that we have correctly
and completely understood their needs.
Purpose
Explore, identify and document TRUE stakeholder needs.

41. Stages of BA & knowledge areas
Elicitation includes such tasks:
Prepare for Elicitation (all needed resources are organized and scheduled)
Conduct Elicitation
Document Elicitation Results
Confrm (Validate) Elicitation Results

42. Stages of BA & knowledge areas
Requirements Analysis describes how we progressively
elaborate the solution defnition in order to enable the
project team to design and build a solution that will meet
the needs of the business and stakeholders
Purpose
Progressively elaborate stated requirements to suffcient level of detail that accurately defnes the business need within specifed scope
Validate requirements meet the business need
Verify requirements are acceptable quality

43. Stages of BA & knowledge areas
Requirements Analysis includes such tasks:
Organize Requirements into logical set
Prioritize Requirements
Specify and Model Requirements
Determine Assumptions and Constraints
Verify Requirements (requirements meet stakeholders’ intentions and needs)
Validate Requirements (requirements meet business needs)

44. Stages of BA & knowledge areas
Solution Assessment and Validation describes how to
assess proposed solutions to determine which solution
best fits the business need, identify gaps and shortcomings
in solutions, and determine necessary workarounds
or changes to the solution.
It also describes how we assess deployed solutions to see how well they met the original need in order to enable businesses to assess the performance and effectiveness of projects.
Purpose
Assess solutions to ensure that strategic goals are met and requirements are satisfied.

45. Stages of BA & knowledge areas
Solution Assessment and Validation includes such tasks:
Assess Requirements Coverage
Allocate Requirements (among releases and/or solutions components to hardware, software, manual procedures, etc.)
Determine Organizational Readiness
Validate Solution (if solution meets the business need)
Evaluate Solution (the value of the solution as deployed to the business; actual vs. expected costs and benefits)

46. Stages of BA & knowledge areas
Requirements Management and Communication describes
how we manage conflicts, issues and changes and
ensure that stakeholders and the project team remain
in agreement on the solution scope.
Depending on the complexity and methodology of the project, this may require that we manage formal approvals, baseline and track different versions of requirements documents, and trace requirements from origination to implementation.

47. Stages of BA & knowledge areas
Purpose
Recognize that communication takes places throughout all knowledge areas and is important for managing requirements
Manage the approved solution and requirements scope
Ensure stakeholders have access to business analysis work products
Prepare and communicate requirements to stakeholders
Facilitate enterprise consistency and effciency by reusing requirements whenever possible

48. Stages of BA & knowledge areas
Requirements Management and Communication includes such tasks:
Manage Solution and Requirements Scope (Baseline and manage changes to business case, solution and requirements)
Manage Requirements Traceability
Maintain Requirements for re-use
Prepare Requirements Package (documentation, formulation, and organization of all the requirements the business analyst has gathered from the stakeholders, packaged in a comprehensive set of project requirements)
Communicate requirements

49. Stages of BA & knowledge areas

50. Business analysts’ roles
Strategist (environment, strategy, policy)
Business architect (business processes level)
System analyst (requirements for IT)
Goals:
To analyze business needs and requirements
To develop a solution
To document it