Lecture

AUC Technologies
Business Analysis - Introduction

Projects Consulting, Development, Mentoring, and Training Company
Business Analysis - Introduction
Presented By :
Abubakar Munawar
Project Manager / Lead Business Analyst
abubakar.munawar@gmail.com
AUC Technologies
Agenda
About The Course
What is Business Analysis ?
Some Important Concepts
What is Business Analyst and Why That Role Is Important?
Getting Started As a Business Analyst
Whats In Next Lecture ?
AUC Technologies
Business Analysis ?
Any Idea ?
Any Idea ?
AUC Technologies
About The Course
Knowl
Tasks
Inputs
Tools
&
Techniques
Outputs
Task
Knowledge Area [KA]
Task
AUC Technologies
What is Business Analysis ?
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.
International Institute of Business Analysis [IIBA] - BABOK v2.0
Business analysis is the set of tasks, knowledge, and techniques required to
identify business needs and determine solutions to business problems.
Solutions often include a systems development component, but may also
consist of process improvement or organizational change. The person
who carries out this task is called a Business Analyst or BA.
Those BAs who work solely on developing software systems may be called
IT Business Analysts or Technical Business Analysts.
Wikipedia
AUC Technologies
AUC Technologies
Definition - Solutions
Solution
A solution meets a business need, by solving problems or allowing the organization
to take advantage of an opportunity.
A solution can be subdivided into components, including the information systems
that support it, the processes that manage it, and the people who operate it.
Business analysis helps organizations to define the optimal solution for their needs,
given the set of constraints (including time, budget, regulations, and others) under
which that organization operates.
AUC Technologies
Definition - Scope
Scope
In Project Management, the scope of a project is the sum total of all of its
products and their requirements or features.
In Business Analysis we use 2 predominate definitions for Scope:
In Business Analysis we use 2 predominate definitions for Scope:
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.
AUC Technologies
What is Requirement ?
What is Requirement ?
AUC Technologies
Definition - Requirement
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, specification, or other
solution component to satisfy a contract, standard, specification, or other
formally imposed documents.
3. A documented representation of a condition or capability as in (1) or (2).
Requirement may be unstated, implied by other requirements, or directly
stated and managed.
Requirement must be clearly communicated to & understood by
Stakeholders
AUC Technologies
Types of Requirements ?
Types of Requirements ?
AUC Technologies
Types / Level of Requirement
Business Requirements are higher-level statements of the goals, objectives, or needs of the
enterprise. They describe such things the reasons why a project is initiated, the things that the
project will achieve, and the metrics which will be used to measure its success.
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.
Solution Requirements describe the characteristics of a solution that meets the business
requirements and stakeholder requirements. They are frequently divided, particularly when the
requirements describe a software solution, into:
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
a specific system action or response.
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.
AUC Technologies
Types / Level of Requirement Continue..
Implementation Requirements describe capabilities that the solution must have in
order to facilitate transition from the current state of the enterprise to the desired future
state, but that will not be needed once that transition is complete. They are further
described in the Solution Assessment and Validation.
AUC Technologies
Business Analyst ?
Business Analyst ?
AUC Technologies
Business analyst is one who manages the entire
Systems Requirements Life Cycle from
understanding the business need to ensuring that
the delivered solution meets the need and adds
Business Analyst ?
the delivered solution meets the need and adds
value to the bottom line
Whitepaper published by HP The business analyst : The pivotal I.T. role of the future
AUC Technologies
Why Business Analyst ?
AUC Technologies
If an organization want :
1. to shorten delivery schedules of your project teams
through the reduction of requirements defects
2. to reduce the development effort that is expended on
rework due to miscommunication
3. To reduce user-reported defects which originate in the
requirements phase of a project
AUC Technologies
Business Analyst
&
&
Project Success
AUC Technologies
Business Analyst & Project Success
The projects encounter difficulties not from lack of
technical expertise but from an inability to gather,
understand, analyze and manage business
requirements and convert them into useable
requirements and convert them into useable
system specifications
Whitepaper published by HP The business analyst : The pivotal I.T. role of the future
AUC Technologies
Chaos Factors For Project Success
User Involvement 20%
Executive Management Support 15%
Clear Business Objectives 15%
Agile Optimization 10%
Agile Optimization 10%
Emotional Maturity 10%
Project Management Expertise 10%
Financial Management 5%
Skilled Resources 5%
Formal Methodology 5%
Tools & Infrastructure 5%
AUC Technologies
Key findings from the report, The Impact of Business Requirements on the Success of Technology
Projects from IAG Consulting, include (emphasis added):
1. Companies with poor business analysis capability have three times as many project failures
as successes.
2. 68% of companies are more likely to have a marginal project or outright failure than a success
due to the way they approach business analysis. In fact, 50% of this groups projects were
runaways which had any 2 of: taking over 180% of target time to deliver; consuming in excess of
runaways which had any 2 of: taking over 180% of target time to deliver; consuming in excess of
160% of estimated budget; or delivering under 70% of the target required functionality.
3. Companies pay a premiumof as much as 60% on time and budget when they use poor
requirements practices on their projects.
4. Over 41% of the IT development budget for software, staff and external professional services will
be consumed by poor requirements at the average company using average analysts versus the
optimal organization.
5. The vast majority of projects surveyed did not utilize sufficient business analysis skill to consistently
bring projects in on time and budget. The level of competency required is higher than that employed
within projects for 70% of the companies surveyed.
AUC Technologies
This chart illustrates the requirements skills gap most companies face:
AUC Technologies
The impact of this skills gap is substantial, directly increasing project time, cost, and risk
of failure. The skills gap premium is reflected in this graph:
AUC Technologies
According to survey respondents, the top three risks
threatening the success of projects are :
Unstable, constantly changing requirements (66%)
Poor requirement specification (55%)
Poor requirement specification (55%)
Client behavior, such as approval delays, requirements
changes and poor communication (42%)
AUC Technologies
Good requirement reduce errors :
60% of software errors are
requirement errors
If errors are found during the
If errors are found during the
requirement phase, the cost is
$1.00
If found during testing, the cost is
$100
AUC Technologies
Why Project Manager
Unable to Handle These
Unable to Handle These
Failure ?
AUC Technologies
Why Project Manager Unable to Handle These
Failure ?
PM Role : A project manager is accountable for developing &
delivering a Solution within budget & timelines will limited
resources using Project as a vehicle
Solution
Cost
(Resources)
Time
(Schedule)
Project Scope
AUC Technologies
Why Project Manager Unable to Handle These
Failure ?
BA Role : A business analyst is accountable for defining &
ensuring the right Solution is delivered using their Skills as a
vehicle
Solution
People
Process
Technology
AUC Technologies
Therefore, Project Manager
Need a partner ?
Need a partner ?
AUC Technologies
Lets Collaborate with Your Requirement Lead -
The Business Analyst
Requirements
Design
Built & Test
Implementation /
Transition
Post Implementation
AUC Technologies
Project Manager &
Business Analyst
Business Analyst
Collaboration Model
AUC Technologies
During Project Initiation
1. Communicates the Stakeholder Vision & Objectives to PM
2. Communicates the solutions scope & requirements efforts to allow PM to
start planning process
Project Manager & Business Analyst
Collaboration Model
Assess Risk of Requirements
Assess Risk of Requirements
1. The biggest issue raise the requirement error & delay is lack of SME &
Stakeholder Participation, therefore BA helps PM in identification of
stakeholder by using requirements planning techniques
2. The BA also identify business roles & responsibilities of SME,
Stakeholders & Project TEAM to ease the communication throughout the
project
AUC Technologies
BA Plans the Requirement Efforts
1. The BA add value by providing time inputs to PM for :
Gather, Analyze, Review & Document Information
Coordinate with team & clients
Project Planning
Collaboration Model
Project Planning
1. Requirement Planning
2. Ensures Availability of SMEs
3. Effective Elicitation Techniques & detail analysis results in Complete
Requirements
4. Verification & Validation of requirements ensure SME involvement,
ownership & manage expectations of Stakeholders
5. Prioritized requirements for better planning & execution
AUC Technologies
BA Role During Design Phase
1. Business TEAM
Ensure business changes are incorporated
Usable Interface
2. Design TEAM
Collaboration Model
2. Design TEAM
Assist design team in identification of best implementation strategy
Assist in making trade-off decisions
Review designs & specification to ensure business feasibility
3. Management
Update the requirements as necessary
Identify Conflicting & Orphan Requirements
Communicates the Impactss
AUC Technologies
BA Role During Built & Testing
1. Built / Unit Testing
Ensure built addresses the required business need
2. System / Integration Testing
Confirm all requirements (overall) addressed in the system
Non-functional requirements are clearly defined & met
Collaboration Model
Non-functional requirements are clearly defined & met
Participate in identification & resolution of defects
3. Management
Update the requirements as necessary
Identify Conflicting & Orphan Requirements
Communicates the Impacts
Update the quality & status of built so that corrective actions can be taken
AUC Technologies
BA Role During Scope Management
The BA manage solution scope through Requirement Traceability Matrix.
This help project manager in identification of whats in scope and whats
not ? along with impact of any change in requirement.
BA Role During Implementation & Transition
Collaboration Model
BA Role During Implementation & Transition
Ensure users are prepared to receive the product
Manage the resistance to change
Observe Product / Solution in Business Environment
Describe the current & future states
Identify Transition Requirements, facilitate transition & validate transition
succeeding
AUC Technologies
Standardized Approach to software development
lifecycle keeping in mind the business needs
Better Business Process
Good Requirements
Transparent Communications
What Results BA Will Bring To Your Organization ?
Transparent Communications
Enhance Risk Management
Efficiency
Customer Satisfaction
Cost Reduction
AUC Technologies
Working together PM & BA are
Element of Success For Project and
Solution
AUC Technologies
Get Started As A Business Analyst
1. www.theIIBA.org
2. www.ModernAnalyst.com
3. www.BusinessAnalystMentor.com
4. www.LinkedIn.com
1. BA Forum
1. BA Forum
2. Business Analysis Professionals
3. Modern Analyst
4. IIBA
5. www.RequirementsNetwork.com
6. www.PracticalAnalyst.com
7. www.Bridging-The-Gap.com
8. www.BetterProjects.net
AUC Technologies
Get Started As A Business Analyst [Books]
1. Seven Steps to Mastering Business Analysis by Barbara A. Carkenord
2. The Business Analyst's Handbook by Howard Podeswa
3. Business Analysis by Debra Paul and Donald Yeates
4. CBAP Certification Study Guide (2nd Edition) by Richard Larson and Elizabeth Larson
5. Sample Exam Questions: IIBA Certified Business Analysis Professional (CBAP) by
5. Sample Exam Questions: IIBA Certified Business Analysis Professional (CBAP) by
Larry T. Barnard
AUC Technologies
Questions

Lecture

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lecture

Uploaded by

Copyright:

Available Formats

AUC Technologies

Business Analysis - Introduction

You might also like