Optional deep-dive · Read before you apply

The full roadmap — A0 to A6.

This is the complete picture of what the program looks like from the inside. Read it before you apply so there are no surprises. Everything here is honest — the time commitment, the tools, what you'll produce, and what "ready" actually looks like.

1. Overview — who this is for and how it works

GAP2IT is a structured, human-centred 6–8 week pathway into Business Analysis or Systems Testing. Built for migrants, career changers, fresh graduates, people returning to work, and anyone anxious about AI who wants clarity, practice, and confidence — without learning to code.

Clarity
Understand BA/QA roles and how hiring works
Practice
Weekly labs and realistic simulations
Evidence
Artefacts you can show employers
Support
Feedback within 48 business hours

2. Business Analysis vs Systems Testing — a clearer picture

Business Analysis
  • Turn messy ideas into user stories and acceptance criteria
  • Sketch simple flows and wireframes; model states and rules
  • Capture non-functional requirements — performance, accessibility, security
  • Maintain traceability: requirement → AC → UAT → evidence
  • Align stakeholders, reduce ambiguity, make change safe
Golden rule: if a developer or tester can misread your acceptance criteria, make it clearer.
Systems Testing — QA
  • Design test ideas and charters from AC and process flows
  • Test UI, API, and data; report defects with evidence
  • Re-test fixes and support User Acceptance Testing
  • Check non-functional risks: accessibility, usability, performance
  • Provide clear, reproducible findings employers trust
Golden rule: good QA finds inconsistencies — not just crashes.

3. Tools you'll use

No complex installs to start. Everything runs in the browser.

Azure DevOps (ADO)

Stories, tasks, test cases, sprint tracking. The most common project tool in Australian IT teams.

draw.io

Quick process flows and wireframes. Free, browser-based, no account required.

Postman QA

Simple API checks — used in the QA track from Week 3 onwards.

Google Docs / Forms

Submissions, reflections, and collaborative documents throughout the program.

SQL basics Week 5

A few joins and queries for UAT and data validation. No prior SQL knowledge required.

Accessibility devtools

Browser-based tools for checking labels, focus order, and colour contrast against WCAG standards.

4. Your A-series at a glance — 6 weeks

Week
A0
Orientation and baseline

Tool links, a quick primer quiz, and expectation setting. Unlocks A1 after a pass of 70% or above. You'll understand the full roadmap before Week 1 begins.

Week
A1
Market-back targeting

Analyse 5–7 real job ads, produce a Job-Ad Analysis and a Gap Analysis, build a personal learning plan of 4–6 bullets. Your job search starts here, not at the end.

Week
A2
Core labs — BA and QA tracks diverge here
BA track

User stories and acceptance criteria, a simple wireframe, one accessibility acceptance criterion.

QA track

Test ideas from AC, two defects using the GAP2IT defect template, evidence documentation.

Week
A3
SDLC and traceability

Connect requirement → acceptance criteria → UAT or test → evidence. Safe exposure to the development cycle and how boards work in practice.

Week
A4
Observe → shadow → lead

This is intentionally low-risk — you're gently stepping into realistic tasks with scaffolding.

BA track

Co-draft stakeholder questions, lead a small requirements slice with feedback.

QA track

Lead a focused test pass — plan, execute, report.

Week
A5
Data and UAT

UAT scenarios, evidence capture, change logs, and basic SQL readiness checks — a few joins and queries to support data validation work.

Week
A6
Documentation pack — portfolio complete
BA track

Functional specification, NFR excerpts, SRS summary, full traceability matrix.

QA track

Test report, accessibility findings, defect summary, execution evidence.

Portfolio and interview preparation run in parallel from Weeks 4–6.

5. What your portfolio will contain

BA portfolio
  • 3 user stories with clear acceptance criteria (including one accessibility AC)
  • Simple wireframe exported from draw.io
  • Traceability snippet: requirement → AC → UAT
  • Mini functional spec / NFR / SRS excerpt from A6
QA portfolio
  • 2–3 defect tickets using the GAP2IT template with evidence
  • Execution notes — screenshot or short documentation
  • Accessibility smoke test findings
  • Concise test report from A6

Tangible evidence employers can review in minutes — not a certificate that says you attended, but work that shows you can do it.

6. Time and commitment — honest numbers

Minimum viable

4–7 hours per week

Ideal pace

8–12 hours per week

Live sessions

Two × 90 minutes per week. Optional but valuable. Replays within 72 hours — mini-task required for attendance credit.

Feedback turnaround

Within 48 business hours. Re-submissions welcome — we want you to get it right, not just done.

Most committed learners feel interview-ready in 6–10 weeks of consistent work. Timelines vary by prior experience and availability — that's honest, not a disclaimer.

7. AI and confidence

AI accelerates tasks — it does not replace human judgement. BA and QA roles rely on clarity, communication, reasoning, and context. These are exactly the skills you'll practice here.

We also teach you to use AI as a tool — for drafting ideas, generating options, checking structure — then refine those outputs into your own specific, testable artefacts. The judgment is always yours. That's what makes it yours.

Rule of thumb: if your artefact could fit any project, make it more specific to this one. Specificity is what separates evidence from exercise.

8. Self-assessment — is A0 right for you now?

If most of these fit your situation, A0 will feel like home:

  • I can commit at least 4–7 hours per week for 6–8 weeks
  • I prefer clarity and structure over hype and vague promises
  • I'm willing to ask "basic" questions early — before they become problems
  • I want to build artefacts I can show employers, not just study material
  • I'm comfortable learning simple browser-based tools with guidance
  • I want a human-centred, non-coding path into tech

You don't need all six. Four or five is enough. If you're unsure, reach out and we'll have an honest conversation.

9. Ready to apply?

The application takes 5 minutes. We review within 24–48 hours and send a friendly onboarding email with your A0 links. No essay questions. No pressure.