Software Development

Project Plan
for

PayWise

For CSC 313 (Project Management) Group B

List of Students in CSC 313 (Project Management) Group

Names Matric No
 Contents
1. Introduction
1.1 Project Overview
1.2 Project Approach

2. Project Initiation
2.1 Project Team and Roles
2.2 Teams Roles and Responsibility
2.3 Stakeholder and Customer
2.4 Project Environment
2.5 Project Charter

3. Project Planning
3.1 Project Scope
3.2 Wall Breakdown Structure (WBS)
3.3 Project Schedule (Gantt Chart) and Meetings
3.4 Project Resources Plan
3.5 Communication Plan
3.6 Project Standard and Procedures
3.7 Project Risk Plan
3.8 Project Budget Plan
3.9 Baseline Project Plan

4. Project Execution and Monitoring

4.1 BPP execution
4.2 Project Progress
4.3 BPP Changes

5. Project Closure
5.1 Close-out Plan
1. Introduction
1.1 Project Overview
PayWise is a mobile payment app which help students make payment for various fees to
be paid in Campus. The App allows each students access the application with their
Unique ID (Matric Number) and their password providing a secure payment system.
Role: To build an application to simulate the client ideas.

1.2 Project Approach

This section outlines the way you will roll out the technology, including the highest level
milestones.
Phase I: Initiating.
Phase II: Planning.
Phase III: Executing and Monitoring.
Phase IV: Closing.

2. Project Initiation
2.1 Project Team and Roles
The team generally has no hierarchy, with individual members taking on the roles
voluntarily.

Roles Names

Project Manager Tobi Mojeed

Secretary LIGALI Morenikeji

Financial Secretary Afolabi Eritobi

Obanla Mayowa
Software Developers
Yakubu Ahmed
Database Administrator Celestine Daniel

User Interface (UI) Designer Olaleye Olajesu

Software Tester Project Team

2.2 Teams Roles and Responsibility
Roles
Project Manager
Secretary
Financial Secretary
Software Developers
Database Administrator
User Interface (UI) Designer
User Experience (UX) Researcher
Software Tester
Description
Leads in planning, executing, monitoring,
controlling, and closing out projects.
Ensuring projects meet deadlines.
Managing relationships with clients and
stakeholders.
Organising and servicing meetings
(producing agendas and taking minutes).
Logging or processing bills or expense
Writing and implementing efficient code.
Working closely with other developers, UI
designers, UX Researcher.
Deploying software and maintaining the
existing software.
Responsible for the evaluation of database
software purchases.
Ensuring the security of company data.
Responsible for maintaining the integrity and
performance of company databases.
Gather and evaluate user requirements in
collaboration with project manager and
software developer.
Develop UI mock-ups and prototypes that
clearly illustrate how the app function and
look like.
Design graphic user interface elements, like
menus, tabs and widgets.
Carry out the qualitative research for the
project
Put users at the centre of a design to make
it simple, easy to use and good looking.
Detect and track software defects and
 inconsistencies.
Executing tests on software usability.
Preparing reports on all aspects related to
the software testing carried out and
reporting to the design team.

2.3 Stakeholders
At the stage, the Project Manager carries the task of identifying the stakeholders for
project which include:
Internal Stakeholders, directly involved in the project.
1. Project Manager.
2. Project Teams.
3. Company.
4. Project Sponsor (Client).

External Stakeholders, linked indirectly to the project.

1. Customers.

2.4 Project Environment

The Project Environment as outlined by the Project Manager using System Development
Lifecycle (SDLC) environments.
1. Analysis and Design Environment
2. The Development Environment.
e.g IDE(Integrated Development Environment).
3. The Common Build Environment
4. The Testing Environment
5. The Production Environment

2.5 Project Charter

This document that formalizes a project and gives the project manager authority over the
project.

*Company Name* Project Charter

Project Name PayWise
PayWise is a mobile payment app which help students
Project Description
make payment for various fees to be paid in Campus.
Project Manager Afolabi Eritobi

Client Dr. Olusanya .O (Lecturer-in-Charge)

1. Increasing app traffic(user) by 10% this quarter.
Business Case 2. Establishing PayWise as a thought leader in the
payment system space in school.
1. Landing page for PayWise.
2. PayWise Android and iOS app.
Project Deliverables 3. Work Break down structure (WBS).
4. Project Plan.
5. Project Charter.
Project Budget 6 Million Naira.

Project Duration 3 Months, From 12th June 2021 to 12th August 2021

3. Project Planning
3.1 Project Scope
This project is for the development of a mobile payment app. There will be an app for
iPhones and Android Mobile Operating systems. The user interface will be designed as
part of the project but will contain, as a minimum, the ability to create and edit account
plan, add credit cards, view transaction history, and make transactions. The app must
include a walkthrough to make it easy to get started.
3.2 Wall Breakdown Structure (WBS)
The Document (Wall Breakdown Structure) illustrate the project task and their sequences.
3.3 Project Schedule (Gantt Chart) and Meetings
Meetings
The Meeting Agenda and Minutes were documented by the Project Secretary(Morenikeji)
Meeting 1
Time: 17th June, 2021, 1:40PM to 2:17PM
Where: SBK 3 (Lecture Room)
Attendees: 20180204041, 20180204037, 20180204038, 20180204025, 20180204030,
20180204027, 20180204019, 20180204029, 20180204028, 20180204040, 20180204020

Agenda
 Choose Project
 Review Project
 Choose Project Manager
 Determine Roles for People
 Choose Process
 Summary

Minutes
The meeting got off to a rough start, with many having difficulties locating the group
gathering
 Mr Adeleye Joseph dropped his idea which is about updating the College Library,
outlining the problems affecting the College Library proffer solutions.
 Another idea was dropped by Mr Tobi Mojeed which is a solution to Payment in the
School, with the process to get it done. The group decided to work on the Payment
Application.
 The assigning of role was a bit too chaotic, so we decided to do pick the roles
voluntarily.

Meeting 2
Time: Fill this Later*
Where: COSIT Ground
Attendees: Fill this Later*

Agenda
 Plan Project
 Determine the Document
 Summary

Minutes
 Mr Tobi Mojeed (Project Manager) came up with a name for the Project “PayWise”.
 Project Manager came up with the lists of documents to be prepared before the
completion of the project.

3.4 Project Resources Plan

Key human resources involved in
the project include the Project
Sponsors, Project Manager and the
Project Team. Each brings skills
and attributes required to ensure
project success.
Key human resources involved in the project include the Project Sponsors, Project
Manager and the Project Team. Each brings skills and attributes required to ensure
project success. The table below lists and documents the type and number of resources
required during the project lifecycle.
Amount/Quality Duration
Resources Status Allocated
Required Required
June 14th,
Meeting Room 1 Reserved
2021
Smartphone (Android June 14th,
4 Allocated
and iPhone) 2021
June 14th,
Laptop 4 Allocated
2021
Web Technology
June 14th,
Knowledge(HTML, 2 Allocated
2021
CSS and JavaScript)
Flutter (Cross-platform
June 14th,
App Framework for 2 Allocated
2021
App Development)
June 14th,
Microsoft Access 1 Allocated
2021
June 14th,
Microsoft Word 1 Allocated
2021
Microsoft Project 1 Allocated June 14th,
 2021
June 14th,
Adobe Photoshop 1 Allocated
2021

3.5 Communication Plan

Communication Medium Frequency Audience Responsibility

Meeting,
Project Team Project Project
WhatsApp Chat Weekly
Communication Team Manager
App
Project
Meeting, PPT Project
Stakeholders Weekly Stakeholders
(Presentation) Manager
Communication
Board members Project Project
Meeting Weekly
Communication board Manager
FAQ’s (Frequently Project
Webpage One-time Users
Asked Questions) Manager

3.6 Project Standard and Procedures

This project teams follows some standard and procedure to achieve project success.
Project Procedures: Agile Project Management
Project Standard: Project Management Institute Standard.

3.7 Project Risk Plan

Risks Mitigation

Poor Quality Code Testing of all code

Inadequate Human Resources Maintain up-to-date documentation.

Effective selection of Delivery and project
Low Stakeholder Engagement
goals/priorities.
Poor Productivity Set achievable timeframes and a
 sustainable pace during your project
estimations to avoid burn-out of project
team.
End-user Engagement User testing and surveys

3.8 Project Budget Plan

Requirement Amount(Naira)

Domain Name 50,000

Hosting 100,000

Computer Equipment 800,000

Computer Software 50,000

Workmanship 4,500,000

Miscellaneous 500,000

Total Expenses 6,000,000

3.9 Baseline Project Plan

4. Project Execution and Monitoring
4.1 BPP execution
4.2 Project Progress
4.3 BPP Changes

5. Project Closure
5.1 Close-out Plan