Career studio / Project Planning
Build evidence for the Junior Business Analyst role
A training center handles course-change requests through scattered emails. Administrators report rework but disagree about the cause. Define the problem and trace requirements to evidence.
Your outcome: Process discovery and requirements pack for a course-change workflow.
Start with the right expectations
Who this is for
Comfort with writing clear notes and asking follow-up questions.
This path develops a demonstrable work sample for the named role. It does not replace employer-specific experience, professional qualifications or supervised practice.
Plan your study time
Use a flexible six-week project schedule: one week for each of the first four stages and two weeks for the portfolio and review. Allow roughly 3–5 hours per week for the case work, in addition to course study. This is a planning suggestion, not a measured course duration or a promise of job readiness.
Read the course access notes before starting. Free viewing or reading does not automatically include certificates, graded assessments, software licences or paid cloud resources. Core case work can be documented with a free editor and spreadsheet; optional implementation tools may have additional requirements.
Your course sequence
Start in the order below. Use the course outline to select the sections relevant to the stage tasks, and complete foundation exercises before moving on. Full provider courses can be substantially longer than this project schedule. These are course resources, not a claimed count of individual lessons.
Resource 01 / Simplilearn
Free Simplilearn Course: Business Analysis and CBAP Concepts
Purpose: Build the foundations. Connect your notes to the case tasks below rather than only collecting completion marks.
- Explore business-analysis concepts, planning the analysis approach and selected BABOK/CBAP-related explanations.
- Follow the selected explanations of Analysis Planning, Requirements and Stakeholders.
- Connect concepts to lessons such as An Introduction to CBAP — CBAP Based on BABOK Guide — CBAP Training Online.
Access: Free Video
Certificate: Free video viewing; Simplilearn certificate not included
Resource 02 / Google
Free Project Management Course by Google
Purpose: Develop the role-specific method. Connect your notes to the case tasks below rather than only collecting completion marks.
Access: Free Video
Certificate: Free video viewing; a Google certificate is not included
Resource 03 / Google
Free UX Design Course: Research to Prototypes by Google
Purpose: Strengthen practical application. Connect your notes to the case tasks below rather than only collecting completion marks.
Access: Free Video
Certificate: Free video viewing; a Google certificate is not included
Learn, make, check
Keep a decision log as you work. For each stage, capture the assumption, your work product, a check and the change you made after that check. The acceptance criterion is the stopping condition for the stage.
Stage 1 / suggested project week 1
Elicit before prescribing
Understand: Ask about current decisions, exceptions and evidence.
Make: Draft six open interview questions for a learner and an administrator. Mark assumptions awaiting validation.
Check before moving on: Questions do not presuppose that a new app is the solution.
Study companion: Free Simplilearn Course: Business Analysis and CBAP Concepts. Use its relevant lessons and examples; the independent WikiFree task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 2 / suggested project week 2
Model the current process
Understand: A process map exposes handoffs and rework.
Make: Map request, eligibility check, approval and notification. Add the rejected and missing-information branches.
Check before moving on: Every branch has a trigger and accountable role.
Study companion: Free Project Management Course by Google. Use its relevant lessons and examples; the independent WikiFree task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 3 / suggested project week 3
Specify testable needs
Understand: Requirements state a needed behavior or constraint.
Make: Write eight requirements with IDs, sources, priority and acceptance examples.
Check before moving on: Replace words such as fast or easy with observable criteria.
Study companion: Free UX Design Course: Research to Prototypes by Google. Use its relevant lessons and examples; the independent WikiFree task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 4 / suggested project week 4
Validate the proposal
Understand: Traceability connects a problem to its test.
Make: Create a requirement-to-test matrix and compare a process-only change with a software change.
Check before moving on: Every high-priority requirement has a source and a verification method.
Study companion: Free UX Design Course: Research to Prototypes by Google. Use its relevant lessons and examples; the independent WikiFree task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 5 / suggested project weeks 5–6
Present your portfolio
Assemble the four work products into Process discovery and requirements pack for a course-change workflow. Write a README explaining the problem, your assumptions, the decisions you made, tests actually performed and what remains incomplete.
Give a five-minute walkthrough: one minute for the problem, two for the work and evidence, one for trade-offs and one for the next improvement. If you have not implemented a proposed system, label it a design or prototype rather than a deployed solution.
Acceptance: a reviewer can locate each work product, reproduce the key reasoning and identify the limits without a private explanation from you.
The portfolio brief
A training center handles course-change requests through scattered emails. Administrators report rework but disagree about the cause. Define the problem and trace requirements to evidence.
Deliver: Process discovery and requirements pack for a course-change workflow.
| request id | issue | missing information | rework rounds |
|---|---|---|---|
| R 1 | Change date | Course code | 2 |
| R 2 | Change location | None | 0 |
| R 3 | Change learner | Approval owner | 3 |
| R 4 | Change date | Preferred date | 1 |
Use these small inputs to make the reasoning visible. They are not a representative dataset, a real client engagement or evidence of production performance. Where the brief requires additional sample records, create them yourself, label them synthetic and explain why you added them.
The ZIP includes the case CSV, four stage worksheets, course sequence, decision log, test log, portfolio README template, review rubric and reference reasoning. It is a starter kit for your work, not a completed application, professional report or proprietary project file.
Check your reasoning
The request says approvals must be fast. Rewrite it without inventing an agreed service target.
Write your answer and assumptions before opening the reference.
Read the reference reasoning
Record the current statement as ambiguous, ask stakeholders for the required threshold and measurement window, then document the agreed target. A proposed one-day target must be labelled a proposal until validated.
Portfolio review rubric
| Criterion | Points | Evidence required |
|---|---|---|
| Problem and scope | 4 | A clear user, need, boundary and assumptions |
| Role-specific work | 8 | 2 points for each of the four stage acceptance checks |
| Reasoning and validation | 4 | Independent checks, actual results and uncertainty |
| Communication and reproducibility | 4 | A usable README, source links and reviewable work products |
Aim for at least 16/20 as a self-review target, with no missing stage acceptance check. This is a WikiFree practice rubric, not an industry credential or a hiring assessment.
Interview practice
How did you resolve conflicting stakeholder requirements?
Answer using the case: context, your action, evidence and limitation. Describe this honestly as a self-directed project. Do not present fictional organizations, invented interviews or practice results as paid work experience.
Your progress
Use this checklist as a personal study aid. Progress is stored in this browser when local storage is available; it is not an account record or a certificate.
0 of 5 milestones complete
The lessons and projects remain readable without JavaScript. Automatic progress saving requires JavaScript.
Questions before you start
Will this path qualify me for a job?
It helps you study relevant foundations and produce a work sample. Employers may require additional skills, qualifications and experience. Review actual role requirements before applying; no job or certification is guaranteed.
Are all tools and certificates free?
The linked learning routes were selected for free viewing or reading. Follow the separate access and certificate notes on each course. Paid tools and cloud deployment are optional; document a local design when implementation resources are unavailable.
Can I follow this on a phone?
You can read the path and many learning resources on a phone. Coding, detailed spreadsheet work, design tools and mobile-app development are easier or require a suitable computer. The page is designed to reflow; that is not a claim that every physical device has been tested.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.