Table of Contents 10. WORK BREAKDOWN STRUCTURE 10.1 Introduction 10.2 Outline View 10.3 Hierarchical Structure 10.4 Tabular View 10.5 Tree Structure View 10.6 WBS Dictionary 10.7 Glossary of Terms 11. HR MANAGEMENT PLAN 11.1 Introduction 11.2 Roles and Responsibilities 11.3 Project Organizational Charts 11.4 Staffing Management 12. QUALITY MANAGEMENT PLAN 12.1 Introduction 12.2 Quality Management Approach 12.3 Quality Requirements/Standards 12.4 Quality Assurance 12.5 Quality Control 12.6 Quality Control Measurements 13. RISK MANAGEMENT PLAN 13.1 Introduction 13.2 Top Three Risk Risk Management Approach 13.4 Risk Identification 13.5 Risk Qualification And Prioritization 13.6 Risk Monitoring 13.7 Risk Mitigation And Avoidance 13.8 Risk Register 15. PROCUREMENT MANAGEMENT PLAN 15.1 Introduction 15.2 Procurement Risks 15.3 Procurement Risk Management 15.4 Cost Determination 15.5 Procurement Constraints 15.6 Contract Approval Process 15.7 Decision Criteria 15.8 Performance Metrics for Procurement Activities 16. Implementation Plan 16.1 Executive Summary 16.2 Transition Approach 16.3 Workforce Transition 16.5 Workforce Exec During Transition 16.6 Property Transition Intellectual Property User Accounts and Passwords 16.7 Knowledge Transfer 16.8 Schedule 16.9 Handover and Acceptance 17 Change Management Plan 17.1 Introduction 17.2 Change Control Board 17.3 Roles and Responsibilities 14.4 Change Control Proces

The Work Breakdown Structure (WBS) is a hierarchical breakdown of the project deliverables into smaller, more manageable components. The WBS provides a framework for the team for organizing their project work and helps them to identify the activities needed to complete their project. The purpose of the WBS is to break down the project into manageable work packages that can be planned, monitored, and controlled. By breaking down the project into smaller components, it is easier for the team to estimate the effort required to complete each task, assign responsibilities to team members, and track progress against the project plan. It is an essential tool for project managers and provides a visual representation of the project scope and objectives. The WBS is a key component of the project management plan and is developed during the project's planning phase. The WBS helps the team to ensure that all project activities are accounted for, and nothing is overlooked or missed. Listed below are the project deliverables, project work, activities required to complete each deliverable and the resources needed to complete the project. Such as choosing a project client, choosing a consultant, creating all papers needed for the project, and the expected labor to cost.

The outline view for the work breakdown structure (WBS) of Fil-Chi Animal Clinic provides a straightforward and clear layout that is easy to understand. This layout is particularly useful during the development phase of the project as it enables the project team to make changes quickly and efficiently. The outline view displays the hierarchical structure of the WBS, which allows the project team to easily see the various levels of the project and how they relate to one another. With this view, the team can easily identify the major deliverables of the project and the sub-deliverables that contribute to the completion of each major deliverable. This helps ensure that the project team stays on track and is able to complete the project within the established timeline.

The hierarchical structure is an effective way to represent the Work Breakdown Structure (WBS) for the Fil-Chi Pet Record Management project. It shows the breakdown of the project into smaller, manageable parts, with each level representing a more detailed and specific set of activities. This structure allows for a clear understanding of the dependencies between different tasks and deliverables and enables the project team to track progress and identify any potential issues at an early stage.

The Tabular View shows the WBS for the Barangay South Signal Village Web App project, organized in a table format with four main categories: Planning, Analysis and Design, Development, and Implementation, with a fifth category for project closeout. Each category is broken down into subcategories and tasks, making it easier to track project progress and ensure timely completion of tasks.

The Tree Structure view provides an intuitive and easy-to-understand visual representation of the project's hierarchical structure, showing how each element contributes to the project as a whole

The WBS Dictionary contains all the details of the WBS which are necessary to successfully complete the project. Most importantly it contains a definition of each Work Package which can be thought of as a mini scope statement. Resources on the project will look at the WBS dictionary to determine the scope of the Work Package they've been assigned, so it's important to be clear when writing the definition. Most WBS dictionaries contain more information than we show in our sample. These things usually include Level of Effort, Cost Control Numbers, Resource Assignments, Responsibility Assignments - just to name a few.

Level of Effort:	Level of Effort (LOE) is how much work is required to complete a task.
WBS Code	A unique identifier assigned to each element in a Work Breakdown Structure for the purpose of designating the element’s hierarchical location within the WBS.
WBS Code	A unique identifier assigned to each element in a Work Breakdown Structure for the purpose of designating the element’s hierarchical location within the WBS.
Work Package:	A Work Package is a deliverable or work component at the lowest level of its WBS branch.
WBS Component:	A component of a WBS which is located at any level. It can be a Work Package or a WBS Element as there's no restriction on what a WBS Component is.
WBS Element:	A WBS Element is a single WBS component and its associated attributes located anywhere within a WBS. A WBS Element can contain work, or it can contain other WBS Elements or Work Packages.

The Human Resource Plan is important for managing a project team. It makes sure the right people with the right skills are in the right jobs at the right time. This plan helps organize who does what in the project and ensures everyone knows their tasks and responsibilities. The plan also encourages team members to communicate openly and work together. This way, they can share ideas and solve problems more effectively. By using the Human Resource Plan, the project manager can guide the team smoothly and keep the project on track. It helps everyone understand their roles and provides a clear guide for managing the team, leading to a successful project.

Project Manager

• He is responsible for overseeing the project and ensuring that it is completed on time.

Product Owner

• He is responsible for defining and prioritizing the project requirements and ensuring that the final product meets the needs of the clinic.

Scrum Master

• She is responsible for facilitating the agile development process and ensuring that the team is following the Scrum framework.

Scrum Team

• The Scrum Team is responsible for developing the project deliverables and working together with the rest of the team to ensure the success of the project. This includes understanding and adhering to the project's scope, identifying any scope-related risks or issues, and communicating these to the Project Manager and Scrum Master.

Documentation Manager 

• He is responsible for managing the project documentation and ensuring that it is complete and accurate.

Project Sponsor

• Provides executive support for the project.

Project organizational chart of Fil-Chi Animal Clinic Web Application provides a visual presentation of the project team and the relationship with their client. At the top of the organizational chart is the Product Sponsor, who provides resources and support for the project and makes major decisions. Directly under the Product Sponsor is the stakeholder who provides executive support for the project. Under the stakeholder is the Project Manager, responsible for overseeing the project from the planning phase to its conclusion. Reporting to the Project Manager is the Product Owner, who is tasked with maximizing the product's value and managing the product backlog; the Scrum Master, who facilitates the agile process, removes obstacles, and ensures the team adheres to its processes; and the Documentation Manager, who handles all documentation, ensuring all necessary information is accurately recorded, organized, and maintained.

The Fil-Chi Animal Clinic Web App Team's Staffing Plan will be closely monitored to ensure it works well. This plan explains how the team will find, manage, and release employees during the project.

• The project sponsor will make sure the right people are hired for the job, so each person has the right skills. Most of the team will be made up of people who already work for the clinic, and they will oversee making sure the web application runs smoothly.
• The team will provide training to each person who will use the web application, so they can use it effectively and avoid mistakes.
• The team will regularly check how each person is doing and what they have accomplished. This will help ensure the team is meeting the project's goals and requirements.

The project owner will regularly review the project's goals, scope, and requirements to make sure the staffing plan stays on track. This includes considering government rules about data privacy and security, as well as the specific needs of a government-owned web application.

The Quality Management Approach for the Fil-Chi Pet Record Management System will employ an Agile and Scrum methodology to ensure that the project consistently delivers high-quality outcomes that meet or exceed stakeholders' expectations. Throughout the course of the project, this method places a strong emphasis on iterative development and continual improvement to attain the highest possible quality. Every stage of the project will incorporate the Quality Management Approach, and all members of the team will actively participate in making sure that quality requirements are fulfilled. It will be based on the ideas of Agile and Scrum, with a focus on client's feedback, iterative development, and continuous improvement. The Fil-Chi Pet Record Management System aims to promote a culture of collaboration, flexibility, and continuous improvement by using the Agile and Scrum methodology as the quality management approach. This will allow the team to consistently deliver a high-quality web application that meets the needs and expectations of its users.

The Quality Management Approach for the Fil-Chi Pet Record Management project will employ an Agile and Scrum methodology to ensure that the project consistently delivers high-quality outcomes that meet or exceed stakeholders' expectations. This approach emphasizes iterative development, frequent customer collaboration, and continuous improvement to achieve optimal quality throughout the project's lifecycle. The following roles and responsibilities are defined within the quality management approach:

Role	Responsibilities
Project Manager	The project manager is in charge of making sure that the finished product satisfies the quality needs of the stakeholders by actively engaging in the agile and scrum processes, articulating a clear product vision, and setting priorities for tasks related to quality.
Documentation Manager	The Document Manager keeps accurate and current records of processes, standards, and procedures, which helps to support the quality management approach. They make sure that team members can readily access documentation, which encourages uniform comprehension and adherence to quality standards.
Scum Master	The Scrum Master will be responsible for promoting and enforcing the adherence to the Scrum framework. He will remove obstacles, foster teamwork, and make sure that the Agile development approach incorporates quality.
Project Sponsor	Provides executive support for the project.

The Quality Requirements/Standards for the Fil-Chi Pet Record Management project encompass both the product and process aspects, aiming to ensure the delivery of a high-quality web application. The project team will actively identify and document these requirements and standards, demonstrating compliance throughout the project lifecycle. Quality Requirements:

• Product Quality Standards:

1. To establish precise quality standards for the web application, the project team will analyze user needs, industry best practices, and customer expectations.
2. We will identify and record the functional requirements, performance expectations, usability standards, and security measures.
3. To guarantee that the finished product satisfies the required quality level, quality requirements will be matched with project objectives and stakeholders' expectations.

• Process Quality Standards:

1. In order to guarantee adherence to industry standards and best practices throughout the project lifecycle, the team will set up quality assurance systems and procedures.
2. To guarantee standardized and excellent development techniques, standards for documentation, code review procedures, testing protocols, and change management plans will be established.

Quality Assurance (QA) for the Fil-Chi Pet Record Management project will be rooted in Agile methodologies, promoting quality through iterative development, constant collaboration, and improvement.

• Establishing Quality Standards: In order to establish and record the project's quality standards in the Quality Management Plan, the project team will work with stakeholders. All parties involved will be informed of the quality standards.
• Compliance with Industry Standards: The project team will make sure that the Fil-Chi Pet Record Management System complies with all applicable industry standards, including those pertaining to data protection, security, and accessibility. Audits will be carried out on a regular basis to confirm adherence to these guidelines.
• Reporting and Enhancement: Stakeholders will get documented reports and communications regarding the outcomes of quality assurance audits and measurements.
• Reports will point out non-compliant sections, point out possible dangers, and suggest corrective measures.

Quality assurance metrics will be monitored closely, tracked, and reported on a regular basis to guarantee that the project yields a high-quality outcome. Any violation of these guidelines will result in an instant assessment and adjustment. To collect information on these characteristics, the application software will generate reports on a regular basis. Making sure the Fil-Chi Pet Record Management Web App satisfies the highest standards of quality is the aim. Using quality metrics, the project team will keep an eye on the project's progress and report back on it in reference to the quality standards.

The quality control process is an integral part of the development and maintenance of the Fil-Chi Pet Record Management Web App. It ensures that all aspects of the application meet the defined quality standards and requirements. The following quality control measures will be implemented:

• Establishing Quality Standards: Acceptable standards will be based on customer requirements, industry standards, and project objectives.
• Tracking and Documenting Outcomes: Utilize a bug tracking tool such as JIRA to record and handle errors found throughout testing.
• Evaluation of Performance: To guarantee dependability, periodically check the web application's uptime against the 99.9% goal uptime.
• Suggestions for Modifications: Perform usability testing sessions to discover pain areas and offer UI enhancements if users have trouble navigating the program.
• Documentation: Keep an up-to-date Quality Control Plan detailing the procedures for UAT, performance monitoring, and automated testing. After every testing phase, create and send thorough test reports to the appropriate parties.

The Agile and Scrum techniques will be employed to promote continuous inspection and modification throughout the project lifecycle for the project, which will adopt a transparent and collaborative approach to quality control. To guarantee that the product fulfills the standards and criteria, quality control measures will be made at each stage of the development process and documented on a shared, viewable platform, such as a project management tool, as opposed to a static spreadsheet or table. The following details will be on the platform:

• Measurement date
• Measurement type (e.g., QA testing, source code review, peer review, user story acceptance)
• The measurement's findings (such as passed/failed, the number of flaws discovered, and the percentage of code coverage)
• Requirements and standards for comparison
• Member of the team in charge of measuring
• Team member responsible for assessing the measurement results
• Taking any required corrective actions
• The date that the remedial measures were finished
• Team member in charge of carrying out corrective measures

The quality control measurements will be recorded and documented on a shared platform or project management tool to ensure accessibility and transparency. Dashboards like Trello's workspace will be utilized to provide real-time tracking and visualization of the quality control metrics, enabling the team to identify patterns, highlight problem areas, and take prompt action. Regular project reviews, such as sprint reviews will be conducted to review the quality control metrics and adjust the approach if needed. By documenting the quality control measurements and findings, the Fil-Chi Pet Record Management project team can effectively monitor the product's compliance with the defined quality standards, identify areas for improvement, and implement necessary corrective actions to ensure the delivery of a high-quality web application.

The Risk Management Plan plays a vital role in this project, which strives to develop a web application catering to the clinic's need for efficient patient data management and appointment scheduling. By implementing effective risk management strategies, the project team ensures the delivery of a premium-quality product while proactively addressing potential obstacles to project success. The project team must implement the risk management plan in an agile project since its objectives include identifying and assessing potential risks, developing risk response strategies, and overseeing and controlling risks during the course of the project. The plan will be included into the project's day-to-day activities and reviewed and adjusted as necessary. By proactively managing risks, the project team can ensure that risks are reduced and the project's goals are achieved within the allocated budget and timeline. The potential project risks, the method for managing risks, the steps involved in identifying and assessing risks, tracking risks, putting preventative and mitigation measures in place, and keeping a risk register are all included in the risk management plan. This risk management plan will specify exactly how to handle hazards and monitor their development. The speed with which risks are recognized and addressed, as well as the degree to which the project's objectives are accomplished, will be used to evaluate the efficacy of the plan.

The following are the risks for the Fil-Chi Pet Record Management web app identified by the team. The project manager will choose and use the proper risk reduction and avoidance measures to reduce the likelihood of these hazards.

1. External Security Threats: The web application could be vulnerable to external cyber threats, such as malicious cyber-attacks, hacking attempts, and unauthorized access to sensitive patient or clinic data. Robust security measures must be implemented to safeguard the application and protect confidential information.
2. Resource Constraints: Inadequate allocation or availability of resources, including budget, personnel, equipment, or technology, can significantly hinder project development. Insufficient resources may lead to delays, compromised quality, or failure to meet project objectives. Meticulous resource planning and management are essential to mitigate this risk and ensure the project has the necessary resources at every stage.
3. Technical Complexities: Projects involving sophisticated technologies often face technical hurdles, such as compatibility issues, software or hardware failures, integration challenges, or scalability limitations. These technical complexities can cause setbacks, increased costs, and delays in project delivery. Comprehensive testing, contingency planning, and expert technical support are crucial to address and overcome these challenges effectively.

The Fil-Chi Pet Record Management project team has devised strategies to reduce these risks, such as adopting an Agile development methodology to swiftly identify and address technical issues, thoroughly testing and validating the data migration process, offering training and support to ensure successful system adoption, and keeping in regular contact with stakeholders to promptly address any potential delays or issues. The following are the steps in the Risk Management Approach of the Fil-Chi Pet Record Management Web App:

1. Risk Identification: The project team will proactively identify potential risks to the project through regular team meetings, brainstorming sessions, thorough review of the project scope, and rigorous testing of the web application. Each team member will contribute to this process by documenting the risks they identify based on their potential impact on the project's objectives.
2. Risk Assessment: Once risks have been identified, the team will carefully evaluate and prioritize them based on their potential severity and impact on the project. A risk matrix will be utilized to systematically assess and categorize the identified risks, ensuring that high-priority risks receive appropriate attention and evaluation.
3. Risk Response: For risks deemed high-severity, the team will develop comprehensive risk mitigation plans. These plans will outline specific techniques, processes, and actions to be taken to reduce, prevent, or avoid the identified risks from materializing or causing significant disruptions to the project.
4. Risk Monitoring and Review: The project team will closely monitor and track all identified risks throughout the project's lifecycle. Any changes, improvements, or new emerging risks will be promptly communicated to the project sponsor. Regular risk reviews will be conducted to reassess both existing and newly identified risks, evaluate the effectiveness of the current risk mitigation strategies, and make necessary adjustments to ensure the project remains on track.

Through a comprehensive risk identification process for the Fil-Chi Pet Record Management project, various methods will be employed to identify and assess potential risks. These methods include expert interviews, analysis of historical data from previous projects, and a risk assessment conference involving the project team and key stakeholders. The aim is to create a risk register that documents the identified hazards, including a brief description, potential impact, and likelihood of occurrence.

1. Lack of Project Management and Planning: Inadequate project management practices, such as poor planning, ineffective communication, or insufficient risk assessment, can lead to project failure. Robust project management methodologies and practices should be in place to ensure effective planning, execution, monitoring, and control of the project.
2. Lack of resources: The project may not have access to relevant resources and materials that will be crucial to the completion of the project.
3. Communication and Collaboration Challenges: Ineffective communication and collaboration among team members, stakeholders, or third-party vendors can lead to misunderstandings, delays, and conflicts. Establishing clear channels of communication and fostering a collaborative environment are crucial for successful project development
4. Inadequate Quality Assurance and Testing: Insufficient testing and quality assurance practices can result in undetected defects, functional issues, or poor user experience. Comprehensive testing strategies and quality control processes should be implemented to identify and resolve issues before deployment.
5. External Factors and Dependencies: External factors such as regulatory changes, market conditions, natural disasters, or geopolitical events can impact project development. Identifying and monitoring these external dependencies and having contingency plans in place can help mitigate their potential impact.

The potential risks identified for the Fil-Chi Pet Record Management project will now be qualitatively assessed and prioritized based on their probability and impact. This process will allow the project manager to determine the critical risks that require immediate attention and develop appropriate mitigation strategies. The risk qualification and prioritization for each identified risk are as follows:

• Extreme: Risks with a very high probability of occurrence and severe impact on the project.
• High: Risks with a high probability of occurrence and significant impact on the project. These risks require immediate attention, and mitigation strategies should be developed.
• Medium: Risks with a moderate probability of occurrence and moderate impact on the project. These risks should be closely monitored, and mitigation strategies need to be prepared if they occur.
• Low: Risks with a low probability of occurrence and minor impact on the project. These risks can be periodically monitored, and mitigation strategies can be developed if needed.
• Negligible: Risks with a very low probability of occurrence and negligible impact on the project. These risks can be disregarded.

Probability Impact	High	Medium	Low	Very Low
Insignificant	N	N	N	N
Minor	L	L	N	N
Significant	M	M	L	N
Disastrous	H	H	M	L
Catastrophic	E	E	H	M

The Risk Monitoring approach employs a proactive and continuous process to manage risks throughout the project's lifecycle. Maintaining vigilant monitoring and comprehensive documentation, including identifying risk triggers, is crucial for effective risk management. The project manager will incorporate risk scoring into the project schedule and designate a dedicated risk manager to oversee the monitoring process. This empowers the project manager to pinpoint when risks demand immediate attention and ensure the risk manager provides timely updates during weekly team meetings. During meetings, the risk manager will report on the status of identified risks, highlight any newly emerged risks, and evaluate the effectiveness of existing mitigation strategies. Any necessary adjustments or updates to the Risk Management Plan will be collaboratively made with the project team's input. Overall, the project team will adopt an agile risk management methodology that emphasizes continuous progress, flexibility, and adaptability. Regular assessments and adjustments to the risk management plan will be conducted to ensure its effectiveness and alignment with quality standards throughout the project's duration. By implementing this proactive and iterative approach, the team can swiftly identify, mitigate, and respond to risks, enhancing the project's likelihood of success while maintaining high-quality deliverables.

To effectively address and prevent potential risks in the Fil-Chi Pet Record Management project, the project team will develop a comprehensive risk management plan that prioritizes identified risks. Proactive strategies will be implemented to mitigate probable delays, such as developing contingency plans, allocating additional resources, or adjusting project timelines as necessary. The effectiveness of these mitigation techniques will be continuously assessed in collaboration with stakeholders to ensure their optimal implementation. The project manager will employ the following key considerations and approaches for risk mitigation and avoidance:

• Resource Management: Ensuring the project team has access to the necessary resources, including skilled personnel, expertise, tools, and equipment, will be a priority. The project manager will carefully plan and allocate resources to enable successful project completion within the defined budget and timeline constraints.
• Risk Assessment: Early in the project lifecycle, the team will conduct a thorough risk assessment to identify and analyze potential risks comprehensively. Prompt actions will be taken to address and mitigate these risks through targeted strategies.
• Contingency Planning: The project manager will oversee the development, testing, and validation of contingency plans for each identified risk. These backup plans will ensure preparedness and enable swift response should any risks materialize during the project's execution.
• Communication Strategy: Clear and open communication channels will be established and maintained by the project manager to facilitate effective information sharing among the project team, project sponsor, and stakeholders. This proactive approach will help minimize risks arising from miscommunication or misunderstandings.
• Agile Methodology: To promote flexibility and responsiveness in addressing changes and risks, the project team will adopt an Agile methodology. The project manager will ensure adherence to Agile principles throughout the project, enabling continuous risk management and adaptation.
• Change Management: A well-defined change management process will be implemented to handle unexpected changes effectively. The project team will document, communicate, and obtain approval from relevant stakeholders for any proposed changes, ensuring potential risks associated with changes are properly managed and mitigated.

By implementing these risk mitigation and avoidance strategies, the project team will be better equipped to proactively address potential risks, minimize disruptions, and increase the likelihood of successful project delivery while maintaining high-quality standards.

The risk register, which will be updated throughout the project, will include a detailed explanation of each risk, its likelihood and potential consequences, as well as any mitigation measures implemented. The risk register will be reviewed and updated on a regular basis to ensure that it accurately reflects the project's current state. The risk registry, which will be housed in a central location, will be accessible to all stakeholders. The following criteria will be used for the risk register:

• Risk ID - each risk will be assigned a unique identifier.
• Risk Category - will classify risks into technical, Resource, Communication, Project, Quality, Vendor, External.
• Risk Description - there will be a clear and concise description of the risk event.
• Risk Destination/Owner - will be responsible for monitoring and managing each risk.
• Probability - likelihood of a risk occurring is assessed using a scale of High to Low, with Low indicating the lowest likelihood and High indicating the highest.
• Impact - the risk's potential impact on the project is rated on a scale of High to Low, with Low indicating the least significant impact and High indicating the most significant impact.
• Status -risk's current status, whether it is open, in progress, or closed, is also documented.

The goal of the Fil-Chi Pet Record Management Web App project's procurement management plan is to create a workable framework for handling the procurement processes related to the creation and implementation of the web application. This strategy specifies the methods and tactics that will be used to ascertain expenses, take into account procurement limitations, and set up a contract approval procedure in addition to identifying, analyzing, monitoring, and mitigating procurement risks.

The procurement risks for the Fil-Chi Pet Record Management web app project include: 1. Cost Estimation Risk: Estimating procurement costs accurately can be challenging, leading to overestimation or underestimation. This can result in unnecessary expenses or budget constraints for the web application. 2. Schedule Risk: Delays in procurement activities can cause project schedule delays and impact subsequent tasks if the project team fails to submit or finish on time. 3. Quality Risk: There is a risk of procuring substandard services that do not meet the project's quality standards, leading to poor project outcomes.

The Fil-Chi Pet Record Management web app project’s Procurement Risk Management Plan is outlined in this section. A particular risk management approach is essential given the special issues that procurement presents. 1. Risk Identification: We'll identify possible risks by conducting periodic risk evaluations with the project team, particularly those involved in procurement. 2. Risk Analysis: Each risk will be examined with consideration of how it can impact project cost, schedule, and quality. To precisely assess risk probability and potential impact, both qualitative and quantitative risk analysis methodologies will be used. 3. Risk Monitoring: Throughout the duration of the project, all risks will be continuously monitored, along with any related mitigation plans. With this strategy, any changes in the state of the risk are immediately detected and addressed. 4. Risk Reporting: Key stakeholders will receive regular reports on procurement risks, their status, and any notable changes, providing transparency and group decision-making.

The cost determination for the Fil-Chi Pet Record Management web app project encompasses several key factors that contribute to the overall project expenses. The following considerations will be taken into account during the cost determination process: • Software and Hardware Costs: The expenses associated with acquiring, developing, and maintaining the necessary software and hardware components for the web application will be evaluated. This includes licenses, development tools, hosting infrastructure, and any specialized equipment required. • Web Hosting Expenses: The cost of reliable and secure web hosting services will be assessed. This includes determining the most suitable hosting providers based on their pricing models, performance, scalability, and technical support. • Professional Services Charges: The charges associated with engaging professional services, such as design, development, and testing, will be carefully evaluated. This includes assessing vendors' proposed rates and pricing structures.

The constraints below should be considered as a part of the Fil-Chi Pet Record Management web app. 1. Schedule constraints: Every project has a strict deadline; the deliverables should be made based on their deadline or planned schedule. It is important that individuals pass their deliverables on time to avoid any delays to the project and to ensure the team stays on the right track. Any delays within the deliverables might cause the problem to snowball into bigger issues that can affect the project itself. 2. Budget constraints: the project has an allotted budget for the project. 3. Technology Constraints: The software that the team makes does not demand a higher specification for it to run. A typical office computer/desktop can suffice for the software to run smoothly. 4. Resource constraints: The personnel of the office should be knowledgeable of how to operate or use the newly made software for them.

The contract approval process for the Fil-Chi Pet Record Management web app project ensures that all contracts are reviewed and approved in a structured and efficient manner. The following enhanced process outlines the steps involved: 1. Contract initiation: the project manager would first pitch the idea to the clinic. 2. Contract planning. The head of the clinic would then make suggestions or customized features that would personally cater to the needs of the clinic. 3. Contract development: Once the contract is set and ready. The team would develop the software and would have a meeting with the client regarding about the status of the software.

The following are the decision criteria that the contract review board will use for the Fil-Chi Pet Record Management web app: 1. Cost: The cost of the vendor’s proposed solution should be manageable and affordable. It should be based on existing resources and materials in the current market. 2. Schedule: The vendor must show they can complete the project by the deadline and deliverables, as well as significant checkpoints and due dates. 3. Technical Skills: The team must be able to exhibit the necessary skills and capabilities to ensure that the project will be successful. 4. Experience: The vendor must show that they have sufficient experience in handling the current project through past projects that involve developing similar or related systems. 5. Risk Management: The vendor must show that they have the necessary knowledge of risk mitigation techniques as well as methods in identifying potential risk that might impact the progress of the project.

The following metrics that will be used for procurement activities are: 1. Vendor performance rating: The project manager and the project sponsor would thoroughly review the product of the vendor's product. In this way, this gives the team a much better point of view since there are people vouching for the product of the vendor. 2. Procurement cycle time: These measures the vendor’s capabilities or how fast and efficient it is when delivering the items. This starts from the initial ordering of the materials to finishing the project from installing the delivered goods. 3. Cost variance: This metric serves as a purpose to scout the market on the lowest price possible on certain materials. This gives the company a lot of choices settling between couples of vendors who have the best deal possible. 4. Purchase Order Accuracy: This metric tests the vendor’s accuracy when delivering the materials in a large quantity. One wrong item can possibly cause a delay in a project.

The goal of the Fil-Chi Pet Record Management web app is to provide a strong and simple platform that improves community connection and interaction. The strategy places a strong emphasis on timely delivery, effective use of resources, stakeholder involvement, quality control, and all-encompassing support. The project team will keep a close eye on developments, recognize potential problems or hazards, and take proactive steps to resolve any obstacles that may come up throughout the implementation phase. It will be ensured that the implementation is in line with the project's objectives and produces the intended results through regular evaluation and feedback systems. When the Fil-Chi Pet Record Management web app is successfully implemented, the clinic's operational efficiency will be greatly increased, the quality of pet care services will be raised, and pet owners and clinic staff will feel more connected to the community.

In the implementation plan, this section provides an overview of the team organization, including the roles and responsibilities of each team member. It helps stakeholders understand the individuals involved in the project, their areas of expertise, and their specific contributions to the development and transition of the Fil-Chi Pet Record Management web ap 1. Project Manager: Oversee and ensure the overall success of the transition. Lead the transition team, ensure timely completion of tasks, maintain coordination with the customer, and ensure adherence to the transition plan. 2. Scrum Master: Facilitate the agile development process, organize, and lead scrum meetings, remove obstacles, promote collaboration and effective communication within the team. 3. Document Manager: Create and maintain project documentation, including requirements documents, user manuals, technical guides, and other relevant documentation. 4. Laravel Junior Developer: Develop both client-side and server-side components of the web application, ensuring responsive and interactive user interfaces using HTML, CSS, and JavaScript frameworks, while handling data processing, database integration, and business logic implementation with programming languages like PHP and MySQL.

The Transition Project Manager will be working on assigning and retaining current staff or hiring a new one whichever is fit to handle the Fil-Chi Pet Record management System once it has been handed over to them. It is critical for the overall transition to determine the people who will handle and maintain the system, to ensure that it will be utilized as it should be. In this process, effective communication will be crucial. Any changes should be promptly and respectfully communicated to the staff. To make sure all team members are fully informed of their options and receive the appropriate assistance throughout the transition process. Furthermore, staffs will receive the necessary training or retraining to ensure that they are well-equipped to continue providing high-quality services both during and after the transition phase. Understanding details of the web app, its features, and the security precautions it uses are part of this.

Transitioning a workforce during a web application deployment or migration requires careful planning and execution to ensure a smooth and efficient process. 1. User Training: The team needs to identify the specific knowledge and skills users need to acquire. Also, set a clear objective aligned with the web application’s features and user roles 2. Final Testing and QA with the stakeholders: The project team, with the necessary stakeholders, needs to conduct final testing and quality assurance of their web application to ensure a fully functional and it meets all requirements. Migrate any relevant data or content from the legacy systems to the new web application and validate the accuracy and completeness of the data. 3. Documenting Successes and Achievements: Document all the successes and achievements of the implementation process of the team. Acknowledge the contributions of team members and stakeholders who played a vital role in the project's success. Lastly, Identify the areas where improvements can be made for future implementations and updates. 4. Gain Formal Acceptance: Verify everything that all project tasks and activities have been successfully completed. After verifying everything, the development team needs to prepare a formal acceptance agreement or document that will outline the stakeholder’s acceptance of the project. Do not forget to obtain the necessary signatures or approvals from the relevant stakeholders to signify their formal acceptance. 5. Archive Files/Documents: The team needs to review all the files to determine which one is eligible for archiving. After that, sort the files into categories for efficient archiving. 6. Project Close Out Meeting: The development team needs to define the objectives of the close out meeting, including reviewing the project accomplishments, documenting lessons learned, and lastly, celebrating the project's success.

In the case of the Clinic, the client has no prior system before the project has been done. All processes were conducted manually through a physical workforce and the storage are physical file cabinets. The system of the Clinic before the project is all paper based so there will be no issues regarding the transition of all the intellectual properties.

The objective of this implementation plan is to outline the stages and procedures for implementing user accounts and passwords. The security and privacy of user data on the web app is greatly improved with user accounts and passwords. We hope to develop a reliable and intuitive authentication system by adhering to the guidelines and best practices described in this plan.

To ensure the successful implementation and sustainability of the new Pet Record Management web app at Fil-Chi Animal Clinic, a comprehensive knowledge transfer plan will be executed. Initial and advanced training sessions as well as the creation of comprehensive user guides to familiarize staff members with the new system are part of this approach. All training materials will be available as well on a consolidated web page portal, and frequently asked questions will be answered in a FAQ database. A helpdesk system will be implemented for technical support, and a mentorship program will match experienced employees with less experienced ones to offer continuing support. The knowledge transfer method will be continuously improved and adjusted with the help of regular evaluations and feedback systems, giving the clinic's employees the skills they need to operate and maintain the web application.

Throughout the project’s lifetime, the team is able to submit all deliverables needed. Each work that was assigned to each member has a specific deadline to help the team estimate how many resources will be needed to finish all the needed tasks before proceeding. To create the project schedule, the team used software named Open Project to create a Gantt Chart. In this Gantt Chart, all the activities and deliverables are listed and recorded. In this way, it is much easier to monitor the project’s growth over time.

Upon the project’s completion that would be decided by the team and the client, through the criteria of done the complete handover of the system would be given onto the Clinic, along with all other resources and assets that have been used or would prove to be beneficial for them to continuously deploy and run the product, together with any other documentation that may prove to be useful and vital for the exchange.

An essential component or phase of a successful project is changing management. The procedures for identifying and altering a project, including its scope, are outlined in the change management process. This guarantees that everything is in order, including development, web app design, implementation, and what the barangays still require. An all-encompassing and methodical approach to change management is crucial to the project's success, which will result in a significant modification or changes. An efficient change management strategy will boost output and guarantee that the team's project web application keeps getting better.

The Change Control Board (CCB) is the approval authority for all proposed change requests pertaining to the Fil-Chi Pet Record Management Project. The purpose of the CCB is to review all change requests, determine their impacts on the project risk, scope, and schedule, and to approve or deny each change request. The following chart provides a list of the CCB members for the web-app project:

Name	Position	CCB Role
Mary Grace A. Resado	Project Sponsor	CCB Chair
Klarenz Villanueva	Project Manager	CCB Member
Alelie Yvonne Tayco	Scrum Master	CCB Member

The following are the roles and responsibilities for all change management efforts related to the Fil-Chi Pet Record Management Web App:

Project Sponsor:

• Approve all major changes to the web application.
• Approve all changes to schedule baseline.
• Approve any changes in project scope.
• Chair the CCB

Project Manager:

• Receive and log all change requests from project team.
• Conduct preliminary risk, schedule, and scope analysis of change prior to CCB.
• Seek clarification from change requestors on any open issues or concerns.
• Make documentation revisions/edits as necessary for all approved changes.
• Participate on CCB

Project Team:

• Submit all change requests on standard organizational change request forms.
• Provide all applicable information and details on change request forms.
• Be prepared to address questions regarding any submitted change requests.
• Provide feedback as necessary on the impact of proposed changes.

Change is inevitable in any project, and it is crucial to have a well-defined process to manage and control changes effectively. The change control process ensures that all changes to the project scope, requirements, schedule, or resources are properly evaluated, approved, and implemented in a controlled manner. The following steps outline the change control process for this project:

Change Request: Any project team member, stakeholder, or sponsor can identify and initiate a change request. The request should be documented in a standardized change request form, providing details about the proposed change, its justification, and potential impacts on the project.

Change Evaluation: The project manager, along with relevant subject matter experts and stakeholders, will evaluate the change request. This evaluation will assess the impact of the proposed change on the project scope, schedule, budget, resources, quality, and risk. The feasibility, costs, benefits, and potential risks associated with the change will be carefully analyzed.

Change Approval: Depending on the nature and severity of the change, approval may be required from different levels of authority. Minor changes may be approved by the project manager, while significant changes may require approval from the project sponsor, steering committee, or relevant stakeholders. The approval process will follow a predefined authority matrix.

Change Implementation: Once a change request is approved, the project manager will develop a detailed implementation plan. This plan will outline the necessary actions, resources, and timelines required to implement the change effectively. The project manager will communicate the approved change and its implementation plan to the project team and relevant stakeholders.

Change Monitoring and Control: The project manager will monitor the implementation of the approved change to ensure it is executed as planned. Any deviations or issues encountered during the implementation phase will be addressed promptly. The project manager will also assess the impact of the implemented change on the overall project and make necessary adjustments to the project plan, schedule, and resources.

Change Documentation: All change requests, evaluations, approvals, and implementation details will be thoroughly documented in a change control log or register. This documentation will serve as a historical record and facilitate effective change tracking and auditing throughout the project's lifecycle.

By following this structured change control process, the project team can ensure that changes are properly evaluated, approved, and implemented in a controlled manner, minimizing disruptions and maximizing the chances of successful project delivery.