PROJECT MANAGEMENT PLAN

Project Name: project-name-here

Version: version-here
Author: your-names-here
Date Submitted: MM/DD/YY

Version: Document Title: Page:

Version 1.0 (Name of Project) 1-13
Project Plan
Content

s
PROJECT MANAGEMENT PLAN...........................................................................................................1
1. INTRODUCTION...............................................................................................................................3
2. PURPOSE...........................................................................................................................................3
3. DEFINITIONS, ABBREVIATIONS, ACRONYMS..........................................................................3
4. REFERENCES....................................................................................................................................3
5. PROJECT ORGANIZATION.............................................................................................................4
6. PRODUCT OR SERVICE TECHNICAL DESCRIPTION.................................................................7
7. MANAGEMENT PROCESSES........................................................................................................12
8. TECHNICAL PROCESSES..............................................................................................................13
9. PROJECT SCHEDULE.....................................................................................................................13
10. BUDGET INFORMATION..........................................................................................................14
11. DOCUMENT REVISION HISTORY...........................................................................................14

Version: Document Title: Page:

Version 1.0 (Name of Project) 2-13
Project Plan
1. INTRODUCTION
[introduction: Give a short description ( should only be half page of the document) of the type of solution
you will provide the client. For example : the inventory management solution is an information system
designed to meet the inventory needs of the client and enhance their business operations. It is an end-to-
end solution for large scale enterprises to monitor and mange the inventory of stocks and deliver the
products and services to customers;

2. PURPOSE
[Purpose, scope of document. Do not extensively describe the purpose of the project itself. Make it brief]
The purpose of this Project Management Plan document is to communicate the business need to all
project and technical team members to ensure the end product meets the business objectives. It is the
second phase of project management and will be used to:

● Design the solution to be delivered by mapping business requirements to the new system.

● Test that requirements are delivered correctly

● Measure the quality of the project deliverables and outcome of Key Users’/Stakeholders’
needs and expectations

3. DEFINITIONS, ABBREVIATIONS, ACRONYMS

Term Definition
Application The software component of the system
SOP Standard Operating Procedure
[ex.] [these are examples. Remove above, or add below.]
CFMIS Corporate Financial Management Information System
FR Financial Reporting
GL General Ledger

4. REFERENCES
[this can be the source or legal references used in this Management Plan document. Sample below:]
 FDA Guidance for the Content of Premarket Submissions for Software Contained in Medical
Devices
 Draft Guidance for Industry and Food and Drug Administration Staff Mobile Medical Devices
 FDA 21 CFR Part 820 Quality System Regulation
 [above are examples. add or remove as needed. Note: all management plans must reference the
Project Management Plan. Additionally, the Project Management Plan must reference all other
management plans. These references reflect the relationship between the Integration KA and all
other KAs]

Version: Document Title: Page:

Version 1.0 (Name of Project) 3-13
Project Plan
5. PROJECT ORGANIZATION
[text-here. Summarize the management hierarchy and management methodology.]

The Project Team must present an organizational chart indicating at least the following personnel for this
project.

a. Project Manager - The Project Manager must be responsible for the overall delivery of the
project scope and deliverables.
b. System Analyst - The System Analyst must be responsible for determining the needs of a client
and translating them into system specifications.
c. User Interface Developer -The User Interface Developer must render the graphics design and
user-friendly interface of the application in accordance with the preferred design and functionality
of the application.
d. Frontend Developer - The Frontend Developer must implement responsive web design
principles to ensure the web-based application renders well across multiple devices.
e. Backend Developer - The Backend Developer must work alongside the Frontend Developer to
develop and implement a high-quality user interface.
f. Quality Assurance Specialist - The Quality Assurance Specialist must be responsible for
monitoring, inspecting, and proposing measures to correct or improve the web-based application
in order to meet established quality standards.

Key Staff No. of Qualification and Experiences

Staff

Project Manager 1 Bachelor’s degree in Computer Science, Information

Technology, Business Administration or similar field

Preferably with 3-5 years experience in project

management

Extensive knowledge of project management standards,

processes, procedures and guidelines

Sound knowledge of the software development life cycle

Proven experience in the following:

● Jira

Version: Document Title: Page:

Version 1.0 (Name of Project) 4-13
Project Plan
 ● Draw.io
● Google applications
● Microsoft applications
Excellent verbal and written communication skill

System Analyst 2 Bachelor’s degree in Computer Science, Information

Technology, Business Administration or similar field
With at least 3-year experience in system analysis
Strong knowledge of the software development life
cycle
Proven experience in the following:
● Jira
● Draw.io
● Microsoft programs
● Google applications
● Good verbal and written communication skills

ITIL Foundation Certificate in IT Service Management

User Interface Developer 1 Bachelor’s degree in information technology or similar

field

With at least 5-year experience as a UI/UX Designer or

any similar role

Excellent interpersonal and communication skills

Expert in discussing and explaining design options

Demonstrable experience UI/UX design software such

as but not limited to:
o Adobe XD
o Sketch
o Figma

Hands-on experience with image editing software (e.g.

Adobe Photoshop, Adobe Illustrator)

Strong knowledge of Usability Factors in Human

Computer Interaction

Frontend Developer 1 Bachelor’s degree in Computer Science, Information

Technology, or similar field

With at least 5-year experience in front-end web

development

Excellent knowledge of the CSS framework

Version: Document Title: Page:

Version 1.0 (Name of Project) 5-13
Project Plan
 Experienced in the following:
o JavaScript (e.g. ES6)
o NodeJS
o ReactJS
o Redux
o React Router
o RESTful web services
o Agile product development

Backend Developer 1 Bachelor’s degree in Computer Science, Information

Technology, or similar field.

With at least 5-year experience in API development or

integration.

Excellent knowledge of PHP and Laravel framework or

Java and Spring Framework

Preferably with experience in NodeJS using Adonis

framework

Demonstrable experience in OOP, Security, refactoring,

application architecture and design patterns.

Experienced in the following:

o REST or SOAP API integration.
o Agile product development environment.
o Test-Driven Development.

Able to design optimal database structures

Knowledgeable in columnar database Knowledgeable in
microservice architecture

Quality Assurance Specialist 1 Bachelor’s degree in Computer Science, Information

Technology, or similar field.

With at least 5-year experience in quality assurance

engineering

Strong knowledge of the following:

o Software Development Life cycle
o Testing Life Cycle
o Bug Life Cycle

Expert in the following:

o Testing Tools (Postman, TestRail)

Version: Document Title: Page:

Version 1.0 (Name of Project) 6-13
Project Plan
 o Bug Tracking Tools (Jira)
o Other related tools
o Automation tools (Selenium, Appium and etc.)

6. PRODUCT OR SERVICE TECHNICAL DESCRIPTION

[text-here. Describe the product or service- which is the reason the project is being implemented. This
may also include technical description. What will be the main features and functions of the project.
Referencing the Scope Statement is encouraged.]

 GENERAL SYSTEM CAPABILITY

The system will help improve the operational process of the Local
Government by providing easier access to Local Government services for
its citizens. The system will also help the Local Government to improve
the availability and accessibility of data and eliminate the need to wait for
the data to be manually encoded, thus removing the need for repetitive
manual data entry. The following will describe the general system
capabilities:
● LOGIN PAGE
○ The system is web-based and accessible to different
platforms, such as but not limited to desktops, laptops, and
smartphones.
○ The system shall be accessible in different web browsers,
such as, but not limited to, Google Chrome, Mozilla
Firefox, and Safari.
○ The system shall recognize login of account type and user
level based on the credentials of users inputted in the login
form. The system shall have form and field validation on
the login page entry fields.
○ The system shall provide a default landing page for end-
user portals/landing screens for applications.

Version: Document Title: Page:

Version 1.0 (Name of Project) 7-13
Project Plan
 ○ The system shall support password reset functionality,
password recovery, and manage sessions if there is an
existing device logged into the application/portal.
● DATA PRIVACY
○ The system shall be capable of allowing the end-user to
accept or refuse any privacy policies, terms, or agreement
conditions through the system.
○ The system shall retain the past version and version control
of all privacy policy changes.
○ The system shall prompt users when accessing, storing,
sharing or utilizing personal or financial information within
or in between systems.
○ The system shall provide a shortcut for viewing the policies
and terms and conditions.
● SYSTEM MAINTENANCE
○ The system shall manage creation and updating of account
through the citizen/applicant portal and admin portal in the
user management module.
● NOTIFICATION
○ The system shall send an SMS notification for OTP upon
registration and payment notification.
● INTEGRATION
○ The system shall be able to support integration with the
Electronic and Collection System (EPCS) via API
Integration.

 CORE/ADMINISTRATOR PORTAL

Version: Document Title: Page:

Version 1.0 (Name of Project) 8-13
Project Plan
 The Core/Administrative Portal will be a web-based application wherein
the Administrator must be able to access, view, and manage the following
modules:
● DASHBOARD
○ The system shall provide a comprehensive statistical
overview of the Total Number of Registration and Total
Finished Transactions. The system shall display a graphical
representation of the Real Property ax (RPTax), and
Business Tax (BTAX).
○ The system shall display the total collection statistics and
geo-mapping location of the Local Government.

● REGISTRANT/SUBSCRIBER
○ The system shall enable the Administrator to view the list
of residents registered with the system and allow the
Administrator to view the personal information of the
citizen. The Administrator shall have the capability to add,
update, and delete a citizen's information and display the
attached documents.
● GENERAL SETTING
○ The system shall display a list of addresses of each region,
province and municipality.
○ The system shall be able to provide a list of billing setting.
○ The system shall display the list of citizens, FAQs,
requirements, and the list and description of modules.
○ The system shall enable the Administrator to display, add,
edit, and remove the Smart City services.
○ The system shall display the OTP setting.
○ The Administrator shall be given control by the system to
manage the website content.

Version: Document Title: Page:

Version 1.0 (Name of Project) 9-13
Project Plan
 ○ The system shall display the Business Establishment List.
● CITIZEN PORTAL
● Citizen Profile
■ PROFILE
○ The system shall allow the citizen to upload a
photo.
○ The system shall be able to show the personal
information of the citizen.
○ The systems shall allow the citizen to update their
personal information.
○ The system shall be able to add, update and delete
information.
■ APPLICATION
○ The system shall be able to display the list of
citizen’s transaction history.
■ BUSINESS
○ The system shall be able to display a list of
businesses under the citizen account.
○ The system shall be able to display the business
details :
■ Business Information
■ Business Activities
■ Application (Transaction History)
○ The system shall be able to pre-register a business
by providing the Business Identification Number
and the latest official receipt number.

Version: Document Title: Page:

Version 1.0 (Name of Project) 10-13
Project Plan
7. MANAGEMENT PROCESSES
[text-here. detail management methodologies. Start up plan, work plan, work activities, schedule,
recourse, budget allocation. ]

8. TECHNICAL PROCESSES
[text-here. Summarize technical processes including designing the project (or service), implementing the
product, testing the product, deploying the product. insert the process model here in a diagram ]

9. PROJECT SCHEDULE
[text-here. Strictly speaking, the project schedule with dates does not belong in the Project Mgmt Plan.
Schedule with dates is why we have a Gantt Chart and Project Schedule. Also, dates change, and we don’t
want to be required to update this document every time a date changes. A good approach I’ve seen is to
include a milestone list with anticipated cumulative durations to each gate. Though, if you feel strongly
about adding a draft schedule with dates, that is acceptable. Below is a milestone list. Note: each project
has a different milestone list. What are the 6-12 most important events (project gates) to your project?]

The service provider must deliver the system, but not limited to installation and
configuration, within the period of 90 calendar days on the proposed implementation
site of the client.
Project Timeline’s

Version: Document Title: Page:

Version 1.0 (Name of Project) 11-13
Project Plan
 Duration Responsible
Activities (Days) Entity Deliverables
Signed Contract

User Requirement Analysis

Winning Bidder,
Project Initialization 20 LGU Validated Solution
Execution and Winning Bidder, Design, Developed, and Integrated
Control 20 LGU Systems
Winning Bidder,
System Testing 20 LGU System Testing Reports
System Installation

Calibration / System Fine-Tuning

Winning Bidder,
Deployment 20 LGU System Production (Go-Live)
End-Users Training

Technical Training
End-User Training/ Winning Bidder,
Workshop 5 LGU Train the Trainers Training
Post Implementation Review
Winning Bidder,
Close-Out 5 LGU Sign Off

Estimated Project Duration: 90 Calendar Days

upon issuance of Notice to Proceed

10.BUDGET INFORMATION
[text-here. For the same reasons in #8 above, we don’t include detailed budget info here- that is what the
cost baseline and cost estimate documents are for. It is sufficient to simply reference Business Case
document if that financial information included is still current.]
₱,000.00 (VAT INC.)

11. DOCUMENT REVISION HISTORY

Version Author Date Remarks

1.0 2023 Initial Copy

Version: Document Title: Page:

Version 1.0 (Name of Project) 12-13
Project Plan
Version: Document Title: Page:
Version 1.0 (Name of Project) 13-13
Project Plan