top of page

Full Business Analyst Workflow for Recycle4Change

šŸŽÆĀ Objective of Showcase

To demonstrate my ability to plan, elicit, document, and manage requirements through structured frameworks while ensuring alignment with Agile principles and stakeholder value.

Key Focus Areas:

  • Strategic Analysis (SWOT & PESTLE)

  • Stakeholder Prioritisation & Engagement

  • Elicitation Activities (Interview, Workshop, Focus Group, Questionnaire)

  • Functional & Non-Functional Requirements

  • Business Process Modelling (Swim Lanes)

  • Requirements Lifecycle Management (RTM)

  • Agile Delivery using Jira (Roadmap, Story Mapping, Personas, Acceptance Criteria)


This end-to-end process demonstrates my capability to fulfil the responsibilities of a Business Analyst across the full project cycle — from discovery to delivery.


šŸ”Ā Project Overview

This project showcases the complete business analysis lifecycle forĀ Recycle4Change (R4C) — a Victoria-based recycling initiative that promotes environmental sustainability and social inclusion. From strategic analysis and stakeholder engagement to functional requirements, BPMN modelling, and Agile delivery via Jira, this project reflects my end-to-end capability as a Business Analyst.


šŸŽÆProject Delivery:

Part 1: Requirements Elicitation:

šŸ“Œ 1. Strategic Analysis

StrategicĀ analysis will provide clearing perspective on R4C project and related software application development, which will be beneficial for shaping the project’s strategies and development. PESTLEĀ analysis guides assessing an organisation’s external environment by identifying political, economic, social, technological, environmental, legal factors and SWOTĀ analysis combines findings from external and internal environment assessments


1.1 PESTLE Analysis


PESTLE assessing an organisation’s external environment
PESTLE assessing an organisation’s external environment

1.2 SWOT Analysis

The SWOT and external and internal environment analysis
The SWOT and external and internal environment analysis

šŸ“Œ 2.Ā Stakeholder Engagement Plan

Understanding all stakeholders and prioritisation are essential components for efficient requirements development and management by R4C Stakeholder Lists and Power and Interest of Stakeholders will be addressed below

2.1 R4C Stakeholder Lists

NO.

Stakeholder

Type

1.

R4C CEO

Internal

Ā 

2.

R4C Employees:

Management team, Operation Team

Ā 

Internal

3.

TOMRA Cleanaway Victoria (TCV)

External

4.

Drivers

External

5.

Environment Protection Authority Victoria (EPA)

External

6.

Victorian Government

External

7.

Commercial / Residential / Individual Customers feedback

External

8.

Justice System

External

9.

A nominated charity of R4C

External

10.

Software Developer

External

11.

Payment Gateway

External

12.

Victoria Community

External

13

Media / Press

External

14.

GPS Map Application Host

External

Ā 15.

Tracking System

External

Ā 16.

Suppliers: Equipment or materials

External


2.2 Power and Interest of Stakeholders

R4C Power and Interest Grid
R4C Power and Interest Grid

šŸ“Œ 3.Ā Elicitation Activity Plan

The Elicitation Activities Process in Four Techniques

3.1 Interview:

Elicitation Activity Plan by Interview Techniques
Elicitation Activity Plan by Interview Techniques

3.2 Workshop:

Elicitation Activity Plan by Workshop Techniques
Elicitation Activity Plan by Workshop Techniques

3.3 Focus Group:

Elicitation Activity Plan by Focus Group Techniques
Elicitation Activity Plan by Focus Group Techniques

3.4 Questionnaires:

Elicitation Activity Plan by Questionnaire Techniques
Elicitation Activity Plan by Questionnaire Techniques

šŸ“Œ 4.Ā Conclusion

Recycle4Change (R4C)Ā is a Victoria-based initiative aimed at improving recycling access and community engagement through a user-friendly platform. Using interviews, workshops, and focus groups across three customer segments, the project identified key functional requirements and service gaps. Beyond sustainability, R4C supports social inclusion by creating jobs for marginalised groups, aligning with broader government objectives.

Part 2: Requirement Management:

šŸ“ŒĀ 1. Feature List

1.1 R4C Functional Requirements with MoSCoW Prioritisation

R4C Functional Requirements
R4C Functional Requirements

1.2 R4C Non-Functional Requirements

R4C Non-Functional Requirements
R4C Non-Functional Requirements

šŸ“ŒĀ 2. Business Process ModellingĀ 


šŸ“ŒĀ 3. Requirement Life Cycle Management

Requirement Traceability Matrix (RTM)


Part 3: Project Management by Agile Approach:

šŸ“ŒĀ 1. Product Vision

For individuals and businesses in Victoria

who need to access the recycling system and convert waste into money.

TheĀ R4C is a mobile application that helps Victorians access the recycling system.

That assists Victorians by providing a convenient and easy-to-use mobile phone platform.

Unlike going to access the recycling system in person, which would result in a loss of time for travel.

Our product provides a user-friendly interface and an audio version for disabled individuals.

AndĀ a convenient service for accessing the recycling system. It enables users to track the results of their recycling efforts and their environmental impact.

šŸ“ŒĀ 2. Product Roadmap

2.1 R4C Release Plan


2.2 R4C Product Roadmap with Epics


2.3 R4C Product Roadmap with Epic and User Story


šŸ“ŒĀ 3. Product Backlog and Story Mapping

3.1 R4c Product Backlog

3.2 R4C Story Mapping


šŸ“ŒĀ 4. Personas

Based on data extracted from the Victorian survey questionnaire (Spicer, 2021, p.41), the demographic exhibiting the greatest interest in recycling comprises women aged 56 and above in Victoria. In this group, 89% of survey participants believe recycling is important and a responsibility.

Recycling Perceptions Across Demographic Groups (Spicer, 2021, p.41)
Recycling Perceptions Across Demographic Groups (Spicer, 2021, p.41)

The results indicate a positive inclination towards recycling practices and a robust sense of environmental responsibility within this age group, as detailed in the first persona (Emma). The second persona (Malinda) represents the identity of 84% of survey participants, aged 36-55, who consider recycling important. These identified personas play a crucial role in the success of this project.


First Persona:

Second Persona:



šŸ“ŒĀ 5. Story Elaboration and Acceptance Criteria

In the first release, example one epic to decompose into user stories to break down the work effectively.

User story: R4C-20 Bin Collection Confirmation

In epic R4C-17: MF-03 Bin management

Split user story to R4C-30, R4C-31, R4C-21




šŸ“ŒĀ 6. Conclusion

This section provides a comprehensive overview of theĀ Recycle4Change (R4C)Ā application project, designed to ensureĀ Agile deliveryĀ and fosterĀ effective team collaboration. It highlights key elements such asĀ Agile principles,Ā roadmap planning, andĀ user-centric development.

The initial releases targetĀ residents and businesses, aiming for bothĀ financial impactĀ andĀ public engagement. Agile practices—includingĀ story mapping,Ā backlog prioritisation, andĀ planning poker—were applied to promoteĀ transparencyĀ andĀ team alignment.


UsingĀ survey-driven personasĀ (agesĀ 56+Ā andĀ 35–56), the team tailored solutions to user needs. Breaking downĀ epics into user storiesĀ withĀ clear acceptance criteriaĀ enabled structured delivery.

Work was managed throughĀ JIRA, a collaborative tool that providedĀ real-time visibility, streamlinedĀ task assignment, and ensuredĀ team-wide transparencyĀ throughout the Agile lifecycle.


These techniques reflect coreĀ Business Analyst competencies, blending business insight, technical understanding, and collaborative planning. The project demonstrates how anĀ Agile mindsetĀ andĀ adaptive approachĀ are essential for delivering impactful outcomes inĀ waste management and recycling innovation.


āœ… 5. Reflection


TheĀ Recycle4ChangeĀ project demonstrates how a structured, end-to-end business analysis approach can deliver meaningful value in both technical and community-focused initiatives. From strategic insight and stakeholder alignment to detailed requirements management and Agile delivery, this project reflects my ability to bridge business needs with solution design.


By leveraging tools like Jira, RTM, BPMN, and story mapping, I was able to ensure clarity, traceability, and alignment across all stages of the BA lifecycle.

Ultimately, this experience highlights the importance of agility, collaboration, and a user-centred mindset in delivering impactful, sustainable outcomes.

Comments


@ 2025 YANITHA. All rights reserved

​

bottom of page