Skip to content
Updated: 6 min read

A Career in Business Analysis: Junior to Expert

What a business analysis career looks like from the first junior role to expert level: the occupation as described in the European ESCO classification, the skills each stage adds, modelling standards such as BPMN and UML, and where the BABOK Guide and certification fit.

Adrian Kwiatkowski Author: Adrian Kwiatkowski

A career in business analysis usually begins with documenting requirements for someone else’s project and grows into deciding which changes to processes and systems an organisation should take on in the first place. Juniors learn the techniques, practitioners run the analysis from start to finish, and experts set the direction of the practice and coach other analysts.

Quick Overview

What you will learn:

  • How the European ESCO classification defines the business analyst occupation
  • Which skills and techniques mark the step up from one level to the next
  • How modelling standards, the BABOK Guide and certification relate to hands-on experience

Who this article is for:

  • People starting out in requirements work or moving into analysis from another role
  • Analysts planning their next career move
  • Managers building or growing an analysis team

Reading time: 7 minutes

The Occupation in Plain Terms

For a vendor-neutral reference point, look at ESCO, the European classification of skills, competences and occupations maintained by the European Commission (esco.ec.europa.eu). It lists “ICT business analyst” under code 2511.8, within ISCO group 2511, systems analysts. In ESCO’s description, the job involves analysing and designing an organisation’s processes and systems, assessing the business model and how it fits with technology, identifying where change is needed and what its impact will be, capturing and documenting requirements, and then making sure they are delivered while supporting the business through implementation.

Read closely, the description shows a much broader job than the stereotype of an analyst who just writes specifications. It runs all the way from understanding the problem to checking that the change, once delivered, has actually solved it.

The Skills That Carry You Upward

ESCO attaches a set of essential skills to the occupation, among them business process modelling, analysing business requirements, interacting with users to gather requirements, identifying legal requirements, applying change management and providing cost-benefit analysis reports. In everyday work, these group into a handful of practices.

Understanding stakeholders. Any analysis begins with working out who the change affects, who could block it and who will use the result, and a stakeholder map keeps all of that in view. Juniors are usually handed a list of people to interview; practitioners draw up the map themselves and run the workshops.

Shaping requirements. Business requirements state the goal, stakeholder requirements say what people need to be able to do, and solution requirements describe how the system should behave. Agile teams often capture all this as user stories with acceptance criteria, prioritised by the product owner.

Modelling processes and systems. Two open standards from the Object Management Group (www.omg.org) give analysts a common notation. BPMN 2.0.2, the current formal version, published in January 2014, deals with business processes, while UML 2.5.1, published in December 2017, adds use case and activity diagrams that come in handy when a business process turns into system behaviour. Analysts who are fluent in both find it easier to move between business stakeholders and the development team.

Making the business case. Further up the ladder, the analyst weighs costs, benefits and risks instead of simply describing features.

From Junior to Expert

The same classification (esco.ec.europa.eu) also defines a senior occupation, “ICT business analysis manager” (code 2511.7). The classification says people in this role identify where information systems must change to support business plans, monitor the impact of those changes and translate business needs into ICT solutions. Its list of essential skills adds managing ICT projects, making strategic business decisions and tracking key performance indicators.

Put together, this gives a practical three-stage picture:

  • Junior analyst. Documents requirements under supervision, takes part in workshops, draws process models and drafts user stories. The habit worth building early is to ask about the goal before asking about features.
  • Practitioner. Owns the analysis for an entire initiative: identifies stakeholders, plans elicitation, resolves conflicting requirements and checks that the solution meets the need.
  • Expert or analysis lead. Oversees the analysis practice across many initiatives, decides which changes are worth pursuing, mentors others and sets working standards for the team.

The profession’s reference standard is the BABOK Guide, published by the International Institute of Business Analysis (www.iiba.org; bear in mind that IIBA sells certifications based on this standard). According to IIBA, the guide organises business analysis tasks into 6 knowledge areas and describes the skills, deliverables and techniques analysts need. IIBA’s core certifications map onto career stages: ECBA at entry level, CCBA for people with 2–3 years of hands-on business analysis experience, and CBAP for those with more than 5 years. A certificate shows that you know the standard, but it is no substitute for the judgement that comes from real projects.

Read Also

Build Your Skills

If you are just starting out, Basics of business analysis covers the foundations. Experienced analysts who want to organise what they know around the standard can take Business analysis, BABOK V3.0 and preparation for IIBA certification. Get in touch and we will match the scope to the career stage your team has reached.

Frequently Asked Questions (FAQ)

What does a business analyst actually do?

A business analyst works out which problem the organisation is trying to solve, elicits and documents requirements, models processes and assesses the impact of a change. ESCO adds that the role includes making sure requirements are delivered and supporting the business during implementation. The work earns its keep wherever changing a process or system comes at a real cost.

What is the BABOK Guide, and is it worth building on?

It is the business analysis standard published by IIBA, which groups an analyst’s tasks into knowledge areas and describes the techniques. Use it as a shared vocabulary and a map of skills rather than as a step-by-step manual, because the right technique always depends on the initiative.

Which skills get you beyond the junior level?

Start by running elicitation and requirements analysis on your own, modelling processes and managing stakeholders. After that, learn to resolve conflicts between requirements and build a business case. At expert level, what sets people apart is choosing which changes to pursue and developing other analysts.

Where should I start learning business analysis?

Begin with the basics of requirements and BPMN, and get onto a real project as early as you can, even in a supporting role. A course will give you the concepts, but the skill itself grows through practice. Preparing for certification makes most sense once you have experience the standard can be mapped onto.

Adrian Kwiatkowski
Adrian Kwiatkowski Opiekun szkolenia

Request a quote

Develop Your Competencies

Check out our training and workshop offerings.

Request Training
Call us +48 22 487 84 90