What skills does a business analyst need?

Elicitation, documentation, process modelling, prioritisation, communication, Agile knowledge and data skills in Excel and basic SQL.

Do I need to code to be a business analyst?

Not usually, but basic SQL and Excel help you check facts and size problems.

How do I build a business analyst portfolio?

Create a requirements pack, a process improvement study and a data-backed problem summary using made-up or public information.

Are certifications required?

No. They can add structure and help some resumes, but projects and communication skills matter as much.

Does the roadmap promise a job?

No. It is a learning guide, and hiring depends on the market, your portfolio and interviews.

Business Analyst Roadmap PDF

Key takeaways

Start with business basics and communication, not only tools.
Core skills are elicitation, documentation, process modelling and prioritisation.
Excel and basic SQL help you check facts and size problems.
Learn Agile practices because many teams work in sprints.
Show your skills with a sample requirements pack and a process model.

What is business analyst roadmap?

A business analyst roadmap is a staged plan for learning the skills, documents and tools needed to work as a business analyst, who connects business needs with technology solutions.

What does the path look like?

Business analysis sits between business teams and technical teams. The roadmap below builds the skills in an order that makes each stage easier. Pace depends on your time and background; many learners need a few months of steady practice to reach entry level readiness.

What are the stages?

Stage 1: business basics. How a company earns and spends money, departments, customers, products, processes and metrics. Read about an industry you like. Practice: describe how one company makes money in half a page.

Stage 2: communication and thinking. Asking questions, listening, writing clearly, structured problem solving and basic presentation skills. Practice: summarise a news article in five bullet points and one recommendation.

Stage 3: requirements and documents. Elicitation techniques, functional and non-functional requirements, BRD, SRS, user stories and acceptance criteria. Practice: write ten user stories with acceptance criteria for a booking app.

Stage 4: process modelling. Flowcharts, BPMN-style diagrams, as-is and to-be, swimlanes, use cases and wireframes. Practice: map a returns process and propose two improvements.

Stage 5: analysis techniques. SWOT, root cause analysis (five whys), gap analysis, MoSCoW prioritisation, stakeholder analysis and cost-benefit thinking. Practice: analyse a problem with a cause chart and a prioritised list of fixes.

Stage 6: data skills. Excel (formulas, PivotTables, charts), basic SQL (SELECT, filters, joins, grouping), reading dashboards and defining KPIs. Practice: answer five business questions from a sample dataset and present one chart.

Stage 7: Agile and delivery. Scrum roles and events, backlog refinement, sprint planning, working with testers, user acceptance testing and change management. Practice: run a mock refinement of five stories with a friend.

Stage 8: tools. A backlog or ticket tool, diagramming tools, a wiki or document tool, and a spreadsheet. Learn the idea of each tool class instead of one product only.

Stage 9: domain knowledge. Pick a domain such as banking, retail, healthcare or e-commerce and learn its terms, rules and common systems. Practice: build a glossary of 30 domain terms.

Stage 10: projects and interviews. Create a sample pack and prepare stories and answers.

What projects should I build?

Project	Output
Requirements pack for a small app	Business case, stakeholders, user stories, acceptance criteria
Process improvement study	As-is and to-be diagrams, gap analysis, recommendations
Data-backed problem sizing	Excel analysis, chart, one-page summary
UAT plan	Test scenarios from acceptance criteria

Use made-up or public information, and never real confidential material.

Which certifications exist?

Professional bodies such as the IIBA offer business analysis certifications, and Scrum organisations offer Agile ones. They can add structure and help some resumes, but they have eligibility rules, fees and exam outlines that change, so check the official sites. Projects and communication skills matter as much.

How do I prepare for interviews?

Study the concept notes, practise explaining a requirement in plain language, prepare two stories about handling conflict or change and practise a case such as "improve the onboarding process". Be ready to discuss basic SQL and Excel.

What mistakes should I avoid?

Learning only tools, writing vague requirements, skipping stakeholders, ignoring data and domain knowledge and expecting to move into a senior role without practice. Start with small, real tasks.

What does a sample weekly plan look like?

Spend two evenings on concepts (requirements, modelling or Agile), two evenings on practice tasks (writing stories, drawing a process, analysing data in Excel), one session on reading about a domain and one session on reviewing and writing a short summary of what you learned. Keep a folder of your documents so that you can reuse them in a portfolio.

How do I practise elicitation without a job?

Interview a friend or family member who runs a small business about one process, such as taking orders. Ask open questions, take notes, draw the process, list pain points and write requirements. Then ask them to read your summary and correct it. This exercise builds real listening and documentation skills quickly.

How do I show business thinking?

For any feature idea, write the problem, who benefits, how you would measure success and what could go wrong. Practise a two-minute explanation of the idea without technical words. Interviewers look for this clear link between a need, a solution and a result.

Which questions should I ask about any requirement?

Who needs it and why, what problem does it solve, how will we know it works, what happens if we do nothing, what are the dependencies and risks, and who approves it? Asking these six questions turns a vague request into a clear requirement.

Download Business Analyst Roadmap PDF