Upload
yrro261606
View
227
Download
0
Embed Size (px)
Citation preview
8/14/2019 Project Mngt Plan
1/52
8/14/2019 Project Mngt Plan
2/52
Acknowledgment
8/14/2019 Project Mngt Plan
3/52
Table of ContentsTable of Contents ................................................................................................................3
I. Project Overview .............................................................................................................. 5
A. Project Name ..............................................................................................................5
B. Brief Description of the Project .................................................................................. 5C. Sponsors Name .......................................................................................................... 7
D. Project Manager and Key Team Members ................................................................. 7
E. Deliverables of the Project .......................................................................................... 7
F. Reference Materials ................................................................................................... 10G. Definitions and Acronyms ........................................................................................ 10
1. Definitions ..............................................................................................................10
2. Acronyms ............................................................................................................... 11II. Project Organization .....................................................................................................14
A. Organizational Chart .................................................................................................14
B. Project Responsibilities .............................................................................................14III. Management and Technical Approaches .....................................................................18
A. Management Objectives ............................................................................................18B. Project Controls .........................................................................................................19C. Risk Management ......................................................................................................20
D. Project Staffing .........................................................................................................26
1. Project Manager .....................................................................................................262. Graphical User Interface Team .............................................................................. 26
3. Database Administrator Team ............................................................................... 27
4. Domain Programming Team ..................................................................................27
5. In-house Quality Team .......................................................................................... 286. Business Analyst .................................................................................................... 28
7. Senior Network Engineer .......................................................................................29
8 Others 29
8/14/2019 Project Mngt Plan
4/52
15. Develop User Verification Subsystem .................................................................35
16. Develop Inventory Reorder Subsystem ...............................................................35
17. Develop Delivery Subsystem ...............................................................................3518. Develop Sales Subsystem .................................................................................... 35
19. Develop Returns Subsystem ................................................................................ 35
20. Develop Data Management Subsystem ...............................................................3621. Develop Reports Generation Subsystem ............................................................. 36
22. Construct Website ...............................................................................................36
23. Develop Beta Version ..........................................................................................3624. Conduct System Test ..........................................................................................37
25. Conduct User Acceptance Test ............................................................................3726. Develop final version of the program .................................................................. 37
27. Develop a users manual ......................................................................................3728. Conduct training ...................................................................................................37
B. Key Deliverables .......................................................................................................37
V. Project Schedule Information ........................................................................................43A. Summary Schedule ................................................................................................... 43
B. Detailed Schedule ......................................................................................................44
VI. Budget ..........................................................................................................................44A. Summary Budget .......................................................................................................44
B. Detailed Budget .........................................................................................................49
8/14/2019 Project Mngt Plan
5/52
I. Project Overview
A. Project Name
Inventory Management System for a Furniture Exporter
B. Brief Description of the Project
This project aims to provide our client a secure, efficient and user-friendlyInventory Management System to assist them in addressing the inventoryproblems they face while going about their business.
The following objectives will be met by the project:
The system should assign access rights to certain users such as the
warehouse personnel who has access only to the functions related to
ordering and receiving new inventory, and the salesperson, who canonly perform functions involving the sale or return of inventory, and
the administrator, who should have access rights to all. It should add
new authorized persons or remove the existing ones.
Each authorized user should log in using a valid username and
password.
The system should keep a record of all products offered by the
store. The record includes the product code, product name, price, andnumber of stocks on hand.
8/14/2019 Project Mngt Plan
6/52
When a customer returns a product, the salesperson should be able
to verify that the product was brought from the store by searching forthe sales transaction by date and/or customer name. The system should
then record the data for two kinds of scenarios: Refund. The system
should automatically increase the count of the product returned andrecord the transaction. Exchange. Aside from increasing the count of
the product returned, the count of the product given to the customer in
exchange should be decreased. The transaction details should also berecorded. Transaction details that the salesperson needs to enter
include the date, product code, quantity returned, and whether it wasexchanged or refunded.
When products are returned to a supplier, the warehouse personnel
should be able to choose from the list of inventory, enter the quantity
to be returned, and note down the specific defects of the product to bereturned. This should automatically reduce the current count of the
products returned. The system should keep a record of the transaction.
If an inventory audit finds a discrepancy between the physical
inventory count and the inventory control system count, the
administrator should be allowed to make adjustments in the inventorydatabase. He/she should be able to search for the product by name or
code, and then change the inventory count for that product. A
transaction record describing the change should be created. The record
should contain the date, the product code, the old amount, the newamount, and the username of the person who made the change.
The system should keep a supplier database containing the
8/14/2019 Project Mngt Plan
7/52
C. Sponsors Name
Tim RobertiChief Executive Officer
AE Design Concepts, Inc.
Upper Tingub
Mandaue City, 6014 CebuPhone: (63 32) 343 9169
Fax: (63 32) 343 9170
E-mail: [email protected]
D. Project Manager and Key Team Members
Project Manager: Arianne Joy Garing
Key Team Members: Roanne Abecina
Jocelle LunaAna May Obmina
E. Deliverables of the Project
Listed below are the products that will be produced as part of the project and
a brief description for each. They are explained in more detail in the section about
the work to perform.
Deliverable Type Description
8/14/2019 Project Mngt Plan
8/52
the project
Test plan Document Describes how the system will be tested
Training plan Document Describes the plan for training clients inthe use of the system
Work breakdownstructure (WBS)
Document Lists the activities required to accomplishthe project and its objectives
Schedule baseline Document The approved planned schedule for the
project, used to measure project progressand schedule performance
Cost baseline Document The approved time-phased budget for theproject, used to measure and monitor cost
performance
Risk management
plan
Document Describes the procedures for managing
risk throughout the project
User inputs Document Compilation of user feedback, comments,
and suggestions
Server Hardware Contains the server software and enables
the sharing of files and resources in thenetwork
Client computers Hardware Computers that serve as the users
workstations. They request access to
information and resources, and areconnected to the server as clients.
Router switch Hardware Delivers routing functionality along withtraditional switching capabilities for the
networkModem Hardware Needed to connect to the Internet.
Firewall and VPN
device
Hardware Provides protection of private information
by preventing unauthorized access to or
8/14/2019 Project Mngt Plan
9/52
functions that they have access rights to
Inventory reorder
subsystem
Software Enables the user to prepare a purchase
order to replenish stocks, and submit it forapproval. Once approved, it may beprinted and sent out to the appropriate
supplier
Delivery subsystem Software Enables the user to record the acceptance
of new stocks when they are delivered by
a supplier
Sales subsystem Software Enables the user to record the sale of an
itemReturns subsystem Software Enable the user to record the return of an
item by a customer
Data management
subsystem
Software Enables the user to add, edit, and delete
user, product, and supplier information
Reports generation
subsystem
Software Enables the user to obtain information
about transactions in an organized format
Website Software Enables the site visitor to viewinformation about the company and its
products, contact the marketing arm of the
company, and register to be able to orderonline
Beta version Software All software subsystems integrated intoone working version of the system, used
for further testing
Final version Software Final version of the system to be turnedover to the sponsor
Users manual Document Serves as a reference material to usersregarding the use of the system
8/14/2019 Project Mngt Plan
10/52
F. Reference Materials
Project Charter
Project Communication Plan
Project Scope Statement
Quality Assurance Plan
Change Management Plan
G. Definitions and Acronyms
1. Definitions
Software Development Process
A software development process is a structure imposed on the
development of a software product. Synonyms include software life cycleand software process.
Work Breakdown Structure (WBS)In project management and systems engineering, it is a tool that
defines a project and groups the projects discrete work elements in a way
that helps organize and define the total work scope of the project.
Bug
A software bug is an error, flaw, mistake, failure, or fault in acomputer program that prevents it from behaving as intended (e.g.,
producing an incorrect or unexpected result).
8/14/2019 Project Mngt Plan
11/52
2. Acronyms
8/14/2019 Project Mngt Plan
12/52
8/14/2019 Project Mngt Plan
13/52
CDR Critical Design Review
CI Configuration Integration
CM Configuration Management
DID Data Item Description
FCA Functional Configuration Audit
FGD Focus Group DiscussionFQR Formal Qualification Review
GUI Graphical User Interface
LAN Local Area Network
PDR Preliminary Design Review
PM Project Manager
PRR Production Readiness ReviewSCM Software Configuration Management
SDL Software Development Library
SDP Software Development Process
SDR System Design Review
SIP System Implementation Plan
SOW Statement of Work SPM Software Project Management
SQA Software Quality Assurance
8/14/2019 Project Mngt Plan
14/52
II. Project Organization
A. Organizational Chart
Arianne Garing
Project Manager
Tim Roberti
Project Sponsor
Felix Hagad
Procurement Officer
Executive Steering Committee
Amaya BengzonMarketing Manager
Business Analyst
Jocelle Luna
Technical Lead
Senior Java DeveloperI
Senior Java Developer
II
Junior Java Developer
I
Junior Java Developer
II
GUI and Web Team
Ana May Obmina
Interface Expert
Senior Web
Programmer
Web Developer
Database Admin Team
Roanne Abecina
MySQL
Database Expert
Database Administrator
Network
Carlos Muro
Senior Network
Engineer
Quality Assurance Team
Roanne AbecinaSoftware Quality
Assurance Engineer
Tester
Project Organizational Breakdown Structure2/21/2009
8/14/2019 Project Mngt Plan
15/52
Committee
Provide business content expertise
Remove project barriers
Provide business requirements input, testplanning, test execution, and User Acceptance testingsign-off
Provide business sign-off for project
milestones as needed
Ensure that the appropriate business resourcesare available to meet project schedule and project
deliverables
Ensure that the business needs are met
Project Manager
Manage daily project tasks
Manage project deliverables, resources, andschedule
Track project progress to plan and manage the
project plan
Facilitate project communication, project
decision making, project issue resolution, and projectrisk management
Facilitate Monthly Executive Steering
Committee meetings
Review project deliverables, facilitate
adjustments as needed, and facilitate change approval
Issue and Change management log owner
Project Status Report author
Provide leadership in the coordination of
assigned project tasks for the technical team
Provide technical architect and design
8/14/2019 Project Mngt Plan
16/52
Provide technical expertise in the area of networkadministration, components, and implementation
Complete technical tasks related to the setup,configuration, and testing of the network of different
workstations and the website
Recommend and administer hardware and network
decisions
Provide documentation as required for the project
Interface Expert
Provide technical expertise for the design and setup of
the systems user interface. Set product direction and UI requirements based on
business, user and brand needs
Collaborate with product managers, engineers andresearch specialists to define the user experience
Design user interaction models, workflows and user
interfaces.
Work hand in hand with web developers and java
engineers to deliver the final product Engage in system development
Integrate systems to achieve flow-through efficiency
and performance
Promote a strong Management and processenvironment that guarantees the integrity and
continuity of business information
Facilitate workshops to capture business requirementsusing use cases as required
Develop software designs adhering to companys
technical standards, architecture and frameworks.
8/14/2019 Project Mngt Plan
17/52
Develop software designs adhering to companystechnical standards, architecture and frameworks.
Ensure adherence to coding standards and technicalstandards.
Ensure adherence to code versioning
policy/procedures (companys configuration
management), security policies and procedures.
Complete unit/system/regression testing as perpolicy/procedures
Other requirements as per assigned by Senior Java
Developer or Technical Lead
Senior WebProgrammer
Write codes for the web sites
Work on web-based applications, web enhancements,database-backed websites and web administration
processes
Collaboration with Interface Expert and Web
Developer to provide system end needs in GUI and
website part
Web Developer
Provide website design and implementation
Work on web-based applications, web enhancements,
database-backed websites and web administration
processes
Work closely with the Database and Domain Team to
meet customer and system specifications on the
website end
D t b
Provide technical expertise in the area of mySQL
databases
Complete technical tasks related to the setup,
8/14/2019 Project Mngt Plan
18/52
Tester
Design test cases
Write test scripts
Test modules and identification of bugs Creation of bug reports and test results
III. Management and Technical Approaches
A. Management Objectives
Management deems large corporations as a long-term business partner.
Hence, the management supports the timely completion of the Inventory
Management System project for the client.
Since project inception, the management has been involved by sealing its
approval, and then supporting its commencement. They have reviewed the
project proposal and approved providing resources in order to accomplish projectrequirements. Correspondingly, they have approved of a 6 million Philippine
Peso budget, which will be released on a staggered-basis.
Management is also well-informed of the six-month project timeframe.
They are determined to see the project through and would like to be updated on
the projects progress. They would like to keep track of the accomplishment ofproject milestones provided in the proposed Gantt chart schedule. At the same
8/14/2019 Project Mngt Plan
19/52
Manage Data
Aside from meeting the project software specifics, management wouldlike to ensure the excellent quality of the product. The management supports the
creation of an internal quality team, who will not include the project manager and
staff members who have been instrumental to the completion of the project. Theywould like to hear their opinions in terms of how well the project team has created
the Inventory Management System software as against the project proposal.
In case of significant circumstances that will affect the projects
completion, the management would like the project team to take steps to resolveit. However, the management would like to be informed of such circumstances,and management decisions when issued should hold.
B. Project Controls
Project management plan shall serve as a reference material as to theproposed deliverables, costs, schedule, and the like. It shall be reviewed by the
project team in order to keep track of their deliverables and work schedules.Likely deviations from the proposed plan shall be determined and communicated
to the projects key stakeholders; namely, the management team and the project
sponsor. These deviations shall be approved by the Change ManagementCommittee, who will be represented by the management team.
It is the project teams objective to minimize the changes in the projectplans. Hence, the Weekly Status Reports shall assist in determining the progress
of the project team. The Weekly Status reports shall be checked against the
proposed deliverable timeline and work schedules. Issues which impede the
8/14/2019 Project Mngt Plan
20/52
The Change Management Committee shall review the Change Request
Form. They shall evaluate on the necessity of the request. Upon careful
evaluation, they shall warrant an approval or otherwise. Once it has beenapproved, it shall be communicated to the project manager. The project manager
shall be responsible for the dissemination approved changes to the project team.
He or she shall take the succeeding steps to realize the approved changes.
Approved Change requests shall be properly documented. Project
proposals which shall affect with the change shall be revised. The revised projectproposals shall be archived accordingly.
Referenced below is the Change Request Form template.
Change Request Form Template
1) Nature of the Change Request
Briefly describe the nature of the change request
Include the company staff who has requested for the change
2) Change Request evaluation
Refer to the Risk Management Plan for preventive and/or
corrective actions
Assess if those actions can be administered within the project
team, without affecting the proposed deliverable and workschedule timeline
Evaluate the necessity of Change requests. Project Manager
shall be responsible for its evaluation.3) Change Request status
Note if it has been forwarded to the management team.
8/14/2019 Project Mngt Plan
21/52
sponsor, stakeholders, management, and the project team sit together and discuss
potential problem areas. Enumerated below are the potential problem areas in
relation to the nine knowledge areas.
8/14/2019 Project Mngt Plan
22/52
Knowledge Area Risk Conditions
Integration Poor integration management
Inadequate planning
Lack of post-project review
Scope Inadequate scope Management
Poor definition of scope
Incomplete definition of quality requirements
Time Schedule estimation error
Poor time allocation
Cost Cost estimation errors
Unaccounted financial adjustments
Quality Poor attitude toward quality
Substandard design/materials/workmanship
Inadequate quality assurance program
Human Resources Poor conflict management Poor breakdown of responsibilities
Poor definition of responsibilities
Absence of leadership
Communications Lack of communication initiative
Carelessness in communicating
Lack of consultation with key stakeholders
Risk Ignoring riskProcurement Unenforceable conditions or contract clauses
Adversarial relations
8/14/2019 Project Mngt Plan
23/52
In response to the identified problem areas, the stakeholders, sponsor,
management, and the project team came up with a list of strategies to respond tothe above-mentioned concerns. Summarized in those strategies are the mitigation
plans, contingency plans, severity or impact on the project and an estimate of the
likelihood of occurrence.
Mitigations plans include the steps that the company will undertake inorder to reduce the probability of the occurrence of risk. On the other hand,
Contingency plans lay down the predetermined action the concerned team willtake, if the risk is realized.
Description
Mitigation
Plan
Contingency
Plan
Severity/
Impact
Likelihood
of
Occurrence
1.Poor Integration
Management
Project team
will produce adetailed project
integration
report.
Managementwill review the
monthly
reports & askproject-specific
questions to
ensure goodproject
integration
Low
8/14/2019 Project Mngt Plan
24/52
project team
5.
Poor definitionof scope
Scope revision
Scope review
& approval bymanagement,sponsor,
stakeholders, &
project team
Incomplete
projectrequirements
Low
6.
Incompletedefinition of
qualityrequirements
Review project
and its related
quality score.
Incorporatemissing quality
criteria.
Review quality
guidelines
Substandard
product Low
7.
Schedule
estimation error
Project team
administers
scheduleadjustments
Project team
plans theschedule.
Management
reviews
monthlyprogress as
against the
proposedschedule.
Project delay Low
8.Poor time
allocation
Project teamadministers
time allocationadjustments.
Project teamallocates the
time.
Project delay Low
Review the
cost estimation External and
8/14/2019 Project Mngt Plan
25/52
.
design/materials/workmanship
product
revisions to
meet qualitystandards.
quality
auditors;
Product qualityaccountability
product
13
.
Inadequate
quality
assuranceprogram
Perform
product
revisions tomeet quality
standards.
Review quality
guidelines
Substandard
productLow
14
.
Poor conflictmanagement
Discussionwith involved
parties
Encourage
friendlyatmosphere and
constructivecriticisms
Project delay Low
15.
Poor breakdownof
responsibilities
Revisions onbreakdown of
responsibilities
Project team
creates thebreakdown of
responsibilities
Overworked orUnderworked
personnel
Low
16
.
Poor definition
of
responsibilities
Revise
definition of
responsibilities
Project team
defines the
responsibilities
Unclear
responsibilitiesLow
17
.
Absence of
leadership
Appoint a
ProjectManager
Project
Manager mustbe assigned.
Untimely
decisions;Project delay
Low
18
Lack ofcommunication
initiative
Producerequired
Require
Milestone &Monthly
No project
updatesLow
8/14/2019 Project Mngt Plan
26/52
23.
Adversarialrelations
Legal
department
consultation
Legal
department
consultation
Project delay Low
D. Project Staffing
Project Manager shall anticipate the required knowledge and skills needed
to accomplish the Inventory Management System project. The management team
shall be consulted prior to hiring the necessary personnel. On the other hand, therecruiting team shall design and warrant an attractive remuneration and incentivepackage for the new team members of the project.
Below are the targeted personnel who are deemed crucial to the successfulimplementation of the Inventory Management System project.
1. Project Manager
The Project Manager shall administer the successful
implementation of the project. He or she shall be knowledgeable of theclients requirements, companys capacity to fulfill the clients
requirements, and teams capability to realize the projects requirements.
He or she shall lead the team in designing a project plan which details how
the project shall be accomplished. He or she must also be updated withthe progress of the project and must ensure that the project be completed
within the proposed time schedule. At the same time, he or she shall also
be instrumental in the project staffing requirements of the project He or
8/14/2019 Project Mngt Plan
27/52
order to understand the visual requirements of the project. Aside from the
visual appeal, the GUI team must also consider the simplicity of the
software interface. The terms that will be used in the GUI system must beunderstandable. Technical or jargon terms must be avoided, if possible.
For the clients ease, the client must be able to walk through the interface
system without referring to the manuals technical dictionary or manual.The clients business familiarity should be sufficient in understanding
what the interface button does.
3. Database Administrator Team
The Database Administrator team shall be composed of twopeople; the MySQL DBA Expert and the Database Administrator. They
will design the database of the Inventory Management System project.
Together with the client and project team, they will pinpoint the necessary
variables to be included in the project database system. They willdetermine and consider the characteristics of the variables in their database
design. Once the variables have been determined, they will propose for an
efficient and workable database design. They will also define how thedatabase design shall be implemented. These proposals must be
communicated with the rest of the project team so as to assess its viability.
Design and implementation concerns of the project team must beaccounted for. The Database Administrator team shall assess their design
and implementation proposal once again. Upon careful assessment, the
Database Administrator team shall come up with a revised plan. Therevised plan shall be communicated once again to the whole team. With
the project managers approval, the Database Administrator team shall
commence with their task. If within the middle of its design, the Database
8/14/2019 Project Mngt Plan
28/52
proper. The Domain Programming team will then assess the most
effective programming language to be used for the software product.
They shall consider the advantages and disadvantages of the shortlistedprogramming languages. They shall also note the existing technical skills
and knowledge the company houses. In-house technical skills and
knowledge shall be utilized to assure projects successful implementation.If the current Domain Programming team assesses that there is an unmet
technical need, the recruiting team shall be informed. With the Domain
Programming teams recommendation and managements approval, therecruiting team shall advertise the need for an external technical
programmer, consultant, project-based programmer, or new programmerwho shall fill in the needs of the project. The Domain Programming team
shall absorb the new team member. They shall be responsible ineducating the new team member of his or her roles and responsibilities.
The new team member shall be considered officially part of the project
team. The new team member shall actively participate in the advancementof the project teams goals.
5. In-house Quality Team
The In-house Quality team as their name suggests will be internal
quality company personnel who are not included in the InventoryManagement System project team. They shall be composed of two quality
team members---the Quality Tester and the Software Quality Assurance
Engineer---who will be oriented as to the project requirements. The In-house Quality team shall be knowledgeable of the industry quality
standards and assess the final software product based on those criteria.
Apart from that, they shall ensure that the product software includes all of
8/14/2019 Project Mngt Plan
29/52
7. Senior Network Engineer
The Senior Network Engineer shall be responsible for the smooth
data transition between and/or among hardware and software components.
He or she shall install hardware and software compatibilities. He or sheshall also be responsible for troubleshooting networking concerns. The
Senior Network Engineers service may be extended to the external client
to ensure the smooth integration of the Inventory Management System
software project to the existing network in the clients company.
8. Others
Other personnel determined as necessary by the project team,stakeholders, sponsors, and management shall be included in the project
team provided appropriate approval has been secured.
E. Technical Processes
Management employs the technical and business expertise of its in-houseemployees for the successful implementation of the Inventory Management
System project. In relation to business knowledge, the management deems it
appropriate to assign a Business Analyst who will be able to interpret and
understand the clients specifications and unique requirements. The managementwould prefer a business analyst who has a thorough knowledge of an Inventory
system. TheBusiness Analystwill work together with the project team.
8/14/2019 Project Mngt Plan
30/52
full-description, on the other hand, will enumerate the step-by-step process of the
implementation of the software feature. In the Inventory Management System
project case, it will start with the users interface with the system. The systemasks for the appropriate username and password. And the system displays
interfaces and performs functions accordingly.
Moreover, the project team will work on the better interpretation of their
Use-Case diagrams. That is, the Use-case diagram will be further elaborated as a
System Sequence Diagram. In this diagram, the external users, who are the business owners and employees, will be represented as an actor. Actors will
interact with the internal classes of the software. Interactions between theexternal users and internal software classes will be represented in sequential
terms.
Apart from the sequential description of interactions, equally important is
the description of object interactions. This will be reflected in the accompanyingCollaboration diagram. Collaboration diagrams are extracted from the System
Sequence Diagram. However, collaboration diagrams serves to highlight the
interaction among objects. Sequences can be deduced from the numberingsequence referenced beside an object.
Objects will be further defined through class diagrams. These class
diagrams houses the variables and methods of an object. Variables will beidentified based on their name and attributes. Methods, on the other hand, will be
defined through their unique functions or tasks. Class diagrams will then serve as
a blueprint for the programmers.
The final technical document will describe the project in paper-based
form. Initially, it will describe the unique business tasks of the Inventory
8/14/2019 Project Mngt Plan
31/52
1.2. Identify key stakeholders1.3. Prepare business case1.4. Develop project charter
2. Planning2.1. Hold project kickoff meeting2.2. Prepare team contract2.3. Develop scope statement
2.3.1. Conduct domain analysis2.3.2. Prepare customer statement of requirements
2.4. Develop a communication plan2.5. Develop a quality assurance plan
2.6. Develop a change management plan2.7. Develop a test plan2.8. Develop a training plan2.9. Prepare WBS2.10. Prepare schedule and cost baseline
2.10.1. Determine task resources2.10.2. Determine task durations2.10.3. Determine task dependencies2.10.4. Create, review and finalize Gantt chart
2.11. Identify, discuss, and prioritize risks3. Executing
3.1. User inputs
3.2. Hardware and Software Installation3.2.1. Prepare purchase order3.2.2. Track shipping3.2.3. Setup equipment
3.3. System Design
3.3.1. Design User Interface3.3.2. Design Website
3.3.3. Design Database3 4 System Development
8/14/2019 Project Mngt Plan
32/52
3.7.2. Conduct training4. Controlling
4.1. Weekly status reports4.2. Monthly status reports
5. Closing5.1. Turnover product5.2. Prepare final project report5.3. Prepare lessons learned report
1. Conduct domain analysis
In order to determine the requirements and specifications of thesystem, the team needs to analyze the business for which the system is
being developed. Domain analysis involves evaluating existing systems
and processes, identifying information, events and users in the domain,and determining their relationships. The main products of this work
package are concept definitions, association definitions, and attributedefinitions. These will help in determining what needs to be done by theproject, and are thus helpful in developing the project scope statement.
2. Prepare customer statement ofrequirements
For this work package the team will need heavy sponsor or user
involvement in order to describe the kinds of problem in the domain to be
addressed, and how they are solved in the current practice. The customer
8/14/2019 Project Mngt Plan
33/52
This work package is also based on the WBS. It involves
determining how long each of the tasks would take, taking into
consideration the actual amount of time needed to work on a task andelapsed time.
5. Determine task dependencies
In this work package the relationships or dependencies among
project activities are identified. The team needs to ascertain whethercertain activities can be done in parallel, whether some can only start
when others have finished, or whether some can overlap. This work
package results in determining the sequence of project activities.
6. Create, review and finalize Gantt chart
In view of the duration estimate and task dependencies, a Ganttchart needs to be produced illustrating the timeline of the project. An
initial draft must be created, and then reviewed by the team members
assigned to do the tasks. The whole team must ultimately agree upon afinal Gantt chart.
7. Preparepurchase orderA purchase order must be accomplished listing the hardware and
software products needed for the project It must be signed off by the
8/14/2019 Project Mngt Plan
34/52
10. Design User Interface
This work package involves coming up with an illustration of howthe system will look like. The user interface design should have screenmock-ups and must include the parameters users will need to enter. It
describes the navigational paths that one will follow when using the
system. It also specifies the format of forms and reports.
11. Design Website
Designing the website entails deciding on the websitesappearance, content and map. The websites appearance must be described
using screen mock-ups so as to show the formats, graphics, forms, and
links to be used. Web content should show the kinds of information thatcan be viewed on the website, as well as any images or articles. Mapping
refers to where certain features or information are located in the website.
12. Design Database
The systems database needs to store information regarding users,products, suppliers, and transactions such as sales, returns, orders, and
deliveries. Designing the database involves determining the specific
attributes of the entities that need to be recorded, as well as therelationships among the entities. The output of this work package is a
database schema that defines the tables, the fields in each table, and the
relationships between fields and tables.
8/14/2019 Project Mngt Plan
35/52
15. Develop User Verification Subsystem
The goal of this work package is to develop and test a softwaremodule in Java that takes in the user name and password entered throughthe user interface and compares the information with those on the
database. If the user entered a valid username and password, he or she will
be given access to certain parts of the system according to his or heraccess rights. Otherwise, he or she will be shown an error message and be
given two more chances to successfully log in.
16. Develop Inventory Reorder Subsystem
The team will also need to code and test in Java the module that
will enable the authorized user to prepare a purchase order. It must pullinformation from the database to provide the user a list of products to
choose from. The user can then specify the amount to order. The system
should be able to sort the order into separate purchase orders according tosupplier and compute for an estimate purchase price for each. The user
will have the option to send the purchase orders for approval. Once
approved, the purchase order may then be printed.
17. Develop Delivery Subsystem
This work package involves coding and testing the software
module that will allow the user to record delivery of new inventory. The
user should be able to retrieve the purchase order corresponding to the
8/14/2019 Project Mngt Plan
36/52
This work package involves coding and testing the software
module to record a return of a product. Again, the authorized user can
search for the product or choose from a list, then indicate the amountreturned. He or she will then select whether the product was refunded or
exchanged. If it was refunded, the system will merely increase the quantity
on hand of the product by the quantity returned. If it was exchanged, anadditional step would be to choose the product(s) given in exchange and
decrease their quantity on hand accordingly. The transaction will generate
a returns record.
20. Develop Data Management Subsystem
Certain users will have access to adding, editing, and deleting
information in the database. An authorized warehouse personnel, for
example, will be able to add, edit, and delete product and supplier
information, while the administrator will in addition be allowed to add,edit, and delete user information in order to manage access rights. The
coding and testing of the software module implementing these processes isdone in this work package.
21. Develop Reports Generation Subsystem
Another important feature of the system is the generation of sales,
returns, delivery, and inventory report. The authorized user will be able tochoose the type of report and the period covered by the report, and then
the system will automatically generate the requested report based oninformation stored in the database This work package involves the coding
8/14/2019 Project Mngt Plan
37/52
24. Conduct System Test
This work package involves letting the technical team run the beta
version and look for any bugs.
25. Conduct User Acceptance Test
Representatives from the sponsor will also need to test run the betaversion and provide feedback regarding the user experience.
26. Develop final version of the program
The beta version must be refined in view of technical and user
inputs in this work package.
27. Develop a users manual
Once the final, working product is completed, the team mustprepare a users manual to aid the sponsors employee in learning how to
use the system. This is a useful training material will also serve as a
reference after system roll out.
28 Conduct training
8/14/2019 Project Mngt Plan
38/52
Initiating
Business case This document serves as the project proposal as it
drives at the need of the business for the project. Itshould include an introduction, business objective,current situation and problem/opportunity
statement, critical assumptions and constraints,
analysis of options and recommendation,preliminary project requirements, budget estimate
and financial analysis, schedule estimate, potential
risks, and exhibits.
Project charter This document officially recognizes the existenceof the project. It must list the project title, project
start and projected end date, project manager, project objectives, approach, roles and
responsibilities, sign-off of all key stakeholders,
and comments from stakeholders.
Planning
Team contract This document should help promote teamwork and
clarify team communications. It should enumeratethe project team code of conduct, and the
guidelines for participation, communication andproblem solving. The team contract must be agreed
upon by all team members in a meeting.
Customer statement of
requirements
This document should list the business problems or
opportunities the system is to address and all
requirements. Each requirement should state thatthe user should be able to do using the system or
what the system should do automatically.
Project scope statement This document helps improve the accuracy of time,
8/14/2019 Project Mngt Plan
39/52
Test plan This document will describe how the system will
be tested. It must include details such as who will
do the testing, when testing will be done, and howbugs will be reported.
Training plan This document will describe the plan for training
clients on how to use the system. It must specify
the names of the trainers, the topics to be covered,and the date and time of training.
Work breakdown structure This document lists the activities required to
accomplish the project. It provides the basis for
creating the project schedule and forecastingproject performance. It should have at least three
levels and must use the project managementprocess groups as its main categories.
Schedule baseline This document is the approved planned schedulefor the project. It is used in measuring project
progress and schedule performance. A Gantt chart
must be used to list the project activities and their
corresponding start and finish dates. It mustcontain milestones, summary tasks, individual task
durations, and arrows showing task dependencies.
Cost baseline This document is a time-phased budget used to
measure and monitor cost performance. It should
list the WBS items and the costs of accomplishingthem on a monthly basis.
Risk management plan This document describes the procedures for managing risk throughout the project. It must list
all perceived risks and suggest preventive and
corrective actions for each.
8/14/2019 Project Mngt Plan
40/52
Processor 3065 Processor (2.33GHz, 65W,
1333 FSB, 4MB)
Cache Memory: 1 x 4MB Level 2 cache Memory: 512 MB PC2-6400
Storage Managementler HP Embedded 6
Port SATA Managementler with embedded
RAID (4 ports for HDD)
Hard Drive: 160GB SATA HDD
Internal Storage: Maximum 3TB (4 x
750GB) SATA
Optical Drive 16x SATA DVD-ROM
Form Factor Micro ATX Tower (4U)
Client computers These computers are connected to the server asclients. A client requests access to information and
resources. The client computers to be used by the
system need to meet the at least the followingspecifications:
Memory: 2GB DDR2
Hardisk: 160Gig SATA
Operating System: Windows XP
Router switch This piece of hardware delivers routing
functionality along with traditional switching
capabilities at very high rates of speed andefficiency. It should provide integrated intelligence
for filtering and security, as well as flexibility fornetwork design and traffic patterns.
Modem This piece of hardware will be used to transmit
8/14/2019 Project Mngt Plan
41/52
User Interface Design This document must describe how the system
would like to a user. It must include screen mock-
ups to show the system layout, suggested formats,and graphics.
Website Design This document must include the site map,
suggested formats, graphics, and content.
Database Design This document must present a database schema for
storing and manipulating information on users,
products, suppliers, and transactions. It must define
the tables, the fields in each table, and the
relationships between fields and tables.User Interface Subsystem This segment of software code corresponds to the
presentation layer of the system. It is the means by
which the user interacts with the system. As such it
must easily be understood and navigated. It mustalso allow the user to enter pertinent data that the
system will use for processing.
Database Subsystem This segment of software code corresponds to the
data layer of the system. It must containinformation according to the database design.
User Verification Subsystem This segment of software code corresponds to the
domain layer of the system. It must accept as input
from the interface the username and password andverify the information against the information
stored in the database. Upon a match, it should
allow the user to proceed. Otherwise, it shouldshow an error message. It must limit the access of
the user to the functionalities that he or she has
access rights to.
8/14/2019 Project Mngt Plan
42/52
in the database accordingly. The process must be
completed by the creation of a transaction record
in the database.Returns Subsystem This segment of software code corresponds to thedomain layer of the system. It must accept as input
from the interface the products and quantities
returned and whether they were refunded orexchanged. In either case, the quantity on hand of
the products must be increased. For an exchange,
however, the quantity of the products given in
exchange must be decreased. The process must becompleted by the creation of a transaction record
in the database.
Data Management Subsystem This segment of software code corresponds to the
domain layer of the system. It should allow the
user to add, edit, and delete user, product, andsupplier information stored in the database. The
process must be completed by the creation of a
transaction record in the database.Reports Generation Subsystem This segment of software code corresponds to the
domain layer of the system that pulls information
from the database according to user specificationsand presents it in an organized manner. Generated
reports should be accurate and must follow the
specified format.
Website The website should be linked to the database and
provide information to users real-time. It musthave the following features: user registration or
log-in, article on a featured product, view of the
8/14/2019 Project Mngt Plan
43/52
with. On-the-job training should also be
conducted.
ManagementWeekly status reports These documents are produced after weekly
meetings that update the whole team of the
projects progress. They must include the actualaccomplishments of the project team, measured
against the proposed schedule and budget. A brief
description of each accomplishment must be
provided. Issues and concerns must also be
reported. Monthly progress reports These documents are produced after monthly
meetings that are held to discuss the progress of
the project. It should summarize the
accomplishments for the current month, plans forthe following month, and important issues that
surfaced or are still important. The dates and
description of approved or requested changes to
the project must also be included in these reports.Closing
Final project report This document provides a summary of the project.
It must include the project objectives, a summary
of the project results, original and actual start andend dates, original and actual budget, project
assessment, a transition plan, and annual project
benefits measurement approach. Documentsrelating to project management and to the product
need to be attached to the final project report.
Lessons learned This document details the important things the
8/14/2019 Project Mngt Plan
44/52
B. Detailed SchedulePlease refer to the attached file PM Plan Network Diagram.pdf
VI. Budget
A. Summary Budget
Costs play a crucial role in the successful implementation of the Inventory
Management System project. A project cost has its boundary. And a boundary
overboard might be unprofitable for the company. Hence, it is important that thecompany consider an exact amount which will serve as a boundary line for the
project cost. Extending beyond the boundary must be put into careful assessment
by the projects stakeholders. Profitability and other considerations must be
assessed. Correspondingly, appropriate actions must be recommended. Usually,a project cost overboard may conclude with the project termination.
Noting these, it is important that the Inventory Management System bereasonably priced. It is also equally important that the design and creation of the
Inventory Management System be profitably undertaken. Hence, the creation of a
project costs estimate will be necessary in the successful implementation of theproject.
Items which are pertinent to the projects completion shall be identified.These items will be determined as part of major categories such as Human
R H d S ft d th lik A i th it th i
http://opt/scribd/conversion/tmp/scratch2537/PM%20Plan%20-%20Network%20Diagram.pdfhttp://opt/scribd/conversion/tmp/scratch2537/PM%20Plan%20-%20Network%20Diagram.pdf8/14/2019 Project Mngt Plan
45/52
Project team
compensation
908,118.18 Project Team shall comprise of 14 members, including
the Project Manager. It shall consist of a Technical
Lead, Senior Java Developer I, Senior JAVA DeveloperII, Junior GUI Developer I, Junior GUI Developer II,
Interface Expert, mySQL DBA Expert, DBAdministrator, Senior Network Engineer, Tester,
Software Quality Assurance Engineer, and Business
Analyst. Compensation is calculated based from themonthly income of the project team members and the
numbers of hours he or she has worked.
Hardware 241,700.00 Hardware shall include three desktop computer clientsand one main computer server. The computer hardware
package shall include a display monitor, keyboard,
mouse, LAN Cards, Printers, and other specialperipherals such as cables and racks. Network hardware
such as router, switch, firewall and VPN, shall be
included as well.
Software 2,380,881.82 Software shall include the Windows XP Operating
license installed in every computer terminal the companywill utilize. It shall be calculated based on the cost of thesoftware license and the total number of computer
terminals used. It also includes the labor costs for
developing the software components of the system.
Testing 262,258.18 Testing shall include the mandatory quality test on the
final software product. The Testing procedure shallensure that the quality standard has been met. At the
same time, it shall verify that the proposed software
features operate in the final software product. More thanthat, it shall also cover the integration testing of the
8/14/2019 Project Mngt Plan
46/52
the like. Support expense shall be incurred for the
smooth integration of the final software product to the
external client's system. It shall include the softwaresystem installation costs.
Team BuildingActivities
60,000.00 Team building expense shall be accounted for the purpose of encourage team communication and
cooperation. It is also hoped that informal gatheringsshall minimize and resolve conflicts, should they arise.
Team Building activities will be determined by the project team. The budget will be accounted for as a
recurring monthly expense.
Administration
Needs
60,000.00 Administration needs shall cover the non-core related
Inventory Control System project expense. It shall be
considered as a petty cash fund for immediate
administration needs such as paperclips, bond papers,staplers, pen, and the like. It shall also be used for
reproducing Weekly Status reports, Monthly Progressreports, Communication Templates, and the like. Other
non-core related expenses shall be covered as well.
Transportation
Allowance
120,000.00 Transportation allowance shall be accounted for as a
recurring monthly expense as the project is being
designed. It shall consider the travel expenses to and
from the client's site. It shall also cover the travelexpense the various commercial computer shops. Other
transportation expense incurred for the benefit of the
8/14/2019 Project Mngt Plan
47/52
The costs estimate, on the other hand, is referenced on the table below.
GOAL Microsystems Cost Estimate
#Units/Hrs Cost/Unit/Hr SubtotalsWBS Level 1
Totals% ofTotal
WBS Items
1. Project Management 908,118.18 18%
Project manager 296 454.55 134,545.45
Project team members
Technical Lead 296 284.09 84,090.91
Senior JAVA Developer I 296 227.27 67,272.73
Senior JAVA Developer II 296 227.27 67,272.73
Junior GUI Developer I 296 170.45 50,454.55
Junior GUI Developer II 296 170.45 50,454.55Interface Expert 296 227.27 67,272.73
mySQL DBA Expert 296 227.27 67,272.73
DB Administrator 296 170.45 50,454.55
Senior Network Engineer 296 227.27 67,272.73
Tester 296 142.05 42,045.45
Software Quality Assurance Engineer 296 142.05 42,045.45
Business Analyst 296 198.86 58,863.64
OT reserves* 148 397.73 58,800.00
2. Hardware 241,700.00 5%Client computers 6 26,500.00 159,000.00
Server 1 51,000.00 51,000.00
Router Switch 1 5,000.00 5,000.00
Modem 1 1,700.00 1,700.00
Firewall and VPN 1 25,000.00 25,000.00
3. Software 2,380,881.82 47%
8/14/2019 Project Mngt Plan
48/52
Windows XP Software 7 7,000.00 49,000.00
Project manager 760 454.55 345,454.55
Technical Lead 760 284.09 215,909.09
Senior JAVA Developer I 760 227.27 172,727.27
Senior JAVA Developer II 760 227.27 172,727.27Junior GUI Developer I 760 170.45 129,545.45
Junior GUI Developer II 760 170.45 129,545.45
Interface Expert 760 227.27 172,727.27
mySQL DBA Expert 760 227.27 172,727.27
DB Administrator 760 170.45 129,545.45
Senior Network Engineer 760 227.27 172,727.27
Tester 760 142.05 107,954.55
Software Quality Assurance Engineer 760 142.05 107,954.55
Business Analyst 760 198.86 151,136.36OT reserves* 380 397.73 151,200.00
4. Testing (10% of total hardware &software costs) 262,258.18 262,258.18 5%
5. Software packaging 40,000.00 1%
Software CD 1 5,000.00 5,000.00
Software & Hardware manuals 1 35,000.00 35,000.00
6. Training and Support 120,000.00 2%
Trainee Cost 1 50,000.00 50,000.00
System Installation 1 50,000.00 50,000.00
Travel Cost 1 20,000.00 20,000.00
7. Others 300,000.00 6%
Team Building Activities 6 10,000.00 60,000.00
Administration needs (Paperclip, folder, etc) 6 10,000.00 60,000.00
Transportation Allowance (to & from client'scompany) 6 20,000.00 120,000.00
8/14/2019 Project Mngt Plan
49/52
Marketing Expense 6 10,000.00 60,000.00
8. Reserves (20% of total estimate) 850,591.64 17%
Total project cost estimate 5,103,549.82
*Overtime Pay Computation
Daily salary = (monthly salary / 22 days)
Hourly OT rate = (daily salary / 8 hours) * OT rate
*OT rate
regular day -1.25%
non-working holiday - 1.30%
B. Detailed Budget
Apart from estimating the costs which may be incurred during the project, it is also crucial to determine when the costs
will actually be incurred. This projected cost flow will aid the management team and the related budget department in the
timely approval and release of funds. Integrating the release of funds when it is needed assures the project team that the fundswill be available just in time. This eliminates the wait time from the funds approval to its release date. Hence, it is also
necessary to prepare a cost baseline.
For the Inventory Control System projects purposes, the cost baseline shall project the estimated costs on a monthly
basis. Provided below is the proposed cost baseline for the six-month period.
Goal Microsystems Cost Baseline
1 2 3 4 5 6 Totals
WBS Items
1. Project Management
Project manager 22,424.24 22,424.24 22,424.24 22,424.24 22,424.24 22,424.24 134,545.45
8/14/2019 Project Mngt Plan
50/52
Project team members
Technical Lead 14,015.15 14,015.15 14,015.15 14,015.15 14,015.15 14,015.15 84,090.91
Senior JAVA Developer I 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 67,272.73
Senior JAVA Developer II 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 67,272.73Junior GUI Developer I 8,409.09 8,409.09 8,409.09 8,409.09 8,409.09 8,409.09 50,454.55
Junior GUI Developer II 8,409.09 8,409.09 8,409.09 8,409.09 8,409.09 8,409.09 50,454.55
Interface Expert 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 67,272.73
mySQL DBA Expert 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 67,272.73
DB Administrator 8,409.09 8,409.09 8,409.09 8,409.09 8,409.09 8,409.09 50,454.55
Senior Network Engineer 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 11,212.12 67,272.73
Tester 7,007.58 7,007.58 7,007.58 7,007.58 7,007.58 7,007.58 42,045.45
Software Quality Assurance
Engineer 7,007.58 7,007.58 7,007.58 7,007.58 7,007.58 7,007.58 42,045.45Business Analyst 9,810.61 9,810.61 9,810.61 9,810.61 9,810.61 9,810.61 58,863.64
OT reserves* 9,800.00 9,800.00 9,800.00 9,800.00 9,800.00 9,800.00 58,800.00
2. Hardware
Client Computers 159,000.00 159,000.00
Server 51,000.00 51,000.00
Router Switch 5,000.00 5,000.00
Modem 1,700.00 1,700.00
Firewall and VPN 25,000.00 25,000.00
3. SoftwareWindows XP Software 49,000.00 49,000.00
Project manager 57,575.76 57,575.76 57,575.76 57,575.76 57,575.76 57,575.76 345,454.55
Technical Lead 35,984.85 35,984.85 35,984.85 35,984.85 35,984.85 35,984.85 215,909.09
Senior JAVA Developer I 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 172,727.27
Senior JAVA Developer I 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 172,727.27
Junior GUI Developer I 21,590.91 21,590.91 21,590.91 21,590.91 21,590.91 21,590.91 129,545.45
8/14/2019 Project Mngt Plan
51/52
Junior GUI Developer II 21,590.91 21,590.91 21,590.91 21,590.91 21,590.91 21,590.91 129,545.45
Interface Expert 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 172,727.27
mySQL DBA Expert 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 172,727.27
DB Administrator 21,590.91 21,590.91 21,590.91 21,590.91 21,590.91 21,590.91 129,545.45
Senior Network Engineer 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 28,787.88 172,727.27Tester 17,992.42 17,992.42 17,992.42 17,992.42 17,992.42 17,992.42 107,954.55
Software Quality Assurance
Engineer 17,992.42 17,992.42 17,992.42 17,992.42 17,992.42 17,992.42 107,954.55
Business Analyst 25,189.39 25,189.39 25,189.39 25,189.39 25,189.39 25,189.39 151,136.36
OT reserves* 25,200.00 25,200.00 25,200.00 25,200.00 25,200.00 25,200.00 151,200.00
4. Testing (10% of total
hardware &software costs) 262,258.18 262,258.18
5. Software packagingSoftware CD 5,000.00 5,000.00
Software & Hardwaremanuals 35,000.00 35,000.00
6. Training and Support
Trainee Cost 50,000.00 50,000.00
System Installation 50,000.00 50,000.00
Travel Cost 20,000.00 20,000.00
7. Others
Team Building Activities 10,000.00 10,000.00 10,000.00 10,000.00 10,000.00 10,000.00 60,000.00
Administration needs
(Paperclip,folder, etc) 10,000.00 10,000.00 10,000.00 10,000.00 10,000.00 10,000.00 60,000.00
Transportation Allowance (to
&from client's company) 20,000.00 20,000.00 20,000.00 20,000.00 20,000.00 20,000.00 120,000.00
8/14/2019 Project Mngt Plan
52/52
Marketing Expense 10,000.00 10,000.00 10,000.00 10,000.00 10,000.00 10,000.00 60,000.00
8. Reserves (20% of total
estimate) 141,765.27 141,765.27 141,765.27 141,765.27 141,765.27 141,765.27 850,591.64
Totals 731,765.27 731,765.27 731,765.27 731,765.27
1,022,465.2
7
1,154,023.4
5 5,103,549.82
*Overtime Pay Computation
Daily salary = (monthly
salary / 22 days)Hourly OT rate = (daily salary / 8 hours) * OT
rate
*OT rate
regular day -1.25%non-workingholiday - 1.30%