You are on page 1of 12

AUTOMATED LAUNDRY MANAGEMENT SYSTEM

PROJECT MANAGEMENT PLAN


Version 1.0
Aug. 09,2019

[Insert appropriate disclaimer(s)]


<Project Name>

TABLE OF CONTENTS
1 INTRODUCTION.....................................................................................................................2
1.1 Purpose of Project Management Plan........................................................................2
2 EXECUTIVE SUMMARY OF PROJECT CHARTER........................................................2
2.1 Assumptions/Constraints............................................................................................2
3 SCOPE MANAGEMENT........................................................................................................2
3.1 Work Breakdown Structure........................................................................................2
3.2 Deployment Plan........................................................................................................3
3.3 Change Control Management....................................................................................3
4 SCHEDULE/TIME MANAGEMENT....................................................................................4
4.1 Milestones..................................................................................................................4
4.2 Project Schedule.........................................................................................................4
5 COST/BUDGET MANAGEMENT.........................................................................................5
6 QUALITY MANAGEMENT...................................................................................................5
7 HUMAN RESOURCE MANAGEMENT...............................................................................7
8 COMMUNICATIONS MANAGEMENT...............................................................................8
8.1 Communication Matrix..............................................................................................9
9 RISK MANAGEMENT............................................................................................................9
9.1 Risk Log...................................................................................................................10
10 ISSUE MANAGEMENT........................................................................................................10
10.1 Issue Log..................................................................................................................11
11 PROCUREMENT MANAGEMENT....................................................................................11
12 COMPLIANCE RELATED PLANNING.............................................................................11
APPENDIX A: PROJECT MANAGEMENT PLAN APPROVAL.........................................11
APPENDIX B: REFERENCES..................................................................................................13
APPENDIX C: KEY TERMS....................................................................................................13
APPENDIX D: SUMMARY OF SPENDING...........................................................................13

Page 1 of 13
[Insert appropriate disclaimer(s)]
<Project Name>

1 INTRODUCTION
1.1 PURPOSE OF PROJECT MANAGEMENT PLAN
This document provides the Software Project Management Plan of Automated Laundry
Processing System project for Easy Wash Laundry shop, which is about monitoring and
automation of calculation of the sales of the shop and claiming of customers’ laundry in a
web-based environment without the use of internet.
ALMS (Automated Laundry Management System) Software Requirement Specification
Report is prepared according to IEEE Recommended Practice for Software Project
Management Plan. This document includes the information such as purpose, scope,
constraints and assumptions of the project. In addition to this information managerial,
technical and supporting process plans such as work break-down structure.

2 EXECUTIVE SUMMARY OF PROJECT CHARTER


2.1 ASSUMPTIONS/CONSTRAINTS
Constraints:
1. Scope – project outcome as defined in the document
2. Timeline – important milestones and client imposed completion dates
3. Resources – availability of skilled human resources or materials
4. Risks – uncertainties associated with the project
Project Team – maximum team members are 4. All staff has other commitments outside
the project

3 SCOPE MANAGEMENT
3.1 WORK BREAKDOWN STRUCTURE
LABORATORY RENTAL EQUIPMENY SYSTEM
1. System Preparation
1.1 Implementation Notice
1.2 Identify System Environment
1.2.1 Technical Preparations
1.2.2 Identify Development Environment
1.2.3 Identify Quality Assurance Environment
1.2.4 Identify Training Environment
1.2.5 Identify Production Environment
1.3 Documentation Updates
2. Testing
2.1 System Testing
2.1.1 Define Test Scripts
2.2 User Acceptance Testing
2.2.1 User Acceptance Test Documents
2.2.2 Define User Acceptance Test Scripts
2.2.3 Test Functionality
2.3 System Deployment
3. Project Close Out
3.1 System Evaluation

Page 2 of 13
[Insert appropriate disclaimer(s)]
<Project Name>
3.2 Client Acceptance Documentation
3.3 Post Implementation Report

3.2 DEPLOYMENT PLAN


PLAN DESCRIPTION
Hardware

Software
Installation
Learning Learning center gives the users
Center opportunity to try out the system and
can be comfortable in handling.
Business
Process

3.3 CHANGE CONTROL MANAGEMENT


Change
Scope Description Status Date
Number
In
Change affecting scope
1 Scope Review
In
Change affecting time
2 Time Progress
3 Duraction Change affecting duration open
In
Change affecting cost
4 Cost Progress
5 Resources Change affecting Resources open
In
Change affecting deliverables
6 Deliverables Progress
7 Product Change affecting Product open
8 Processes Change affecting process open
9 Quality change affecting quality open

4 SCHEDULE/TIME MANAGEMENT
4.1 MILESTONES
The table below lists the milestones for this project, along with their estimated completion
timeframe.
Milestones Estimated Completion
Timeframe
Project charter approved 2 weeks estimated
approval

Page 3 of 13
[Insert appropriate disclaimer(s)]
<Project Name>
Milestones Estimated Completion
Timeframe
Project plan completed 3 weeks estimated
completion
Project plan approved 2 weeks
estimated time
with revisions
System design completed 2 weeks
estimated time
completed
Test plan completed 1 week estimated
time
Client Acceptance 3 days estimated
time with
workshop and
seminar about the
system
Project closed out 5 days
completion with
maintenance

4.2 PROJECT SCHEDULE


After this page

5 COST/BUDGET MANAGEMENT
Months
Activity
June July August September October Total Cost
Client Meeting
Business Proposals
Data
Gathering/Survey
Materials
Documentary
Materials
Design/Templates
Project Equipments

Page 4 of 13
[Insert appropriate disclaimer(s)]
<Project Name>
Software License
Testing and
Implementation Cost
Labor
Maintenance

6 QUALITY MANAGEMENT
A Laboratory Equipment Rental System has an inventory tracker embedded to the system
to manage all the equipment on the laboratory room to meet the consistency and standards
of the equipment must inspect and segregate old and new equipment and must have an
daily inspections, audits, formal testing and to document defects in an existing traditional
tracking system. Quality measures may be no bugs nor defects for a certain critical
requirements consistent screen layout, or correctly calculating variables. To maintain
quality and consistency must do a quarterly maintenance, monthly filtering of database
directory, and quarterly updates.

Page 5 of 13
[Insert appropriate disclaimer(s)]
<Project Name>

7 HUMAN RESOURCE MANAGEMENT

8 COMMUNICATIONS MANAGEMENT

Page 6 of 13
[Insert appropriate disclaimer(s)]
<Project Name>
8.1 COMMUNICATION MATRIX

9 RISK MANAGEMENT

9.1 RISK LOG

10 ISSUE MANAGEMENT
Step 1 – Monitoring
 Analyze the business environment
 Consider what may impact on the company
Step 2 – Identification
 Assess from the business environment those elements that are important
 Identify the issue that impact on the company
 What is the type of issue and where is it in its lifecycle?
Step 3 – Prioritization
 What is the probability of occurrence?
 How immediate is the issue?
Step 4 – Analysis
 Analyze the most important issues in some detail.

Page 7 of 13
[Insert appropriate disclaimer(s)]
<Project Name>
 Determine their probable impact on the company or its division as precisely as
possible.
Step 5 – Strategy Decision
 What are the resources needed?
 What specific actions should be taken? By whom? When? With Whom?
 Develop issue management communication plan and consider timing.
Step 6 – Implementation
 Implement the system approved by the management.
Step 7 – Evaluation
 Assess result
 Evaluate the success of implementing system
 Capture lessons from failures and successes

10.1 ISSUE LOG


Another Document

11 PROCUREMENT MANAGEMENT
All group members are responsible for their roles and activities. They making sure that the
product are being built correctly. At the completion of each milestone, analysis should be
done. The activity analysis will be performed by group member during internal reviews to
make sure that the delivered products are right. A demonstration of the user interfaces to
the acquirer will be made.
All the testing activities are under the test team members’ responsibilities. There
will be two types of testing. One of them will be done after coding of each part; the other
will be done before publishing of the web site.

12 COMPLIANCE RELATED PLANNING


The company's management philosophy is based on responsibility and mutual respect. ER
maintains an environment and structure that encourages productivity.

- A user friendly system that enables the staff to check for availability of equipment.

- A system that stores rental information and saves a student information who rent a equipment
with e-signature

- Reservations and Allocations management based on differing contract durations and customer
requests

-Return consumables must be managed alongside rental equipment.

Page 8 of 13
[Insert appropriate disclaimer(s)]
<Project Name>

- Product Service Inspection/Repair including the ability to trigger maintenance activity based on
rental status, off-rent damage reports and clock hours or other service units.

Appendix A: Project Management Plan Approval


The undersigned acknowledge they have reviewed the <Project Name> Project
Management Plan and agree with the approach it presents. Changes to this Project
Management Plan will be coordinated with and approved by the undersigned or their
designated representatives.

Signature: Date:
Print Name:
Title:
Role:

Signature: Date:
Print Name:
Title:
Role:

Signature: Date:
Print Name:
Title:
Role:

Signature: Date:
Print Name:
Title:
Role:

Page 9 of 13
[Insert appropriate disclaimer(s)]
<Project Name>

APPENDIX B: REFERENCES
The following table summarizes the documents referenced in this document.
Document Name Description Location
and Version
Project A Baseline project where in Cantonjosmark47@gmail.com
Management Plan it will determine how it will
be able to achieve who will
be involved in this project,
reports needed to comply and
how information will be
communicated

APPENDIX C: KEY TERMS


The following table provides definitions for terms relevant to this document.
Term Definition
Quality the standard of something as measured against other
things of a similar kind; the degree of excellence of
something.
Milestone an action or event marking a significant change or
stage in development.
Human Resource Human resources is used to describe both the people
who work for a company or organization and the
department responsible for managing resources
related to employees.

APPENDIX D: SUMMARY OF SPENDING


[You may double-click on the table to edit it according to the information applicable to this
project.]

Page 10 of 13
[Insert appropriate disclaimer(s)]
<Project Name>

PY: Previous Year; CY: Current Year; BY: Budget Year

Page 11 of 13
[Insert appropriate disclaimer(s)]

You might also like