How to Become a Business Analyst
Bridge the gap between business problems and technical solutions.
United States
$55,000 – $75,000/year
United Kingdom
£28,000 – £42,000/year
Canada
CA$52,000 – CA$72,000/year
Australia
A$65,000 – A$90,000/year
South Africa
R200,000 – R340,000/year
Broad annual benchmarks. Actual pay varies by city, company size, industry, remote status, and experience.
Overview
Business analysts are the translators of the corporate world. They sit between the people who have a business problem and the people who build the technical solution. A BA's job is to understand what a business needs, document it precisely, model the current and future state of processes, and communicate requirements in a way that development teams can act on.
The role is highly accessible to people with a mix of business and technical interest. You do not need to write code, but you do need to understand how systems work and how businesses operate. Graduates with backgrounds in accounting, finance, management, or IT are all natural candidates for business analysis. This roadmap was curated by Ndulamiso Mamburu, who brings direct corporate experience in navigating the intersection of business operations and technology.
Roles You Can Get
Skills You Will Build
Technical Skills
- Requirements gathering & documentation
- Process modelling (as-is / to-be)
- Agile & Scrum methodology
- Project management fundamentals
- Management information systems
- AI and automation awareness
Soft Skills
- Active listening and stakeholder interviewing
- Structured written communication
- Facilitation and workshop management
- Analytical thinking and problem decomposition
The Roadmap
Understand How Organisations Use Information
3–4 weeksBusiness analysts work within organisations, and those organisations are powered by information systems. Before you can analyse business requirements, you need to understand how information flows through a company: how systems capture data, how decisions are made, and how technology either enables or constrains business strategy. This foundational stage gives you the conceptual framework that underpins every BA deliverable.
Stage milestone: You can describe how management information systems support organisational strategy, and map how data flows through a typical business process.
Master Project and Process Management
8–10 weeksBusiness analysts almost always work within project teams. Understanding how projects are initiated, planned, and delivered is not optional; it is the context in which all your BA work happens. This stage covers the full project lifecycle using both traditional and Agile frameworks, giving you the vocabulary and tools to function effectively on any type of project team.
Stage milestone: You can create a project scope document, write User Stories, manage a Product Backlog, and describe the difference between Waterfall and Agile delivery approaches.
Learn Process Improvement Methodologies
5–6 weeksA major part of a BA's work is identifying inefficiencies in current business processes and designing improvements. Lean Six Sigma provides the structured methodology for doing this: how to define a problem, measure its impact, analyse root causes, design a solution, and control the improvement. These frameworks are used globally in manufacturing, financial services, healthcare, and government.
Stage milestone: You can apply the DMAIC framework to a real or fictional business process, identify waste and variation, and propose a measurable improvement.
Add Compliance and AI Awareness
3–4 weeksModern business analysts increasingly need to understand the regulatory environment their organisation operates in, and the impact of AI on business processes. GDPR and data protection frameworks affect how requirements are documented and how systems handle personal data. AI tools are reshaping how analysis, documentation, and reporting are done. This stage ensures you are current on both.
Stage milestone: You can identify GDPR-relevant requirements in a business case and describe three ways AI tools can augment business analysis work.
Certifications Worth Getting
IIBA Entry Certificate in Business Analysis (ECBA)
IIBA (International Institute of Business Analysis)
The globally recognised entry-level BA certification. No work experience required. Widely valued in corporate environments worldwide.
PMI Professional in Business Analysis (PMI-PBA)
Project Management Institute
Strong credential for BAs who work within project teams. Valued by project-driven organisations and consulting firms.
Alison Diploma in Project Management
Alison
Free CPD-accredited diploma. Provides a visible credential for your CV while you prepare for ECBA or PMI-PBA.
Portfolio Project Ideas
Employers want proof, not promises. Build at least two of these before applying for jobs, and document each one publicly on GitHub or a personal portfolio.
- 1
Requirements document: produce a Business Requirements Document (BRD) for a fictional system change at a small company
- 2
Process model: create an as-is and to-be process diagram for a fictional inefficient business process, with a gap analysis
- 3
User stories: write a Product Backlog of 20 User Stories with acceptance criteria for a fictional mobile app
- 4
DMAIC project: complete a full Lean Six Sigma DMAIC mini-project on a real inefficiency you have observed in any workplace or study environment
- 5
Stakeholder map: for any fictional project, create a complete stakeholder register identifying all parties, their interests, influence level, and engagement strategy
Practice with Real Tasks
Stop reading, start building. Each task below is a structured exercise with a brief, deliverables, and a rubric. Submit your work to earn a public Badge of Competence on your profile.
Define KPIs for a Startup
Identify the 5 most important metrics for a food delivery startup.
Start Task →Turn a Table into a Story
Transform a raw data table into a 3-paragraph executive summary.
Start Task →Design a Dashboard Wireframe
Sketch a dashboard layout for a retail store manager with clear information hierarchy.
Start Task →Project Plan with Charter and Gantt
Produce a complete project plan for a real or fictional initiative, the way a junior coordinator does on day one.
Start Task →The One-Chart Dashboard
Design the single chart you would put on a CEO's weekly email.
Start Task →Dynamic Pricing Model
Build a what-if model with data validation dropdowns and conditional formatting.
Start Task →Your First 90 Days on the Job
What real day-to-day work looks like once you land the role. Use this to set expectations and to know what skills to keep sharpening after you are hired.
- 1
Week one focuses on stakeholder mapping: meeting business sponsors, product owners, technical leads, and end users to understand who you serve and how decisions are made
- 2
By week three you should be sitting in on backlog refinement, sprint planning, and retrospectives, observing how requirements flow into delivery
- 3
Month two: take ownership of small user stories, write acceptance criteria independently, and lead at least one stakeholder workshop with a senior BA shadowing
- 4
By month three expect to own a feature or epic end-to-end: discovery, requirements documentation, story writing, supporting the development team during the sprint, and supporting UAT
- 5
Build a personal stakeholder log from day one. Track who said what, what decisions were made, and what is still open. BAs who keep meticulous traceability are the ones senior leaders trust with bigger work
Common Mistakes to Avoid
The pitfalls that keep candidates stuck at the application stage. Each one comes from real hiring feedback across entry-level hiring contexts.
Producing thick BRDs no one reads
Fix: Modern BA work is iterative. Lead with user stories, decision logs, and process diagrams. Reserve full BRDs for regulated or contractually required deliverables.
Documenting requirements without involving developers early
Fix: Requirements written in isolation almost always miss technical constraints. Bring at least one developer into discovery sessions; the rework you save is worth the meeting time.
Treating "agile" as ceremony attendance
Fix: Agile BA work is about continuous prioritisation, slicing stories small, and being responsive to change. If you are merely attending standups and writing the same scope documents you would write in waterfall, you are not yet doing agile BA.
Avoiding data analysis because "that is the data analyst's job"
Fix: BAs who can validate their own assumptions in SQL or Excel are dramatically more credible. Spend a few weekends becoming comfortable with basic queries; it pays back permanently.
Modelling the as-is process and stopping there
Fix: Documenting the current state is the easy half. The valuable half is modelling the to-be state with measurable improvements. Always pair as-is and to-be diagrams in your portfolio.
Frequently Asked Questions
What is the difference between a business analyst and a data analyst?
Do I need to be technical to be a BA?
Is the IIBA ECBA worth getting?
Agile BA or traditional BA?
Can I move from BA into product management?
How important is SQL for a BA?
Accelerate Your Career
Join over 10,000+ learners. Get early access to new courses, exclusive career guides, and platform updates delivered straight to your inbox.
By subscribing, you agree to our Terms of Service and Privacy Policy. Unsubscribe anytime.
Ready to start applying?
The Junior Business Analyst interview prep guide covers practical CV tips and interview questions employers use to screen candidates for this role.
Related Career Paths
Build your CV while you learn
Our free CV builder lets you document your progress as you complete each stage of this roadmap. 3 templates, instant PDF download.