Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

IFS SELF NOTES UNIT 1 (BUSINESS ANALYSIS)

Business Analysis Historical Context


Business Analysis Evolution
• Emergence in the 1980s and 1990s.
• Emergence as a distinct area from software engineering.
IT Developments and Business Operations
• IT advancements improve business operations and management decisions.
• IT departments focus on business operations.
• Emphasis shifts to new services and products development.

What is business analysis?


Business Analysis Definition
• Enables change in enterprises by defining needs and recommending value-
delivering solutions.
• Aids in articulating needs and rationale for change.
• Design and describe solutions delivering value.

Business Analysis Benefits


• Understanding company structure and dynamics.
• Understanding current problems in the target organization.
• Identifying improvement potentials and recommending solutions.
• Identifying and articulating change need.
• Maximizing value delivered to stakeholders.

The Business Analysis Core Concept Model (BACCM)


Need Definition and Importance
• Problem, opportunity, or constraint requiring resolution.
• Starts project.
• Arises from current organizational state.
Organizational Solutions Overview
• Specific ways to address needs or problems.
• Satisfying organizational needs through one or multiple solutions.
• Solutions can be specific to different organizations or situations.
Organizational Change Overview
• Recognizes need and requires solution.
• Chooses best-fitting solution.
• Implements solution internally or through vendor.
• Implements changes within organization, including team and process changes.
Context in Organizational Solutions
• Represents environment for implementation.
• Includes organizational background, structure, locations.
• Influences decision to select solution.

Value in Stakeholder Investment


• Refers to worth, importance, or usefulness.
• Investment in solution based on value.
• Can be tangible or intangible.

BABOK Stakeholder Categories Overview


• Business analyst, customer.
• Domain subject matter expert.
• End user.
• Implementation subject matter expert.
• Operational support.
• Project manager.
• Regulator.
• Sponsor.
• Supplier.
• Tester.
WHAT IS A BUSINESS ANALYSTS
Business Analyst Role
• Liaison among stakeholders for gathering, analyzing, communicating, and
validating requirements for business changes.
• Understands business problems and opportunities within requirements context.
• Recommends solutions to achieve organizational goals.

Business Analyst Role


• Identifies business needs.
• Determines solutions to problems.
• Solutions may include systems development, process improvement, or
organizational change.
• Understands stakeholder needs.
• Bridges business and IT.

Difference between BA, SA, PM


Business Analyst Role Overview
• Understanding business processes and procedures.
• Identifying areas of improvement.
• Collaborating with stakeholders for suitable solutions.
BA's Role in Information System Development
• Gathering, analyzing, documenting business requirements.
• Fulfilling software's functionality.
Systems Analyst Role Overview
• Understanding business requirements.
• Designing and documenting software/IT system implementation.
Systems Analyst Role:
• Researching systems.
• Conducting code reviews.
• Conducting data analysis/modelling.

Project Manager
Project Manager role
• Successfully planning and executing projects.
• Managing people, money, and risk.
• Ensuring team follows project plan.
Role Overview:
• Planning & Defining Scope
• Activity Planning & Sequencing
• Resource Planning
• Developing Schedules
• Time & Cost Estimating
• Analyzing & Managing Risks
• Monitoring & Reporting Progress

Building a house vs building an IS


Generic steps in process

 Initiation
 Analysis
 Design
 Construction
 Maintenance

House Maintenance vs Car Maintenance


• House maintenance less than car maintenance.
• Programmers involved in 2 out of 5 stages.
• Defines necessary tasks, roles, and methods.

Computer Systems Development


• Involves understanding user requirements.
• Designing efficient, effective solutions.

Competences for a Business Analyst


What is a Competency?
Business Analyst Competencies Overview
• Behavioral skills: Communication, analytical thinking, problem-solving, teamwork.
• Business knowledge: Business case development, IT principles.
• Techniques: Project management, business process modelling, facilitation
techniques.
What is e-competence?
Effective Application of Knowledge, Skills, and Attitudes
• Proficient use of cognitive, psychomotor, and affective domains.
• Effective use of technology.
• Effective management of data and information.
• Achieving quality output and desired outcomes.
Knowledge
Knowledge Overview
• Theoretical/declarative.
• Practical.
• Procedural.
• Contextual.
Skills
knowledge Application
• Understanding 'how' to apply knowledge.
Attitudes
Adapting Mindset to Evolving Contexts
• Understanding people's thoughts and motivations.

E-competencies for a Business Analyst


Business Analyst Competencies:
• Technical Competency: Use of relevant IT and critical thinking skills.
• Business Competency: Knowledge of the organization's business processes.
• Knowledge Management Competency: Use of existing or new knowledge to solve
complex problems.
• Leadership and Supervision Competency: Ability to lead people, communicate, and
give direction.
• Social & Emotional Competency: Ability to create and maintain relationships with
team members, business users, IT departments, and managers.
• Intrapersonal Skills: Self-management, assertiveness, and timely project delivery.

You might also like