Lead BA and UX
Worked across stakeholder needs, requirements, and prototype direction.
BA Case Study
iBike Ride
University-industry project focused on cyclist safety in Melbourne. The work combined business analysis, research, backlog planning, and prototype direction across a 12-week delivery cycle.
Business Analysis
UX Design
Agile Delivery
Requirements
Context
Project context
iBike Ride explored how a mobile product could support cyclist safety during commuting through clearer alerts, route awareness, and rider guidance.
Problem
Problem to solve
Cyclist safety is broad. The BA task was to narrow it into features that could be defined, prioritised, and tested within a realistic project scope.
What I Did
Analysis and delivery work
- Ran stakeholder interviews and surveys to capture user and business needs.
- Defined functional and non-functional requirements around safety alerts and rider experience.
- Used MoSCoW prioritisation and INVEST-style stories to convert scope into backlog-ready work.
- Created journey and persona artefacts to connect feature decisions to rider behaviour.
- Supported UAT and privacy-related considerations for a more delivery-ready outcome.
Artefacts
Key artefacts
Prototype overview
Main UI direction used to communicate the proposed experience.
Design process and logic
How user needs, safety logic, and solution direction were connected.
Persona artefact
User understanding used to keep the feature set aligned with commuting concerns.
Backlog and delivery board
Planning artefact showing how requirements moved into delivery work.
Market-facing presentation
Presentation used to explain the concept to external reviewers.
Outcome
What this case study shows
iBike Ride shows how I move from a broad problem to prioritised scope, backlog-ready stories, and prototype direction.