Faculty of Applied Sciences
Bachelor of Science in Computing

COMP313 Project Management

Term Project Report

Academic Year 2023/24 
2nd semester


Shared Bike App Platform






	
Group members:	
	Leo, YUAN HAO QUAN (P2215504)
	Kenny, KOU UN LONG (P2204712)
	
	
	
Submission Date:	Nov 29, 2024
 
Table of Contents 
1	Introduction	2
2	Project Scope Management	3
3	Project Schedule Management	4
4	Project Budget Management	5
5	Project Resource Management	6
6	Project Risk Management	7
7	Work Distribution	8

 
1	Introduction
This report presents the project planning and management aspects for the development of the shared bike software system commissioned by the local government. The purpose of this report is to detail the Project Scope Management and Project Schedule Management plans, ensuring that the project is completed successfully within the stipulated time frame and meets all specified requirements.
The local government has launched an initiative to address urban challenges such as increasing traffic congestion and deteriorating air quality. To promote a healthier and more sustainable lifestyle, they have introduced a shared bike program. Our company has been contracted to develop the software system integral to the operation of this program. This software will facilitate bike rentals and returns, manage the bike fleet, provide a user-friendly mobile application, integrate pricing and payment systems, and support operations and customer service.
We need to conduct this project to deliver a robust and efficient software platform that meets the government's requirements, contributing to the overall success of the shared bike program and, consequently, to the improvement of urban living conditions.
Team Charter
The project team comprises experienced professionals dedicated to delivering high-quality results within the project's constraints. The team members and their roles are as follows:
Name	Role	Responsibilities
Leo	Project Manager	Overall project management, scheduling, resource allocation, stakeholder communication
Bill	Senior Developer	Analysis and design, software architecture, database design
Lisa	Developer	UI/UX design, client-side coding
Andy	Developer	Server-side coding, integration
Kent	Developer	Client-side coding, testing
Vision: Our vision is to contribute to the transformative initiative of the shared bike program by delivering a state-of-the-art software system that will ease urban congestion, improve air quality, and promote a sustainable and healthy lifestyle for city dwellers.
Mission: To develop and deploy a robust, user-friendly, and secure software system that facilitates bike rentals, manages the bike fleet efficiently, integrates seamless payment options, and supports comprehensive customer service, ultimately contributing to the program's success.
Report Structure
The structure of this report is as follows:
•	Section 2 Project Scope Management: Presents the Work Breakdown Structure (WBS) of the project, detailing all tasks and deliverables in a hierarchical tree structure.
•	Section 3 Project Schedule Management: Includes the project schedule with necessary elements, the Network Diagram using the Precedence Diagramming Method (PDM), and a Critical Path Analysis (CPA).
•	…
2	Project Scope Management
In this section, we present the Work Breakdown Structure (WBS) for the shared bike software system project and the corresponding Gantt Chart. The WBS outlines all tasks and deliverables in a structured hierarchical format, ensuring a comprehensive understanding of the project's scope.
2.1 Work Breakdown Structure (WBS)
The project is divided into four main phases: Analysis, Design, Implementation, and Deployment. Each phase consists of specific tasks required to meet the project's objectives.
 
WBS Dictionary
Below is a brief description of each task in the WBS:
•	Analysis
o	a: Conduct a background study on e-payment implementations in similar projects to gather best practices and potential pitfalls.
o	b: Collect detailed requirements from relevant government departments regarding design preferences, compliance standards, and user needs.
o	c: Develop a prototype to demonstrate the payment procedure and gather early feedback.
•	Design
o	d: Design the overall software architecture, defining the system components and their interactions.
o	e: Design the database schema to support all required functionalities.
o	f: Design end-user interfaces for mobile applications, focusing on user experience and accessibility.
o	g: Design interfaces for administrative functions on desktop computers.
o	h: Design the signal connection mechanisms with bike locks for control operations.
o	i: Design the security scheme to safeguard transactions over the internet, ensuring data protection and compliance.
o	j: Develop interface templates for review, including layout, navigation, and visual elements.
o	k: Create a site map or hierarchy chart to illustrate the flow of web pages and user interactions.
•	Implementation
o	l: Create individual web pages based on the approved designs.
o	m: Create the database as per the designed schema.
o	n: Source necessary library modules for client-side coding to enhance development efficiency.
o	o: Purchase a set of bike locks for coding and testing purposes.
o	p: Code server-side modules for system administration and operations.
o	q: Code server-side modules for end-user services.
o	r: Code client-side modules for system administration and operations.
o	s: Code client-side modules for end-user services.
o	t: Integrate server-side modules and web pages to form a cohesive system.
•	Deployment
o	u: Test the connection to bike locks with the shared-bike app to ensure proper functionality.
o	v: Perform performance stress tests on the system to verify handling of transactions and concurrent users.
o	w: Conduct User Acceptance Testing (UAT) with the sponsor and end-user representatives.
o	x: Install the website on the government's web server for operation.
o	y: Create technical training materials for staff.
o	z: Train staff in operating and maintaining the system.
2.2 Gantt Chart
The Gantt Chart below visualizes the project schedule, illustrating task durations and dependencies to ensure a clear understanding of the project timeline.
 
Note: The start date is set as 01-01-2024. The milestones are set to the dates provided by the sponsor:
•	Prototype Delivery Milestone (m1): Prototype must be delivered within two months (by 01-03-2024).
•	Intermediate Modules Milestone (m2): Intermediate modules must be delivered within five months (by 01-06-2024).
•	Project Completion Milestone (m3): Project must be fully completed within eight months (by 01-09-2024).
Task Dependencies and Durations
The table below outlines each task's duration and dependencies:
Activity ID	Activity Name	Duration (Days)	Predecessors
a	Background study on e-payment implementation	18	-
b	Requirements Analysis	20	a
c	Technical Feasibility Study	22	b
d	System Design	25	b
e	Module Design	15	d
f	Interface Design	25	d
g	Database Design	15	f
h	UI Design	15	d
i	Security Design	20	d
j	Integration Testing	12	f, g
k	System Testing	12	j
l	Coding Core Modules	30	k
m	Coding Module E	20	e
n	Coding Module F	20	f
o	Develop UI	12	h
p	Database Implementation	25	i, g
q	Security Implementation	30	i
r	Testing Module N	25	n
s	Testing Module S	25	n
t	Final Integration	20	l, m, p, q, r, s
u	Deployment Preparation	5	t, o
v	System Deployment	5	u
w	User Training	5	v
x	Project Handover	12	w
y	Post-Deployment Support	20	x
z	Project Closure	20	y
 
3	Project Schedule Management
In this chapter, we present the project schedule management plan, including the Network Diagram in Precedence Diagramming Method (PDM) format, and conduct a Critical Path Analysis (CPA).
3.1 Network Diagram in PDM
The following network diagram represents the project's activities using the Precedence Diagramming Method (PDM). Each node corresponds to a task identified by its activity ID.
Legend:
•	Nodes represent tasks labeled from a to z.
•	Arrows indicate task dependencies.
 
3.2 Critical Path Analysis
Critical Path Analysis (CPA) identifies the sequence of tasks that determines the minimum project duration. Tasks on the critical path have zero slack.
3.2.1 Forward Pass (Calculating Early Start and Early Finish)
Task	Duration (Days)	Predecessors	Early Start (ES)	Early Finish (EF)
a	18	-	0	18
b	20	a	18	38
c	22	b	38	60
d	25	b	38	63
e	15	d	63	78
f	25	d	63	88
g	15	f	88	103
h	15	d	63	78
i	20	d	63	83
j	12	f, g	103	115
k	12	j	115	127
l	30	k	127	157
m	20	e	78	98
n	20	f	88	108
o	12	h	78	90
p	25	i, g	103	128
q	30	i	83	113
r	25	n	108	133
s	25	n	108	133
t	20	l, m, p, q, r, s	157	177
u	5	t, o	177	182
v	5	u	182	187
w	5	v	187	192
x	12	w	192	204
y	20	x	204	224
z	20	y	224	244
3.2.2 Backward Pass (Calculating Late Start and Late Finish)
Assuming the project's finish time is 244 days.
Here's the completed backward pass table:
Task	Duration (Days)	Successors	Late Finish (LF)	Late Start (LS)	Slack (LS - ES)
z	20	-	244	224	0
y	20	z	224	204	0
x	12	y	204	192	0
w	5	x	192	187	0
v	5	w	187	182	0
u	5	v	182	177	0
t	20	u	177	157	0
l	30	t	157	127	0
k	12	l	127	115	0
j	12	k, p	115	103	0
g	15	j, p	103	88	0
p	25	t	152	127	24
q	30	t	152	122	39
m	20	t	157	132	54
e	15	m	132	117	54
d	25	e, f, h, i	63	38	0
f	25	g, j, n	88	63	0
r	25	t	152	127	19
s	25	t	152	127	19
n	20	r, s	127	107	39
i	20	p, q	122	102	42
o	12	u	177	165	87
h	15	o	165	150	87
b	20	d, c	38	18	0
a	18	b	18	0	0
c	22	-	60	38	0
3.2.3 Identifying the Critical Path
Tasks with zero slack form the critical path. The critical path for this project is:
•	a - b - d - f - g - j - k - l - t - u - v - w - x - y - z
Project Duration: 8 months, 244 days (Including holidays)

4	Project Budget Management

This chapter should include the following items:
-	Resource sheet
-	Cost baseline (the cost schedule table for the 8 months)
-	The list of the PVs (Planned Values) for the 8 months
-	EVM chart (include all calculation steps)
-	Performance and Forecasting calculations 
-	Elaborations in a paragraph on the performance and forecasting 

5	Project Resource Management

This chapter should include the following items:
-	RACI chart (for tasks)
-	Resource Histogram (to show number of hours performed by individual members along the 8 months)

6	Project Risk Management

This chapter should include the following items:
-	The risk incidence 
-	Anticipated probability and impact on the project
-	Risk response
-	Potential secondary/residual risks