Scribd
Upload
5 views

BA Activities

The document outlines key activities involved in business analysis (BA) that drive project success, detailing phases from inception to delivery. It includes processes such as stakeholder analysis, current state discovery, gap analysis, and requirements documentation. The emphasis is on equipping individuals with the skills to effectively perform BA activities and contribute value to delivery teams.

Uploaded by

ec es
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

BA Activities

The document outlines key activities involved in business analysis (BA) that drive project success, detailing phases from inception to delivery. It includes processes such as stakeholder analysis, current state discovery, gap analysis, and requirements documentation. The emphasis is on equipping individuals with the skills to effectively perform BA activities and contribute value to delivery teams.

Uploaded by

ec es
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

BUSINESS ANALYSIS

KEY ACTIVITIES

The actual BA activities


that move projects
forward

Planning Delivery
Inception & Planning
Phase
What High-Level Description

Business Analysis Outlines the approach, activities, deliverables, and timelines for
Plan conducting business analysis work throughout the project.
Includes methods, tools, and stakeholder engagement strategies.

Stakeholder Identifies key stakeholders, their interests, influence, and


Analysis communication needs. Helps ensure the right people are engaged
at the right time.

Current State Gathers information about existing systems, processes, and


Discovery business context through document reviews, workshops, and
interviews.

Current State Visual representations (e.g., process models, customer journeys,


Process Models etc.) of how the business currently operates, identifying inputs,
outputs, roles, and tools used.

Conceptual Future High-level view of the desired future business processes,


State Design capabilities, and changes needed to meet business goals.

Gap Analysis Compares the current state to the future state to identify
differences, gaps, and the scope of work required to bridge them.

Options Analysis Evaluates potential solution options or approaches, considering


benefits, risks, feasibility, and alignment with business needs.

High-Level Captures early-stage business, functional, and non-functional


Requirements requirements. I write these as user stories to focus on business
outcomes to guide solution design.

Business Impact Assesses the implications of proposed changes on people,


Assessment processes, systems, and policies. Highlights areas needing change
management and support.
@Matthew Thomas Holliday
Execution / Delivery
Phase
What High-Level Description

Detailed Elaborates on high-level requirements to define system


Requirements behaviours, business rules, and interactions. Again, I write
these as detailed user stories with acceptance criteria. I may
also include additional tools to help add context to complex
requirements (fit for purpose).

Use Cases (where Describes specific interactions between users (actors) and the
relevant) system to achieve a goal. Helps define detailed system
behaviour and supports development and testing activities.

Future State Detailed visual representations of how processes will operate


Business Process once the solution is implemented. Includes roles, activities,
Models decision points, and system interactions.

Detailed Business Provides a detailed view of how the new solution will affect
Impact Assessment teams, systems, processes, policies, and training needs. This
supports planning for change and operational readiness.

Requirements A tool to map and track requirements through the project


Traceability Matrix lifecycle - linking business needs to functional requirements,
(RTM) and Coverage design, test cases, and delivered functionality. Ensures nothing
is missed.

User Acceptance Supports the business in defining test scenarios and


Testing (UAT) acceptance criteria. Ensures the solution meets user
expectations and business needs before go-live.

Transition Defines what is needed to transition from the current state to


Requirements the future state, including data migration, user training,
process changes, and system decommissioning.

@Matthew Thomas Holliday


Actions for you...

Learn how to conduct each of the


activities outlined in this post...

If you can, you’ll be equipped to step into


any Business Analyst role with clarity and
confidence.

You’ll know what to focus on.


You’ll speak the language of delivery
teams.
And you’ll be seen as the BA who
brings real value, not just
requirements.
Follow me and repost if
you found this useful.

Need Support? Send


me a DM ✉️

You might also like