- What is business analysis?
- Business analysis is how a working analyst keeps a room on the decision. You already know the title. This course is about holding the line: the need, the requirement, and the moment you stop a conversation that is no longer about either.
- Why does business analysis matter?
- A good room can still wander until the decision is gone. Practitioner work is how you bring it back, write what was agreed, and stop the build from guessing. That is the difference between activity and analysis.
- What skills does a business analyst need?
- At this level you already facilitate. What you add here is the nerve to name what is out of scope, and the writing that lets a team start without phoning you. Judgment first. The tool second.
- How is a business analyst different from a project manager?
- You own the need. They own the date and the budget. When those collide, you say what the requirement will lose if the date stays. You do not quietly shrink the need to protect the plan.
- What does a business analyst hand over?
- A pack you can defend in the room: the need, the behaviour, the stories, the trace to the test, the process, and the stakeholder note. Practitioner standard means a stranger can build from it.
- Which ways of working does this course cover?
- Sequential and agile. You will practise the analyst move in each: what you freeze, what you leave open, and how you stop a backlog from becoming a second, unordered requirements document.
- What is requirements elicitation?
- It is a conversation with a purpose. You prepare the question, you confirm what you heard, and you write the decision before you leave the room. A workshop that produces no decision was a meeting.
- What does a business analyst do in testing?
- You write acceptance so a tester does not have to invent it. You attend the business check. If the result does not match the requirement, you say so, even when the date is close.
- How does a business analyst work with stakeholders?
- You know who can approve a change, and you do not accept a requirement from someone who cannot. Conflict is part of the job. This course is where you practise staying with it.
- What is the difference between a functional and a non-functional requirement?
- What it does, and how well it must do it. A practitioner writes the second with the same care as the first. "Fast" is not a requirement. A number, and the condition, is.
- Which tools will I use?
- Whatever your employer already has: a backlog, a wiki, a model, a sheet. This course will not sell you a tool. It will show you the analysis those tools are failing to hold.
- How does this work change a project?
- Decisions survive the meeting. Scope stops drifting in side conversations. The sponsor hears a change as a change. Dates and the fee are on this page.
- Do you guarantee a job after a cohort?
- No. We publish dates, prices, refund terms and consented stories. Placement and income claims are not part of this academy.
- What time zone are live sessions in?
- Source zone is America/Toronto unless a cohort says otherwise. Session times always name that zone. Convert in your own calendar from the ICS on the cohort card.
- Can I join a waitlist if a cohort is full?
- Yes. Waitlist captures name, email and optional phone. It does not take payment. Seats that free up are offered in join order.
- How does early-bird pricing work?
- If a cohort has an early-bird price and the cut-off has not passed (server date at payment), checkout charges the early-bird amount. The cart may still show list price until quote.
- What is the refund window?
- Full refund before the published cut-off relative to the cohort start; after that the published bands on the Refund page apply. Checkout requires you to accept that policy.