Menu
2025
Software Development Life Cycle was a hands-on, 11 Week experience - August, September and October of 2025; 90 Individuals from around the world came together to tackle real life problems and create the right solutions.
SDLC Experience Workshop
Team 02
Our team represents six countries, six time zones, and a wide range of levels of experience.
When we formed, we were a group of strangers - now we are a working team!
.jpeg)
Problem Statement:
In everyday social situations like dinners, group outings, or shared purchases, splitting the cost fairly often leads to confusion and awkwardness. People may forget what they owe, make incorrect calculations, or delay paying each other back. This can create tension between friends or cause someone to pay more than their fair share. Most existing payment apps are designed for one-on-one transfers, and few offer features that are built specifically for group situations. Users often resort to manual calculations, screenshots, or text message reminders, which are inefficient and unreliable. There is also a lack of transparency in who has paid and who hasn’t, making it hard to track or settle shared expenses quickly.
This creates several challenges:
• Lack of a clear system to split and track group payments
• Repetitive errors and misunderstandings in calculating individual amounts
• No central place to view or manage the full payment picture
• Social discomfort around reminding others to pay their share
A good solution should make it easy to enter shared expenses, calculate who owes what, and present that information clearly. It should also simulate or suggest payment methods to make the experience seamless and fair.
Our product will be a simple, friendly website that helps users solve this everyday problem with confidence and clarity.
Kanban Board (Agile)
-
The Project Tracker tool in Slack was used for task tracking and progress monitoring.
-
The Team worked with the Kanban Board view, which aligns perfectly with the Agile development approach.
-
It visualized the workflow providing a clear view of tasks as they moved through stages such as To Do, In Progress, In Review and Done.
-
This setup improved transparency and accountability, making the current status of each work item visible to all team members.
-
It also helped limit work in progress (WIP), allowing the Team to focus on completing ongoing tasks before starting new ones, thereby reducing bottlenecks and making deliverables more manageable.
-
A total of 11 Milestones were defined,
corresponding to the SDLC stages and the rhythm of the Event
-
The Milestones view of the Project Tracker clearly showed the Project timeline: how work was sequenced, where overlaps occurred, and how resources were distributed
-
To coordinate effectively across 5 time zones the worldtimebuddy.com service was used. (https://www.worldtimebuddy.com/) In addition to 11 common sessions 6 internal Team meetings were conducted.
Project Deliverables - By the Project Manager
Project Charter
-
The Project Charter artefact was used to capture the Project Requirements
-
It outlines the Project Goals and Objectives as measurable Success Criteria
-
Provides the Project Description and the expected delivery/outcomes
-
Defines the Project Stakeholders and the Target Audience of the final product
-
The Scope boundaries are also clearly established
-
The assessment of the project feasibility with the given Resources and Constraints was done
-
4 Project Risks were identified and mitigation strategies were developed accordingly
Project Deliverables - By the Product Owner
Product Canvas
-
The Product Canvas provides a one-page, high-level artefact that aligns the team on the product’s purpose, users, value, features, success measures, and risks. It outlines the following:
-
The Problem Statement which highlights the difficulties and inefficiencies in splitting and tracking group expenses, which lead to errors, delays, and social discomfort.
-
The Product Name identifies the product as “FairShare”, reflecting fairness, transparency, and simplicity.
-
The MVP (Minimum Viable Product) defines the initial core features needed to create, share, and track a group bill with up to 15 participants using a simple website/app interface.
-
The Metrics sets clear measures of success such as quick event setup, accurate calculations, faster settlement, higher completion rates, and repeat use.
-
The Target Audience (Big Picture) focuses on people who organise and participate in shared expenses for social dining, trips, and group activities, using simple web/app access.
-
The Product Details outlines the product’s structure, roles, data elements, user flows, and the limits of the MVP, keeping the experience simple and transparent.
.jpg)
Project Deliverables - By the Business Analyst
-
Use Case Diagram was used to provide a high-level, user-focused view of the system scope. 2 roles were identified: Bill Owner and Participant.
-
Use Cases Registry was developed to serve as a central repository for documenting and managing how users interact with a system.
-
A process map for the “Bill Owner - Create a Bill” flow was designed to visualize the process of creating a bill and splitting it between participants.
-
A process map for the “Participant - Update Payment Status” flow was designed to visualize the process of paying one’s share of the bill.
-
13 User Stories were developed to capture stakeholder and solution requirements. They were prioritized and organized in a backlog as work items, serving as the basis for team collaboration and as a single source of truth for subsequent requirement elaboration.
-
Business Rules Registry was used as a centralized, accessible storage for managing and governing the business rules that were identified during the requirements elicitation.
-
Low-Fidelity Wireframes were created to visualize and discuss the user experience and later served as the basis for high-fidelity wireframes and UI prototyping.
Use Case Diagram
Project Deliverables - By the UI/UX Designer
-
UX Screen map was created to show the structure, hierarchy, and interrelationships of individual screens, role-related functionality. It helped to estimate the workload involved in designing features, providing a clear overview of the project scope.
-
Hi-Fidelity wireframes were designed for all the screens (in different states) to visualize the UI and test the user experience for the Bill Owner Role and the Participant Role across all the use cases.
-
The generative AI was used to create a color palette and logo for the application in Visily (AI powered UI design software).
-
2 Clickable prototypes were created to provide a realistic simulation of the main user flows for the Bill Owner Role and the Participant Role and to facilitate clearer communication and collaboration among the Team Members.
Miro Link: https://miro.com/app/board/uXjVJWrzrTg=/?moveToWidget=3458764638170722648&cot=14
UX Screen Map
Project Deliverables - By the QA/Tester
-
Analyzed high-level requirements and user stories provided by the BA and PO teams to design detailed and comprehensive test scenarios.
-
Prepared User Acceptance Testing (UAT) scenarios to validate the product from the end-user perspective.
-
Collaborated with the development team to understand build timelines and ensured timely test execution post-build delivery.
Test Cases
-
Executed test cases and tracked defects using a centralized defect tracker.
-
Collaborated with developers for timely defect resolution and build verification.
-
Ensured overall quality through continuous testing and feedback throughout the SDLC.
.png)
Video Walkthrough of Solution
Solution Built by Segun Ofe and William Tijesuni - Company name: CloudsDew Tech
Development
· The frontend (user interface: comprising the login page, create new bill page and all other pages) was built using Vite, a lightweight version of ReactJS and Tailwind, a modern CSS framework that enables seamless responsiveness across mobile and web views.
· The backend, which allows users to create bills, add participants, and navigate between pages, was developed using Django, a high-level Python framework for building web applications.
· Also, the backend is powered by PostgreSQL database, which securely stores and manages all user data (like accounts and bill created) for the application.
Deployment
· The frontend code was deployed on Vercel. Vercel automatically detects the pushes to the GitHub repository, builds the project using the Vite configuration, and deploys the latest version.
· The backend code was deployed on a virtual machine (server) in the cloud, precisely Microsoft Azure using the URL of the frontend and other configurations.
· To enable automated deployment (CI/CD), we created a GitHub Actions pipeline script that automatically deploys the application to the server whenever code is pushed to the repository on GitHub.
Solution Alignment with Product Goals
We called our product “Fair Share” because it is short, friendly, and intuitive. The phrase is already familiar in everyday language, making the app approachable and memorable. It instantly communicates what the app does — helping people share expenses in a fair and effortless way.
We identified two roles in the process of paying a shared bill: Bill Owner and Participant. Each user can play both roles depending on which view they are navigating to.
The bill-splitting process starts when the Bill Owner creates a bill in the application. They fill in event details such as Location and Total Amount. Date/Time is generated automatically. These details are useful for tracking bills later.
The Bill Owner then adds Participants from their contacts, and the application automatically calculates the equal share for each participant, including the owner. The process is easy, straightforward, and very fast — immediately after creating a bill, the owner can pay their share right away.
The Bill Owner can view all bills they created on the Home screen. To make payment tracking easier, we defined three bill statuses:
-
Not Started – no one has paid yet
-
In Progress – at least one person has paid
-
Completed – everyone has paid their share
The Participant has a separate view on the Home screen showing all the bills they are part of. Two simple statuses are used to track their payments: Paid and Pending.
The entire process of splitting a bill and paying one’s share takes less than two minutes. User acceptance testing (UAT) showed a low error rate, while users reported high satisfaction, clarity, and intuitive user flows and interface.
_JPG.jpg)
