PROJECT MANAGEMENT PLAN TEMPLATE

(Group No …..)

PROJECT MANAGEMENT PLAN

<PROJECT NAME>

NAME ID

DATE

1
TABLE OF CONTENTS

1.0 INTRODUCTION:
The Introduction provides a high-level overview of the project and what is included in this
Project Management Plan. This should include a high-level description of the project and
describe the projects deliverables and benefits. Excessive detail is not necessary in this section
as the other sections of the project plan will include this information. This section should
provide a summarized framework of the project and its purpose. Look back at the Project
Charter for information to include in this section.

2.0 PROJECT MANAGEMENT APPROACH

This section is where you outline the overall management approach for the project. This
section should describe, in general terms, the roles and authority of project team members. It
should also include which organizations will provide resources for the project and any resource
constraints or limitations. If there are any decisions which must be made by specific individuals
—for example authorizing additional funding by the project sponsor—this should also be stated
here. It should be written as an Executive Summary for the Project Management Plan.

3.0 PROJECT TITLE:

4.0 JUSTIFICATION:

5.0 OBJECTIVES AND PROJECT SCOPES:

State the objectives and scopes of the project in this section. The scope statement from the
project charter should be used as a starting point; however, the project plan needs to include a
much more detailed scope than the charter. This detail should include what the project does
and does not include. The more detail included in this section, the better the product. This will
help to clarify what is included in the project and help to avoid any confusion from project team
members and stakeholders.

2
6.0 OVERVIEW OF THE PROJECT: { Give a brief description of the system with use case
diagram}

The luxury resort management system will be made up of a number of modules that interact
with one another to manage unique facets of the inn's operations. A few of the main modules
are visitor check-in and check-out, lodging and stock management, billing and fee processing,
reporting, and reservation management. The inn's staff may be able to modify bookings and
room allocations, and the reservation management module will allow customers to make their
reservations online. The guest check-in and test-out module will speed up the procedure,
cutting down on wait times and enhancing the tourist experience. The workforce will be able to
manage room availability, inventory, and renovation schedules thanks to the room and
inventory management module, ensuring that all rooms are functional, well-maintained, and
ready for guest occupancy.  The team will be able to control guest billing, payment processing,
and refunds thanks to the billing and payment processing module, reducing errors and
enhancing financial management. In the end, the reporting module will offer hotel
management unique statistics on sales, occupancy rates, and other crucial parameters, enabling
them to make smart business decisions. Overall, by utilizing the power of C#, our luxury hotel
management system will increase financial control, streamline operations, and visitor
experience. We can build a reliable and scalable system that fits the requirements of any luxury
motel using the Internet framework and the Oracle 10g database. 

3
7.0 STAKEHODERS ANALYSIS:

4
8.0 MILESTONE LIST
Provide a summary list of milestones including dates for each milestone. Include an
introductory paragraph in this section which provides some insight to the major milestones.
This section should also mention or discuss actions taken if any changes to the milestones or
delivery dates are required.

Milestone Description Tentative Date

Completion of project charter, team formation, and initial kick-off

1. Project Initiation 15-Sep-2023
meeting.

In-depth analysis of resort management needs, resulting in a

2. System Requirements
detailed SRS document outlining functional and non-functional 25-Sep-2023
Specification (SRS)
requirements.

Creation of the overall system architecture, including module

3. High-Level Design 05-Oct-2023
breakdown and data flow diagrams.

5
 Detailed design of individual modules, including reservations,
4. Module Design and
guest services, billing, etc. Planning for module-specific 15-Oct-2023
Planning
development phases.

Design and development of the guest registration module,

5. Registration Module 25-Oct-2023
allowing for efficient guest check-ins and data capture.

6. Reservation and Design and development of the reservation module, enabling

05-Nov-2023
Booking Module guests to make bookings for accommodations and services.

Actual coding and development work for all modules based on

7. Complete Coding 20-Nov-2023
the design specifications.

Thorough testing of each module, including registration and

8. Internal Testing and
reservation, to identify and fix any bugs or issues. Integration 05-Dec-2023
Debugging
testing to ensure smooth communication between modules.

6
 Involvement of end-users to validate the system's functionality,
9. User Acceptance
usability, and overall performance, including registration and DD-MM-YYYY
Testing (UAT)
reservations.

Design and development of the guest services module, covering

10. Guest Services Module 20-Dec-2023
requests, concierge services, and personalized experiences.

Design and development of the housekeeping and maintenance

11. Housekeeping and
module, managing cleaning schedules and maintenance 05-Jan-2024
Maintenance Module
requests.

12. Billing and Invoicing Design and development of the billing and invoicing module,
15-Jan-2024
Module managing guest billing and generating invoices.

13. Point of Sale (POS) Design and development of the POS module, handling
25-Jan-2024
Module transactions at various resort outlets.

7
14. Staff Management Design and development of the staff management module,
05-Feb-2024
Module managing employee schedules, payroll, and attendance.

15. CRM (Customer

Design and development of the CRM module, managing guest
Relationship Management) 15-Feb-2024
profiles, preferences, and interactions.
Module

Integration of the mobile app, allowing guests to access services,

16. Mobile App Integration 25-Feb-2024
make reservations, and receive notifications.

Preparation of user guides, installation manuals, and technical

17. Documentation 10-Mar-2024
documentation for future reference.

18. Training and Training sessions for end-users and administrators on all
20-Mar-2024
Knowledge Transfer modules and functionalities.

19. Deployment Final deployment of the luxury resort management system, 05-Apr-2024

8
 including all modules, in a live environment.

20. Post-Deployment Gathering feedback from users, assessing system performance,

15-Apr-2024
Review and addressing any post-deployment issues.

21. Project Completion Formal project closure, documentation handover, and lessons
30-Apr-2024
and Handover learned for future projects.

9.0 Process Model to be followed: {Justify why this process model has been selected}

10.0 WORK BREAKDOWN STRUCTURE:

11.0: ESTIMATION:

Estimation for each module based on the lines of code and the number of programmers
needed. Let's assume an average project timeline of 6 months and a coding velocity of 1500
lines of code per programmer per month for C# development.

Here's a breakdown of the estimation for each module:

Registration Module:

Estimated Lines of Code (LOC): 1500 LOC

Number of Programmers Needed: 1500 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Reservation and Booking Module:

9
Estimated Lines of Code (LOC): 2000 LOC
Number of Programmers Needed: 2000 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Guest Services Module:

Estimated Lines of Code (LOC): 1800 LOC

Number of Programmers Needed: 1800 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Housekeeping and Maintenance Module:

Estimated Lines of Code (LOC): 1200 LOC

Number of Programmers Needed: 1200 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Billing and Invoicing Module:

Estimated Lines of Code (LOC): 1600 LOC

Number of Programmers Needed: 1600 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Point of Sale (POS) Module:

Estimated Lines of Code (LOC): 1400 LOC

Number of Programmers Needed: 1400 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Staff Management Module:

Estimated Lines of Code (LOC): 1700 LOC

Number of Programmers Needed: 1700 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

CRM (Customer Relationship Management) Module:

Estimated Lines of Code (LOC): 2100 LOC

10
Number of Programmers Needed: 2100 LOC / (1500 LOC/Programmer/Month * 6 months) ≈ 1
programmer

Total 8 programmers needed.

COCOMO MODEL

If we consider that our project is organic:

Then, Coefficient<Effort factor>= 2.4
Let's consider SLOC (Source line of coding) = 40,000
For organic projects the value of P (Project complexity) = 1.04
The value of T (SLOC - dependent coefficient) = 0.38
Effort = PM = Coefficient *(SLOC/1000) ^P PM (Persons-months needed for project) = 2.4
(40000/1000) ^1.04= 111.26
DM = (Duration time in months for a project) = 2.4 (111.26) ^ 0.38 = 14.38
Required Number of people = PM/DM = 111.26/14.38= 7.7 ~ 8

12.0 RESOURCE REQUIREMENTS

13.1 SOFTWARE REQUIREMENTS
13.2 HARDWARE REQUIREMENTS
13.3 HUMAN RESOURCE REQUIREMENTS

13.0: PROJECT SCHEDULE:

14.0 DELIVERY PLAN: If you follow the agile model then give the schedule for delivery of each
increment
15.0 RISK ANALYSIS:
16.0 QUALITY CONTROL PLAN:

11
17.0 BUDGET:

Category Number of People Monthly Rate (৳) Estimated Budget (৳)

Project Management 1 40,000 240,000

Programmers Total 32,000 6 * 32,000
Testing and QA Estimated 28,000 6 * 28,000
Documentation Estimated 24,000 6 * 24,000
Training Estimated 32,000 6 * 32,000
Miscellaneous Expenses 5,000
Total Budget 941000

18.0 CONCLUSION:

12