SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

FREE SELF-GUIDED BUSINESS ANALYST TRAINING

Business Analyst Project Training: A Worked Practice Example

Business analysis project training means learning the analyst's job by working through a project, from a stakeholder's first claim to a tested requirement, instead of only studying definitions. This free worked example is a short version you can finish today; the sections after it explain how a full simulated project works, stage by stage, and what you produce.

Business analyst (BA) project training becomes useful when you can connect a problem to evidence, a requirement and a test. This short exercise lets you practise that connection with a fictional room-booking service.

Try your own response first. This self-guided exercise includes no live coaching, human assessment, certification or employment promise.

1. Define the decision before proposing a feature

Harbor Desk is a fictional shared workspace. A staff member says: “The room summary makes us look busier than we are.”

That statement is a stakeholder claim. It suggests something to investigate; it does not prove lost revenue, poor customer experience or a software defect.

Your task is to decide what a confirmed-booking summary should count. A complete booking system also needs durations, capacity, permissions and conflict handling.

2. Read the evidence and its limits

These six invented records describe one fictional date. Each row represents a booking, not a person or status-change event.

Fictional booking records
BookingRoomStart timeStatus
B01Pine09:00CONFIRMED
B02Pine09:00CANCELLED
B03Pine10:00PENDING
B04Cedar09:00CONFIRMED
B05Cedar10:00CANCELLED
B06Cedar11:00CONFIRMED

The draft summary counts all six rows. The operations owner proposes counting only confirmed records in a summary labeled “Confirmed bookings.” Whether pending requests should reserve capacity remains undecided.

Before writing a requirement, ask:

Counting event records as bookings could inflate totals even after filtering status.

3. Turn the decision into a testable requirement

A vague draft says: “Make the occupancy report accurate.” It does not define occupancy, the date, the records to include or the expected result.

A more precise requirement is:

R1: For the selected date, show the number of booking records with status CONFIRMED for each room.

Label the metric “Confirmed bookings.” This count does not establish utilization or whether a room is available at a particular time.

Acceptance criterion AC1: Given Pine has one confirmed, one canceled and one pending booking on the selected date, when staff view Pine's confirmed-booking summary, then the count is one. Canceled and pending records do not contribute to that metric.

Excluding pending records from this metric does not settle whether they reserve capacity.

4. Sketch the process and locate the change

Use this simple sequence:

  1. A request creates a pending booking.
  2. A decision changes its status to confirmed or canceled.
  3. Staff open the summary for a selected date.
  4. The summary counts the records that meet its stated rule.

The proposed change belongs in step four; request and cancellation handling remain separate.

Ask what should happen when two confirmed records share a room and start time. Counting cannot resolve that conflict.

  1. A request creates a pending booking
  2. A decision confirms or cancels it
  3. Staff open the summary for a date
  4. The summary counts records that meet its ruleThis is where R1 applies.
Locate the change. Only step four changes; request and cancellation handling stay as they are.

5. Check one question with SQL

Assume a table called bookings contains exactly the six rows above, with columns booking_id, room, slot and status.

SELECT room, COUNT(*) AS confirmed_bookings
FROM bookings
WHERE status = 'CONFIRMED'
GROUP BY room
ORDER BY room;

The expected result is:

Expected SQL result
RoomConfirmed bookings
Cedar2
Pine1

This query was checked against the six-row example in an in-memory SQLite database. It returned these counts. That validates this small calculation, not a deployed booking service or its business policy.

Explain the limits alongside the result:

6. Connect the requirement to user acceptance testing

User acceptance testing (UAT) should check the intended behavior using explicit cases.

UAT checks
TestExpected resultEvidence available here
T1: Use the six-row sampleCedar = 2; Pine = 1SQL calculation checked
T2: Change B03 from pending to confirmedPine becomes 2Proposed test; not executed here
T3: Add a room with canceled bookings onlyShow zero if every room must be listedRequires a room inventory and a different query

T3 reveals a decision hidden inside “for each room.” If the requirement means every room, including empty ones, the simple query is incomplete. Clarify the requirement and use a room inventory with a suitable join before claiming completion.

Keep the connection visible: sample observation → R1 → AC1 → T1. Checking SQL does not prove that a user interface displays the result correctly or that staff understand it.

  1. Sample observationSix records; three are confirmed.
  2. R1Count CONFIRMED records per room.
  3. AC1Pine: one confirmed, one canceled, one pending gives one.
  4. T1The six-row sample gives Cedar 2, Pine 1.
Keep the connection visible. Each step points back to the one before, so the reasoning can be checked.

7. Explain the work honestly

A portfolio summary could say:

I investigated a fictional six-booking sample, clarified a counting rule, wrote an acceptance criterion and checked a SQL result. The sample contained three confirmed bookings. Pending-booking policy and zero-count room display still need decisions. No customer impact was measured.

Now try a variation: the owner wants every room shown, including rooms with zero confirmed bookings. Revise the requirement, identify the extra data needed and write a test before changing the query.

How our project training works, stage by stage

The exercise above is one slice of a project. In the BA Lab you join a fictional company and work through 13 stages in order, the way a project really unfolds. Each stage has short concept cards (what it is, why it matters, an example), a brief from your manager, a practice tool and checks that say what is good, what is risky and how to fix it.

  1. Stage 0: Join the project. What a BA does in a company, your team, your first week.
  2. Stage 1: Business case & problem. Problem statement, objectives, scope, success measures.
  3. Stage 2: Stakeholder analysis. Stakeholder map, power/interest, RACI, communication plan.
  4. Stage 3: Elicitation. Interviews, workshops, good questions, meeting notes.
  5. Stage 4: Requirements. BRD, functional/non-functional, user stories, acceptance criteria.
  6. Stage 5: Process modelling. AS-IS / TO-BE flows, BPMN basics, pain points.
  7. Stage 6: Data & SQL. Tables, joins, aggregates, data validation with SQL.
  8. Stage 7: APIs & integration. REST, endpoints, JSON, status codes, API requirements.
  9. Stage 8: Agile delivery (Jira-style). Epics, stories, bugs, backlog, sprint planning.
  10. Stage 9: Documentation (Confluence-style). Requirement pages, meeting notes, decision log.
  11. Stage 10: Dashboards & Power BI practice. KPIs, data model, DAX measures, slicers, drill-down, storytelling.
  12. Stage 11: UAT & traceability. Test cases, RTM, defect triage, sign-off.
  13. Stage 12: Go-live & portfolio. Release readiness, change management, benefits, portfolio.

You choose one of 7 industries for the project: Banking, E-commerce, Insurance, Finance operations, Healthcare, Logistics, SaaS. The free trial opens the first 4 stages for 7 days. The training is self-guided: there are no live classes, no individual coaching and no human marking, and the Jira-style, Confluence-style and dashboard tools are simulations.

Silent clip, about 14 seconds A longer simulated project: joining a fictional company in the BA Lab, with every stage from business case to go-live listed on the left. Recorded with a synthetic test account.

What you produce: portfolio artefacts

Each stage ends with something you could show and explain in an interview. Keep them together as a portfolio, and label every piece as practice on a fictional company: it is evidence of how you think, not of employment or client delivery.

Portfolio artefacts you produce in each stage of the simulated project
StageWhat you produce
0. Join the projectA one-page summary of the company, the team and your role
1. Business case & problemA problem statement, objectives, scope and success measures
2. Stakeholder analysisA stakeholder map, a RACI table and a communication plan
3. ElicitationInterview questions and notes sorted into facts, assumptions and open questions
4. RequirementsRequirements and user stories with acceptance criteria
5. Process modellingAS-IS and TO-BE process flows with pain points marked
6. Data & SQLSQL queries that answer business questions, with the checks you ran
7. APIs & integrationAn API requirement with request, response and error cases
8. Agile delivery (Jira-style)Epics, stories and bugs on a Jira-style board, and a sprint plan
9. Documentation (Confluence-style)A Confluence-style requirement page, meeting notes and a decision log
10. Dashboards & Power BI practiceKPI definitions and a dashboard explained in plain words
11. UAT & traceabilityUAT test cases, a traceability matrix and a sign-off recommendation
12. Go-live & portfolioA release-readiness check, a benefits note and your portfolio summary

A short written summary like the one in section 7 above turns these files into a story an interviewer can follow: the problem, what you checked, what you decided and what is still uncertain. Our guide to a portfolio without experience shows how to present it.

Who project training suits

  • Freshers who know the theory but have never worked through a whole project and want interview stories.
  • Career switchers from support, testing or operations who want to practise the documents and decisions analysts own.
  • Working professionals who want to rehearse unfamiliar stages, such as SQL checks, API requirements or UAT sign-off, on a safe example.

If you first want an overview of what to learn, read our guide to business analysis training. If you are weighing an exam, the business analysis certification guide explains how training and certification differ; BA Mentorship issues no certification.

Business analysis project training: frequently asked questions

Is this a real-time project with a real client?

No. The project and company are fictional, which lets you practise every stage safely. Describe it as practice in your CV and interviews, not as client work or employment.

What is the difference between this example and the BA Lab?

This page is one free, short exercise. The BA Lab is a full simulated project with stages from the business case to go-live, a choice of industries and checks on every task.

Do I need SQL before starting?

No. The first stages cover the business case, stakeholders, elicitation and requirements. SQL comes later in the project, with concept cards that start from the basics.

Does project training count as work experience or towards a certification?

No. Practice projects build skills and portfolio evidence, but they are not employment and do not count as IIBA or PMI experience hours. See the certification guide.

For further practice, try the free demo, compare the packages or check software requirements. The demo contains one fictional banking mission and three observations. Experience Lab introduces connected banking missions and SQL practice; Core and Advanced add broader scope. See packages and prices on the pricing page.

Original fictional exercise created for BA Mentorship. It contains no customer records or paid curriculum extracts.

Continue with requirements, SQL and interview practice resources.

Glossary terms in this guide

Browse the full glossary

CHECK BEFORE CONTINUING

Keep your work safe