Professional Documents
Culture Documents
Girlie BCC
Girlie BCC
Girlie BCC
DOCUMENTATION
FOR
1 of 104
TABLE OF CONTENTS
2 of 104
1. PROCUREMENT MANAGEMENT PLAN 31
X. PROJECT STAKEHOLDER MANAGEMENT 32
1. STAKEHOLDER REGISTER 33
2. STAKEHOLDER ENGAGEMENT MATRIX 34
XI. APPENDICES 35
1. PROJECT DOCUMENTS 36
A. PROJECT PROGRESS MILESTONE CERTIFICATE 37
B. MEETING MINUTES 38
C. CHANGE REQUESTS 39
D. PROGRESS REPORTS 40
2. FORMS & TEMPLATES 41
A. AGENDA/ MEETING MINUTES 42
B. CHANGE REQUEST FORM 43
C. LESSONS LEARNED REGISTER 44
D. PROJECT PROGRESS MILESTONE CERTIFICATE 45
E. PROJECT PROGRESS REPORT 46
3 of 104
I. PROJECT INTEGRATION
MANAGEMENT
4 of 104
1. PROJECT CHARTER
5 of 104
PROJECT CHARTER
Document No.:
Project Number :
6 of 104
(AIMMS) & Documentation
Project Funding
Php 203,000.00
Project Team
7 of 104
2. ASSUMPTION LOG
8 of 104
ASSUMPTION LOG
Document No.:
Proje Proje
Clarence S.
ct ct
Numb : Mana : Ordonia/Janu
V. Peralta
er ger
Proje
Arduino based Water Irrigation
ct : Monitoring System
Title
9 of 104
10 of 104
3. PROJECT MANAGEMENT PLAN
Document No.:
Clarence Ordonia
Project Number : 2022-1 Project Manager :
Janu Peralta
11 of 104
Project Description - Irrigation of plants requires a large amount of human resources and
considered as one of the most time-consuming activity in farming
which has to be done in a practical amount of time. With the help of
modern technology, the number of workers involve and the time
required was reduced. Since the control and management of the
system is only limited to selected people, the monitoring is
questioned. There are still wasted water since the method used in
supplying is mass irrigation method and sometimes the amount of
water given exceeds the needs of the plants.
- The project is to develop and evaluate an Arduino-based irrigation
monitoring system. More specifically, it aimed to assemble an
Arduino-based irrigation monitoring system and to calibrate the
measuring device of the system in the field. It also aimed to
evaluate the accuracy of an automated measuring device for depth
of water of an irrigation turnout using a sensor and provide data
and information through SMS service and to monitor the opening
and closing of turnout gate and provide the information through
SMS service.
OUT OF SCOPE:
- Due to signal limit, service provider should be considered.
- For further study, the system can automate the opening and closing
of the water gate using a motor.
- The system can also be modified as solar powered.
12 of 104
Requirements During the early planning stages of the project, the Project Manager shall
Management Plan determine, document and manage stakeholder needs and requirements to
meet the project objectives. Requirements may include conditions or
capabilities that are required to be present in the project’s end-product, to
satisfy an agreement or other formally imposed specification. These
requirements may include the quantified and documented needs and
expectations of the sponsor, customer and other stakeholders.
Schedule The schedule includes project functions, activities, and tasks, and the
Management Plan required milestone dates. Project schedule will be published together with
other documents to be followed and reviewed regularly by all team
members. Project manager is responsible to monitor the project schedule,
regularly update it and input all changes
Cost Management The Cost Management Plan establishes the activities and criteria for
Plan planning, structuring, and controlling project costs. Cost estimating and
cost controls are the most important evaluation and control items for State
projects. Actual costs and cost variances must be reported regularly to
oversight committees and project sponsors. Any cost change over five
percent requires project steering committee approval.
Quality Quality Control Manager will be assigned by the Project Manager. QA will
Management Plan ensure that the application functions per the documentation descriptions.
Any deviations from the documentation will be submitted to application
development for review or correction. Any bugs or suggestions submitted
to QA will be reviewed for feasibility, accuracy, and usability. They will
determine if the submission should be elevated to the application
development for correction or implementation. QA will also test all changes
made by the Lead Developer prior to submitting the updated app. Software
Lead Developer will receive submissions to improve or correct the software
from the Quality Control Manager. They will be responsible for
implementing changes to the software per the request of QA. They will
also be responsible for keeping the application up to date and ensuring
that the byte code remains compatible with the devices .
Resource The project manager will be in charge of allocating project work. Any
Management Plan
complaints with their performance will be brought up with their direct
supervisor or Team Lead. Project team members will update the project
management on project progress. The project manager and direct
supervisor, in collaboration with the resource manager, will resolve
conflicts in task priorities.
Communications Kick off meeting to introduce the project to the project team
Management Plan
Team meetings or conference call to review status of the project. Discuss
and develop technical design solutions. Report the status of the project
including activities, progress costs and issues. To review the overall
project issues, lesson learned, corrective actions.
13 of 104
Communications can be through meetings, conference call and emails.
Risk Management The team will conduct risk analysis and management throughout the
Plan application development process. Areas of the application development
project that involve potential technical, budget, or schedule risks will be
identified, analyzed and prioritized. Some of the risks that need to be taken
into consideration include any other application in the market that provides
the same function as the product being developed, time, database
interface issues, security and compatibility.
Procurement During the planning stages of the project, the Project Manager shall
Management Plan document project procurement approaches and decisions, as well as
identified potential sellers, taking into consideration the influence of
procurement activities on the project schedule and any make-or-buy
decisions to be made.
For the project, the whole development of the proposed Arduino based
Water Irrigation Management System shall be done in-house, while the
hardware materials that are required to be procured externally
Project Manager
Project
Management
Office
14 of 104
II. PROJECT SCOPE MANAGEMENT
15 of 104
16 of 104
1. SCOPE MANAGEMENT PLAN
Document No.:
17 of 104
Janu Peralta
I. INTRODUCTION
This document serves as the Scope Management Plan for the project “Arduino based Water
Irrigation Monitoring System”. It aims to describe how the scope is defined, developed, monitored,
controlled and validated throughout the project life cycle.
18 of 104
The Project Manager shall engage the support of the Project Team in planning and developing a
Work Breakdown Structure that will serve as a framework of the required final deliverable.
V. SCOPE VALIDATION
Each deliverable or progress milestone shall be validated or verified against the initial scope
baseline, and formally accepted and signed off by the appropriate authority using the Project
Progress Milestone Certificate.
Deliverables and project milestones are outlined in the Project Scope Statement.
VI. ANNEX
Project Manager
Project
Management
Office
Project Sponsor
19 of 104
Document Release Date:
20 of 104
2. REQUIREMENTS MANAGEMENT
PLAN
21 of 104
REQUIREMENTS MANAGEMENT PLAN
Clarence Ordonia
Project Number : 2022-1 Project Manager :
Janu Peralta
Project Title : Arduino based Water Irrigation Monitoring System
I. INTRODUCTION
This document serves as the Scope Management Plan for the project “Arduino based Water
Irrigation Monitoring System”. It aims to describe how the scope is defined, developed, monitored,
controlled and validated throughout the project life cycle.
II. REQUIREMENTS DEFINITION
During the early planning stages of the project, the Project Manager shall determine, document
and manage stakeholder needs and requirements to meet the project objectives. Requirements may
include conditions or capabilities that are required to be present in the project’s end-product, to
satisfy an agreement or other formally imposed specification. These requirements may include the
quantified and documented needs and expectations of the sponsor, customer and other
stakeholders.
The Project Manager shall then prepare the following documents:
1. Requirements Documentation – describe stakeholders’ individual needs and requirements
2. Requirements Traceability Matrix – grid that links product requirements to their respective
deliverables.
The above-mentioned documents shall be the tools for identification, analysis, documentation
and management of the project requirements to meet objectives.
22 of 104
V. SCOPE VALIDATION
Scope validation is primarily concerned with acceptance of the deliverables. The Requirements
Documentation, Requirements Traceability Matrix, and Scope Baseline shall be used when checking
against the deliverables resulting from the project. The mentioned documents shall be compared to
the actual results as basis for acceptance.
23 of 104
3. REQUIREMENTS DOCUMENTATION
24 of 104
REQUIREMENTS DOCUMENTATION
3 Project Team To develop and evaluate an Arduino-based irrigation monitoring system. NEED
1 of 104
Prepared by: Signature
Project Manager Clarence S. Ordonia CO
2 of 104
4. REQUIREMENTS TRACEABILITY
MATRIX
1 of 104
5. PROJECT SCOPE STATEMENT
2 of 104
PROJECT SCOPE STATEMENT
Clarence Ordonia
Project Number : 2022-1 Project Manager :
Janu Peralta
Project Title : Arduino based Water Irrigation Monitoring System
Project Description - Irrigation of plants requires a large amount of human resources and
considered as one of the most time-consuming activity in farming
which has to be done in a practical amount of time. With the help of
modern technology, the number of workers involve and the time
required was reduced. Since the control and management of the
system is only limited to selected people, the monitoring is
questioned. There are still wasted water since the method used in
supplying is mass irrigation method and sometimes the amount of
water given exceeds the needs of the plants.
- The project is to develop and evaluate an Arduino-based irrigation
monitoring system. More specifically, it aimed to assemble an
Arduino-based irrigation monitoring system and to calibrate the
measuring device of the system in the field. It also aimed to
evaluate the accuracy of an automated measuring device for depth
of water of an irrigation turnout using a sensor and provide data
and information through SMS service and to monitor the opening
and closing of turnout gate and provide the information through
SMS service.
Key Objectives This project aims to develop and evaluate an Arduino-based
irrigation monitoring system.
Specifically, the study aims to:
- To assemble an Arduino-based irrigation monitoring system;
- To calibrate the measuring device of the system under laboratory
condition;
- To evaluate the accuracy of an automated measuring device for
depth of water of an irrigation turnout using a sensor and provide
data and information through SMS service;
- To monitor the opening and closing of turnout gate and provide the
information through SMS service.
-
Scope Description - The “Arduino-Based Irrigation Monitoring System” is aimed to
produce a notification device that helps the operations officer to
manage the delivery of water by following the proper scheduling.
With this device the operations officer will receive text alert
regarding the water level and discharge and the closing and
opening of the water gate. This project can also be used in any
3 of 104
water reservoir system but there will be some necessary changes
required like the change of the mobile number which receives the
notification alert regarding the depth of the irrigation canal and
discharge of the water and whether the water gate is close or open.
Project - Design of the Arduino-based Irrigation Monitoring System
Deliverables - Arduino Micro-controller and Accessories (Cellular signal, MCU,
etc.)
- Arduino-based Irrigation Measuring and Monitoring System
(AIMMS) & Documentation
Assumptions - A full project team will be available to see the project through the
full life cycle.
The Project Team will communicate regularly as outlined in the
Communications Management Plan.
Constraints - No face-to-face meetings shall be conducted, as compliance and
support to IATF’s community quarantine and health protocols in
response to the COVID-19 pandemic.
4 of 104
6. SCOPE BASELINE
5 of 104
SCOPE BASELINE
Document No.:
Date Last Modified:
Clarence Ordonia
Project Number : 2022-1 Project Manager :
Janu Peralta
Project Title : Arduino based Water Irrigation Monitoring System
I. INTRODUCTION
This document shall serve as the approved version of the project’s scope statement, Work
Breakdown Structure (WBS), and its associated WBS dictionary. It shall be used as the basis for
comparison with the project’s actual progress status.
6 of 104
Schematic Diagram of the System
WATER CANAL
AIMS
Operator
7 of 104
Schematic Diagram of how the AIMS sends the data.
8 of 104
Fig.1. Work Breakdown Structure (WBS)
WORK BREAKDOWN STRUCTURE (WBS) DICTIONARY
WBS WBS Responsibl Acceptance Start End
WBS Name WBS Description Deliverable Budget
Level Code e Person Criteria Date Date
9 of 104
Prepared by: Signature
Project Manager
Project
Management
Office
Project Sponsor
2 of 104
1. SCHEDULE MANAGEMENT PLAN
3 of 104
SCHEDULE MANAGEMENT PLAN
Document No.:
Date Last Modified:
INTRODUCTION
The purpose of the schedule management plan is to define the approach the project team will use in
creating the project schedule. This plan also includes how the team will monitor the project schedule
and manage changes after the baseline schedule has been approved. This includes identifying,
analyzing, documenting, prioritizing, approving or rejecting, and publishing all schedule-related
changes.
Project schedules will be created using MS Project starting with the deliverables identified in the
project’s Work Breakdown Structure (WBS). Activity definition will identify the specific work
packages which must be performed to complete each deliverable. Activity sequencing will be used
to determine the order of work packages and assign relationships between project activities. Activity
duration estimating will be used to calculate the number of work periods required to complete work
packages. Resource estimating will be used to assign resources to work packages in order to
complete schedule development.
Once a preliminary schedule has been developed, it will be reviewed by the project team and any
resources tentatively assigned to project tasks. The project team and resources must agree to the
proposed work package assignments, durations, and schedule. Once this is achieved the project
sponsor will review and approve the schedule and it will then be baselined.
The project manager will be responsible for facilitating work package definition, sequencing, and
estimating duration and resources with the project team. The project manager will also create the
project schedule using MS Project 2007 and validate the schedule with the project team,
stakeholders, and the project sponsor. The project manager will obtain schedule approval from the
project sponsor and baseline the schedule.
4 of 104
The project team is responsible for participating in work package definition, sequencing, and
duration and resource estimating. The project team will also review and validate the proposed
schedule and perform assigned activities once the schedule is approved. The project sponsor will
participate in reviews of the proposed schedule and approve the final schedule before it is baselined.
The project stakeholders will participate in reviews of the proposed schedule and assist in its
validation.
ACTIVITIES
The project starts on Feb 10, 2021 and ends on Dec 30, 2022. It has four phases: planning,
development, testing and deployment. The application is divided into three modules:
customer, service provider and admin.
Feb Mar Apr May June July Aug Sept Oct Nov Dec
2022 2022 2022 2022 2022 2022 2022 2022 2022 2022 2022
Planning
Design of the
Arduino-based
Irrigation Monitoring
System
Development of the
Arduino Micro-
controller and
Accessories
(Cellular signal,
MCU, etc.)
Testing
Deployment
5 of 104
IV. PROJECT COST MANAGEMENT
6 of 104
1. COST MANAGEMENT PLAN
7 of 104
COST MANAGEMENT PLAN
Document No.:
INTRODUCTION
The purpose of this Cost Management Plan is to define the methodology by which costs associated
with Arduino based Water Irrigation Monitoring System will be managed throughout the project
lifecycle. To ensure the successful completion of the project within the allotted budget, this plan sets
the format and standards by which the project costs are measured, reported and controlled. Several
cost components are associated with this project. Metrics, cost variance considerations, and
reporting activities will be outlined in this plan. To complete this project successfully, all key project
members and stakeholders must adhere to and work within this Cost Management Plan and the
overall project plan it supports.
The Cost Management Plan establishes the activities and criteria for planning, structuring, and
controlling project costs. Cost estimating and cost controls are the most important evaluation and
control items for State projects. Actual costs and cost variances must be reported regularly to
8 of 104
oversight committees and project sponsors. Any cost change over five percent requires project
steering committee approval.
COST ESTIMATION
The Cost Management Plan for Arduino based Water Irrigation Monitoring System documents the
methods to be used to manage and control the many internal and external cost components.
Metrics and variance analysis must be applied to these cost components throughout the project
lifecycle for tracking, re-estimating and adjusting the project budget if needed. These cost
components include:
A ‘bottom-up’ approach will be used for preparing a detailed cost estimate of each cost component
involved with each project activity. Costs estimates will be prepared using the best information
available at the time of estimation. The basis for the estimate must be fully documented so that if
better information becomes available at a later time in the project, the cost estimate can be adjusted.
BUDGET DETERMINATION
Once the needs have been determined, the project team will finalize the resource and staffing
requirements necessary for the successful completion of the project. The Project Manager will
complete the Work Breakdown Structure (WBS) respectively. Control accounts and staff labor
categories will be created in each WBS element. Based on the labor costs and planned duration of
each WBS element, an estimate will be determined. WBS element costs will then be totaled and
verified against the allotted project budget. Once the project budget is approved, the Project
Manager will compare the allocation for each WBS element against the overall budget and adjust
allocations as necessary to comply with the project budget. Once all allocations have been
reviewed and approved by the Project Manager, the project budget will be baselined. The project
budget baseline may only be changed with authorization by the Project Sponsor.
9 of 104
Document Release Date:
10 of 104
2. ESTIMATED COSTS
ESTIMATED COSTS
Document No.:
11 of 104
Project Title : Arduino based Water Irrigation Monitoring System
Project Sponsor
13 of 104
3. ACTUAL COSTS
14 of 104
V. PROJECT QUALITY MANAGEMENT
15 of 104
1. QUALITY MANAGEMENT PLAN
16 of 104
QUALITY MANAGEMENT PLAN
Document No.:
Clarence Ordonia
Project Number : Project Manager :
Janu Peralta
I. INTRODUCTION
This document helps guide the Program Manager (PM) and project personnel of Arduino based
Water Irrigation Monitoring System to execute quality management and quality assurance activities
for Agriculture of MMSU.
Delivery on time Baseline schedule +/- change items versus actual dates.
17 of 104
Quality control Milestones Owner
process
Project Developers Comply with quality standards and participate in quality control
activities.
Testing including User Acceptance Part of the PMO project audit process
Testing
VII. ANNEX
18 of 104
Prepared by: Signature
Clarence Ordonia CO
Project Manager
Janu Peralta JP
Project
Management
Office
Project Sponsor
___________, 2022
19 of 104
2. QUALITY METRICS
20 of 104
QUALITY METRICS
Document No.:
Date Last Modified:
Proje Proje Clarence
ct ct Ordonia
Numb : Mana :
er ger Janu Peralta
Proje
Arduino based Water Irrigation
ct : Monitoring System
Title
1.1 1.3.2 Software Largest System speed Test Pending Project developer
average speed Contentful Paint: Insights team will
load time less than 2.5s measure at 1
Cumulative month post
Layout Shift: less launch
than 0.1s
2.1 1.5.2 Security Number of Critical Security or Test Pending Project developer
Vulnerabilities Vulnerabilities team will
scanners tools
measure at 1
month post
launch
3.1 1.5.2 User Defects found Defects found Test Pending Defect tracking
Acceptance during UAT: during UAT will template
be logged on
Testing 0-5 - Medium
the Defect
6-10 - High Tracking Log.
More than 11 - The project
Critical manager will
use it to
calculate the
number of
defects that fall
into each
category.
21 of 104
Prepared by: Signature
Clarence Ordonia CO
Project Manager
Janu Peralta JP
Project
Management
Office
Project Sponsor
22 of 104
VI. PROJECT RESOURCE
MANAGEMENT
23 of 104
1. RESOURCE MANAGEMENT PLAN
24 of 104
RESOURCE MANAGEMENT PLAN
Document No.:
I. INTRODUCTION
This document helps guide how project resources of Serbi-Shop should be categorized,
allocated, managed, and released.
II. TEAM IDENTIFICATION
Requirement Skills needed Role
Develop a new Arduino Uno which Prior experience Arduino Uno, Project Developer
will be used as the micro- Ultrasonic sensors & coding
controlling device languages
Develop, implement, and maintain a Excellent verbal and written skill, QA Tester
system of quality and reliability test Critical thinking, Strong IT skills,
for the organization's products Ability to use logic and reasoning to
and/or development processes identify the strengths and
weaknesses of IT systems.
25 of 104
III. TEAM ACQUISITION
Role Person or team if Acquisition
known
26 of 104
VI. ROLES AND RESPONSIBILITIES
Role Authority Responsibility Qualifications Competencies
Procurement Manage the Ensure that the BS degree in supply Proven working
Manager company’s supply business chain management, experience as a
of products and purchases logistics or business Procurement
services (goods and administration Manager,
services) will Procurement
best help Officer or Head of
achieve the Procurement
goal
27 of 104
processes
Team Player Award - intended to recognize and encourage collaboration. This employee
award communicates the expectations for the team and rewards those who meet them.
Customer service award - for those team members who have demonstrated exceptional
skills in client communication and relations. Keeping customers satisfied is no easy task,
but delivering a great customer experience benefits everyone involved.
28 of 104
- Equipment will be purchased through the pre-approved supplier list.
XI. ANNEX
Project Manager
Project
Management
Office
Project Sponsor
29 of 104
VII. PROJECT COMMUNICATIONS
MANAGEMENT
30 of 104
1. COMMUNICATIONS MANAGEMENT
PLAN
31 of 104
COMMUNICATIONS MANAGEMENT PLAN
Document No.:
Date Last
Modified:
Clarence Ordonia
Project Number : Project Manager :
Janu Peralta
Project Title : Arduino based Water Irrigation Monitoring System
Item/ Purpose Method/ Frequency Audience Person- Deliverable Format Distribu Archiving
Event Medium In-Charge tion
Kick-off Introduce the project Meeting/ Once, at the Project Project - Agenda Soft copy Email to Project
meeting to the nominated Conference beginning of sponsor, Manager - Meeting minutes Audience website or
project team Call the project Project team, SharePoint
Stakeholders
Project Review status of the Meeting/ Weekly Project team Project - Agenda Soft copy Email to Project
team project Conference Manager - Meeting minutes Audience website or
meetings Call - Project Schedule SharePoint
Technical Discuss & develop Meeting/ As needed Project Technical - Agenda Soft copy Email to Project
design technical design Conference technical staff Lead - Meeting minutes Audience website or
meetings solutions Call & PM SharePoint
Project Report the status of Email Monthly Project Project - Project Progress Soft copy Email to Project
status the project including (end of the sponsor, Manager Report Audience website or
reports activities, progress month) Project team, - Project Schedule SharePoint
costs and issues Stakeholders
Project Review the overall Meeting/ Once, at the Project Project - Agenda Soft copy Email to Project
closure project issues, Conference end of the sponsor, Manager - Meeting minutes Audience website or
meeting lessons learned, Call project Project team, - Lessons Learned SharePoint
corrective actions Stakeholders Register
Key Guidelines:
Authorizing Authority : The Project Manager is authorized to release communications as deemed appropriate.
Timeframe for Distribution : Within 3 days after Communications Item/ Event
Email Addresses : Only official email addresses authorized for the project shall be used.
Recipients of : All communications recipients to maintain confidentiality of project details.
Communications
Language : Meetings – common language among all persons involved may be used in verbal
communications.
Deliverables – shall be constructed in the English language.
Updates : The Project Manager shall update this document as needed.
Others : The Project Team may communicate among each other via other media such as voice calls, or
other text messaging applications to discuss minor details on the project for follow-up or
clarifications, using any language they are comfortable with.
Templates:
Annex A - Agenda/ Meeting Minutes
Annex B - Project Progress Report
Annex C - Lessons Learned Register
2 of 104
Document Release Date:
3 of 104
VIII. PROJECT RISK MANAGEMENT
1. RISK MANAGEMENT PLAN
2 of 104
RISK MANAGEMENT PLAN
Document No.:
Date Last Modified:
Clarence Ordonia
Project Number : Project Manager :
Janu Peralta
Project Title : Arduino based Water Irrigation Monitoring System
I. INTRODUCTION
This document serves as the Risk Management Plan for the project “Arduino based Water
Irrigation Monitoring System”. It aims to foresee risks in the development of the Arduino based
Water Irrigation Monitoring System, their estimated impacts and severity, and the appropriate risk
responses.
The risk management plan is partially based on input from the Scope Management Plan, Cost
Management Plan, Schedule Management Plan, Quality Management Plan and Project Charter.
3 of 104
III. RISK REGISTER
Limited Arduino kit for the Developers of the system Major Unlikely
used of system are would not be able to
sustain a large amount of
the area needed for the
irrigation
4 of 104
IX. PROJECT PROCUREMENT
MANAGEMENT
5 of 104
1. PROCUREMENT MANAGEMENT
PLAN
6 of 104
PROCUREMENT MANAGEMENT PLAN
Document No.:
Date Last Modified:
VI. INTRODUCTION
This document serves as the Procurement Management Plan for the project “Arduino based
Water Irrigation Monitoring System”. It aims to describe the activities to be undertaken during the
procurement process, and how these activities will be aligned with the project schedule.
7 of 104
8 of 104
B. SOURCE SELECTION CRITERIA
To ensure that there is balance between the quality and cost of the required product/ service to
be procured, the following criteria shall be used as basis when sourcing:
1. Capability and capacity – 50%
2. Adequacy of inclusive services – 30%
3. Product cost – 20%
9 of 104
Prepared by: Signature
Project Manager
10 of 104
X. PROJECT STAKEHOLDER
MANAGEMENT
11 of 104
1. STAKEHOLDER REGISTER
12 of 104
TAKEHOLDER REGISTER
Document No.:
Clarence Ordonia
Project Number : Project Manager :
Janu Peralta
Service
Project
Providers, End Users External Influence decision making H L
Customers
Customers
Legend:
H High
M Medium
L Low
Clarence Ordonia CO
Project Manager
Janu Peralta JP
Project Sponsor
2 of 104
2. STAKEHOLDER ENGAGEMENT
MATRIX
STAKEHOLDER ENGAGEMENT MATRIX
Document No.:
Clarence Ordonia
Project Number : Project Manager :
Janu Peralta
Project Title : Arduino based Water Irrigation Monitoring System
Project Sponsor CD
Quality Manager D C
Project Manager C D
Procurement Manager C D
Project Developer CD
Tester C D
Project Customers C D
Legend:
D Desired Level of Engagement
Clarence Ordonia CO
Project Manager
Janu Peralta JP
Project
Management
Office
Project Sponsor
2 of 104
3 of 104
XI. APPENDICES
1. PROJECT DOCUMENTS
2 of 104
A. PROJECT PROGRESS MILESTONE
CERTIFICATE
3 of 104
B. MEETING MINUTES
4 of 104
C. CHANGE REQUESTS
5 of 104
D. PROGRESS REPORTS
6 of 104
2. FORMS & TEMPLATES
7 of 104
A. AGENDA/ MEETING MINUTES
8 of 104
B. CHANGE REQUEST FORM
9 of 104
C. LESSONS LEARNED REGISTER
10 of 104
D. PROJECT PROGRESS MILESTONE
CERTIFICATE
11 of 104
E. PROJECT PROGRESS REPORT
12 of 104