1.2.1.

15 Staffing Management Plan

The Learning Management Project will consist of a projectized organizational
structure. Staffing requirements for the Learning Management Project include the
following:
Project Manager (1 position) – is responsible for all the management and for the
Learning Management System. The Project Manager is responsible for planning,
tracking, reporting, performance evaluations, interface with appropriate IT
resources and support external stakeholders.
Programmer (1 position) – responsible for coding, test code, editing source-code,
troubleshooting system errors and programming for the Learning Management
Project. The coding and programming tasks will be reviewed by the Senior
Programmer prior in implementation. The programmer also includes assisting with
risk identification, determining impacts of change requests and status reporting. The
Programmer will be managed by the Project Manager and feedback will be provided
to the functional manager for performance evaluations by the Project Manager and
Senior Programmer.
Senior Quality Specialist (1 position) – responsible for assisting the Project Manager
in creating quality control and assurance standards. The Senior Quality Specialist is
also responsible for the development and implementation of inspection activities.
Testing Specialist (1 position) – responsible for helping establish testing
specifications for the Event Management System Project with the assistance of the
Project Manager and Programmers. Responsible in testing schedule, arranges for
use of testing facilities, ensures integrity of testing environment and materials. The
Testing Specialist will be managed by the Project Manager who will also provide
feedback to the functional manager for performance evaluations.
The Project Manager will negotiate with all necessary TSI functional managers in
order to identify and assign resources for the Event Management System Project. All
resources must be approved by the appropriate functional manager before the
resource may begin any project work. The project team will not be co-located for
this project and all resources will remain in their current workspace.
1.2.1.16 Cost Baseline
The cost baseline for the Event Management System Project includes all budgeted
costs for the successful completion of the project.

Project Phase Budgeted Total Comments

Planning ₱360,710 Includes work hours for all project team
members for gathering requirements and
planning project
Design ₱172,000 Includes work hours for all project team
members for work on Learning Management
System conceptual design
Coding ₱293,000 Includes all work hours for coding of Learning
Management System Project
Testing ₱153,000 Includes all work hours for testing (including
beta testing) of Learning Management System
software
Transition and Closeout ₱1,293,250 Includes all work hours for transition to
operations and project closeout
1.2.1.17 Quality Baseline
The Event Management System Project must meet the quality standards established
in the quality baseline. The quality baseline assists in monitoring that the
accumulated cost of the project. It provides the Quality design for the module of the
Event Management System Project. The software must meet or exceed the quality
baseline values in order to achieve success.

Item Acceptable Level Comments

Compatibility There are accepted issue associated with Compatible for desktop
running software with compatible browser
applications.
Supporting Documentation Less than 1% failure rate in testing new The supporting document from
users to run setup and execute software reliable source.
functionality.
Deliverables The project must be on time for deadline The deadline is strictly
and timeline. observed.

1.2.2 Risk Management Plan

1.2.2.1 Introduction
By Implementing Event Management System The Team are searching for
some risk than can cause problem to the event and we make a plan to
prevent some risk and to ensure the safety of the event to any future
problems and we make this plan to avoid those risks and to establish some
strategies for the safetiness of everyone in the event.
1.2.2.2 Top Three Risk
These are some of the following risks that we uncover that may harm our EMS. Our
team have discussed on what appropriate measure to avoid of any necessary risk
and to prevent some problems that can affect our EMS project.

-Natural Disaster such as typhoon, earthquake etc

The event management system team are aware that the event can experience this
kind of risk and we make this plan to prevent natural disaster on the day of the
event.

-Physical Activity that can cause injury

Our team have some personnel to monitor and to guide some students in the event
and to prevent some physical injury during the events.

-Unauthorized person that can cause mess with our EMS

The Event Management System Team are surely secured the event. Our team make
some security policies. The Event will be monitored 24/7 by the personnel to ensure
the safetiness of everyone in the day of the event
1.2.2.3 Risk Management Approach
The Event Management System Team will ensure the safety and peace of the event.
We make some plans to prevent some problems and the event management teams
consist of personnel that can ensure the safetiness of everyone involve in the event.

1.2.2.4 Risk Qualification and Prioritization

In order to determine the severity of the risks identified by the team, a probability
and impact factor was assigned to each risk. This process allowed the project
manager to prioritize risks based upon the effect they may have on the event. Our
team deploy some personnel to ensure the safetiness of everyone to the event.

1.2.2.5 Risk Monitoring

The Event Management System team make the security policies for the event. And
we deploy some personnels to monitor and ensure the security of the students. Our
team will be noting some future problems to make sure the positive results of the
event. Also, Our team will plan a meeting on discussing the status of the risk of the event
and the team also will the responsible to ensure the threats of the risks will be fixed.

1.2.2.6 Risk Mitigation and Avoidance

The Event Management System Team responses to the risk that being identified and
monitored and to communicate to the Project Manager to determine the impact of each
risk, and also the team will also develop the mitigation and avoidance strategies. The risks
that being added to the project plan will be ensure that they monitored and identified in
time to time and to respond clearly. The risk of the Event Management System will be
monitored and managed the Schedule and scope of the event. The risks that being identified
are going to examine and evaluated to determine if it will affect the event. The Team will
assist the Project Manager to respond on each risk that to be ensured the completion of the
project.

1.2.2.7 Risk Register

The Risk Register for this project is used to record of all identified risks, their probability and
potential impact of the project, mitigation strategy, the likelihood and consequences of risk
occurs. The project was created through the initial project risk brainstorming session led by
project manager. During the meeting, the project member identified and categorized each
risk of the project. Also, the team assigned each risk a score based on the probability of it
occurring potential impact. The Risk Register also contains mitigation strategy for each risk
as well as the likely risk occur.

1.2.3 Scope Management Plan

1.2.3.1 Introduction
The Scope Management Plan will be provided by the scope framework for this
project. The approach for the scope management plan are the deliverables, scope,
project and resource requirements, potential risks and implementation overview
verification and control measures scope change control and the project’s work
breakdown structure. The project should pertain to the project’s scope and adhere
to the Scope Management Plan.
The project’s design, programming, and testing the product which will be used to
improve various financial processes. This will include the design of the software,
programming, coding and testing of the software. There will be no external
resources can be expected for this project.

1.2.3.2 Scope Management Approach

The one who is responsible and have the authority over this project is our Project
Manager. The Scope Management Plan for this project will be defined by the Scope
Statement, Work Breakdown Structure (WBS) and WBS Dictionary. Once approved by the
Project Manager, Sponsor and Stakeholders we can begin to measure the project scope that
will include such as quality checklist and work performance measurements. The changes
proposed by the Sponsor and Stakeholders it can only be permitted to change by the Project
Manager and any members involved in this project. The request will be given to the Project
Manager to review if the request can be initiated within the scope. Once approve by the
request the Project manager will now request to the Change Control Board and Project
Sponsor for their approval. Once approved the Project Manager will update all project
documents and communicate the scope change to all stakeholders. The Project Sponsor will
be the one responsible for the acceptance of the final project
1.2.3.3 Roles and Responsibilities
The Project Manager, Sponsor and team will all play key roles in managing the scope
of this project. As such, the project sponsor, manager, and team members must be
aware of their responsibilities in order to ensure that work performed on the project
is within the established scope throughout the entire duration of the project. The
table below defines the roles and responsibilities for the scope management of this
project.

Name Role Responsibilities

Ronald Roldan Jr. Sponsor - Provide support for the project
- Approve or deny scope change requests as
appropriate
- Evaluate need for scope change requests
- Accept project deliverables

Jennylyn Dotillos Project Manager - Manages the scope management system and
Robante project team
- Measure and verify project scope
- Facilitate scope change requests
- Facilitate impact assessments of scope change
requests
- Organize and facilitate scheduled change
control meetings
- Communicate outcomes of scope change
requests
- Update project documents upon approval of all
scope changes

Richfford Mark Team Member - Measure and verify project scope

Magno - Validate scope change requests
- Participate in impact assessments of scope
change requests

Daryl Jorolan Team Member - Participate in defining change resolutions

- Evaluate the need for scope changes and
communicate them to the project manager as
necessary

John Keeno Rivera Team Member - Participate in defining change resolutions

- Evaluate the need for scope changes and
communicate them to the project manager as
necessary

Allan Francisco Team Member - Communicate outcomes of scope change

requests to team
- Facilitate team level change review process

1.2.3.4 Scope and Definition

The scope for this project was defined through a comprehensive requirements
process. First, a thorough analysis was performed on the school’s current software
applications based on students and user feedback. From this information, the
project team developed the project requirements documentation, the requirements
management plan, and the requirements traceability matrix for what the new
software application must accomplish.
The project description and deliverables were developed based on the requirements
collection process and input from subject experts in software design, technical
support, programming and software applications. This process of expert judgement
provided feedback on the most effective ways to meet the original requirements of
providing a new software platform from which the school or university can improve
traditional educational institutions.

1.2.3.5 Project Scope Statement

This Project Scope State provides the detailed information of the Project
Constraints, Project Deliverables and the Project Assumptions. This Scope Statement
includes all the requirements that being outlined in the Learning Management
System and also to eliminate unnecessary works in the Project Scope Statement.
This Project will be including the designing, testing and executing the system. The
Learning Management System deliverables is being completed as the software
application that being executed throughout the project. This software application
has been tested successfully and accomplished by the help of our system
programmer. The Project Constraints of this system is being provided to have better,
faster and higher-quality services to the students and also the funds of the resources
that being used to be able to repair the system with the time that they spend
working and with the tools that being used of hardware/software. The Project
Assumptions of this project are the support of the Project Manager to assists his/her
Project Team to finish and completed all the tasks and also the resources that being
used through the whole project. This Project will not be successfully complete
without the Project Sponsor to finishing and executing it successfully.

1.2.3.6 WBS
This project will manage the work required to complete this project. And also, allow
the Project Manager to manage the project’s scope as the project team works on
the tasks necessary for project completion. The project is broken down into three
phases: the design phase; the programming phase; and the testing phase. Each of
these phases is then subdivided further down to work packages which will require
no more than 40 hours of work and no less than 4 hours of work (see WBS structure
below).

1.2.3.7 Scope Verification

As this project progresses the Project Manager will verify in term project
deliverables against the original scope as defined in the scope statement, WBS and
WBS Dictionary where the deliverables of the work breakdown structure are
located. Once the Project Manager verifies that the scope meets the requirements
defined in the project plan, the Project Manager and Project Sponsor will meet for
formal acceptance of the deliverable. During this meeting the Project Manager will
present the deliverable to the Project Sponsor for formal acceptance. The Project
Sponsor will accept the deliverable by signing a project deliverable acceptance
document. This will ensure that project work remains within the scope of the project
on a consistent basis throughout the life of the project.

1.2.3.8 Scope Control

The Project Manager and the project team will work together to control of the scope
of the project. The project team will ensure that they perform only the work
described in the WBS dictionary and generate the defined deliverables for each WBS
element. The Project Manager will oversee the project team and the progression of
the project to ensure that this scope control process if followed.