Table of Contents Project Title Project Members Project Professor Project Adviser Project Team Company Profile Business Case Executive Summary Business Case Analysis Team Problem Definition Project Overview Strategic Alignment Cost Benefit Analysis Alternatives Analysis Approvals Project Charter Executive Summary Project Purpose/Justification Business Need/Case Business Objectives Project Description Project Objectives and Success Criteria Requirements Constraints Assumptions Preliminary Scope Statement Risks Project Deliverables Summary Milestone Schedule Project Approval Requirements Project Manager Stakeholder Management Strategy Introduction Identify Stakeholders Key Stakeholder Stakeholder Analysis Scope Management Plan Introduction Scope Management Approach Roles and Responsibilities Scope Definition Project Scope Statement Work Breakdown Structure Scope Verification Scope Control Cost Management Plan Introduction Cost Management Approach Measuring Project Costs Reporting Format Cost Variance Response Process Cost Change Control Process Project Budget Schedule Management Plan Introduction Schedule Management Approach Schedule Control Schedule Changes and Threshold Scope Change Work Breakdown Schedule Introduction Outline View Hierarchical Structure Tree Structure View Human Resource Management Plan Introduction Roles and Responsibilities Project Organizational Charts Staffing Management Change Management Plan Introduction Change Control Board Roles and Responsibilities Change Control Process Communications Management Plan Introduction Communications Management Approach Communications Management Constraints Stakeholder Communication Requirements Roles Project Team Directory Communication Methods and Technologies Communications Matrix Guidelines for Meetings Communication Standards Communication Escalation Process Glossary of Communication Terminology

NAME	POSITION	EMAIL
Jose Eugenio L. Quesada	PROJMAN Professor	[email protected]

NAME	POSITION	EMAIL
Doc. Manuel L. Calimlim Jr.	PROJMAN Adviser	[email protected]

NAME	EMAIL
Ramon Benedict V. Elloso	[email protected]
Carlos C. Ligligen Jr.	[email protected]
Andrei Gabriel B. Palma	[email protected]
Done Paolo Y. Tarinay	[email protected]

Ms. Devilyn C. Ligligen is the owner of a small-scale retail outlet situated on Mt. Makiling St., Post Proper Southside, Makati City. She caters to sari-sari stores and a diverse range of customers in the surrounding vicinity, providing goods for both wholesale and retail transactions.

Bregghan Mini Grocery Store is a family-owned business that supplies retail, wholesale, and bulk products to residents and sari-sari stores in the area. The store's current system for tracking sales and stocks is manual, using pen and paper, which has led to difficulty in monitoring inventory and potential loss of sales due to items being out of stock.

To address these pain points, our team aims to develop a responsive webapp that digitizes the recording of stocks and sales, notifies the user when stocks are at a critical level, and automates the computation of sold items. In addition, the webapp will also produce a basic report that shows the items sold.

Manual inventory tracking:

The current system at Bregghan mini grocery store involves manual recording of stocks and sales on paper, which can be time-consuming and prone to errors. The lack of a proper inventory management system can result in out-of-stock items and missed sales opportunities.

Inefficient sales tracking:

The current sales tracking process relies on hand-written receipts, which can lead to errors in the computation of items sold and total sales. This can result in inaccurate sales data and hinder the store's ability to make informed business decisions.

Lack of real-time monitoring:

Without a digital system, the staff at Bregghan mini grocery store are unable to monitor stocks and sales in real-time. This can result in missed opportunities to replenish stock levels and can make it difficult for the store to keep up with customer demand.

Improved inventory management:

The implementation of a digitized sales and stock tracking system will allow Bregghan mini grocery store to have accurate and real-time data on their inventory. This will enable them to make informed decisions on when to replenish stock, which products to order, and how much stock to order, leading to a reduction in stock outs and overstocking.

Increased sales:

With the implementation of a Point-of-Sale (POS) system, the checkout process will be faster and more efficient. Customers will have a better experience and may be more likely to return. The system will also be able to generate reports on the top-selling products, which can help the store to make informed decisions on product placement and marketing strategies.

Reduced errors:

The automated computation of items sold will significantly reduce the occurrence of human errors, which can lead to miscounting of inventory and discrepancies in sales records. This will result in more accurate sales and inventory data.

Increased productivity:

The implementation of a digitized sales and stock tracking system will reduce the workload of the staff, as they will no longer have to manually record sales and inventory. This will free up their time, allowing them to focus on other tasks that can improve the store's operations.

To address the identified business problem of inefficient stock and sales monitoring at Bregghan mini grocery store, we recommend developing a responsive web application that digitizes the recording of stocks and sales, automates computation of sold items, and produces reports for daily, weekly, monthly, and yearly records. By implementing this solution, the staff and manager of Bregghan mini grocery store will be able to monitor stocks and sales in real-time, reducing workload and minimizing human error. This will lead to more efficient inventory management and faster checkouts, resulting in improved customer satisfaction and retention. The system will also provide alerts when stock levels reach a critical point, allowing the store to replenish inventory on time and avoid potential revenue loss due to out-of-stock items. Furthermore, the application's capability to produce detailed sales reports will provide useful insights to the business, allowing for data-driven decision-making to further optimize operations and profitability. Overall, we believe that the proposed solution will address the identified business problem and provide significant benefits to Bregghan mini grocery store, its staff, and its customers.

Bregghan mini grocery store recognizes the need for improvement in its operational processes, particularly in sales and inventory tracking. The current manual system in place is time-consuming and prone to errors, hindering overall efficiency. To address these challenges, the store proposes implementing a digitized system that offers numerous benefits.

By adopting a digital system, the staff, and managers at Bregghan can track sales and inventory in real-time, reducing the workload and improving efficiency. The proposed project will enable more accurate inventory tracking, ensuring timely restocking to avoid stockouts and potential sales losses. With better inventory management and automated sales tracking, the store can meet customer demands more effectively, leading to increased sales and greater customer satisfaction.

In addition to sales and inventory improvements, the implementation of a point-of-sale (POS)-like system will enhance the overall customer experience. Customers will benefit from faster checkouts and more accurate receipts, resulting in improved service quality. Furthermore, by embracing digitalization, Bregghan mini grocery store can remain competitive with other stores that have already implemented similar systems, maintaining its position in the market.

Failure to implement the proposed project would have negative consequences for the store. The current manual system would continue to hinder efficiency and accuracy, resulting in wasted time and potential revenue loss. Inaccurate inventory tracking could lead to stockouts, lost sales, and dissatisfied customers. Furthermore, without keeping pace with competitors who have already embraced digital systems, Bregghan mini grocery store risks losing customers to these technologically advanced stores. Therefore, it is imperative for the store to proceed with the implementation of the proposed project to drive efficiency, sales growth, customer satisfaction, and maintain a competitive edge in the market.

The roles and responsibilities of the team members involved in the plan development are illustrated in Table 1.

Designation	Name
Project Sponsor:	Ms. Devilyn C. Ligligen
Project Adviser:	Doc. Manuel L. Calimlim Jr.
Project Manager:	Ramon Benedict V. Elloso
Team Member:	Carlos C. Ligligen Jr.
Team Member:	Andrei Gabriel B. Palma
Team Member:	Donne Paolo Y. Tarinay

Bregghan mini grocery store is currently facing several issues in their daily operations, which are mainly caused by their manual recording and tracking system. Specifically, the store has trouble in monitoring their inventory, which can result in insufficient stocks or overstocking. Additionally, the manual computation of sold items often leads to errors, which affects the accuracy of their sales records. As a result, the store loses potential customers due to a lack of available items, leading to decreased profits. Furthermore, the current process of tracking sales and stocks is time-consuming, which can lead to slower checkouts and longer queues. Overall, the business problem is the need for a more efficient and accurate system to monitor inventory and sales to improve the overall customer experience and increase revenue.

The implementation of the proposed project will have a significant impact on the organizational processes, tools, hardware, and software of Bregghan mini grocery store. It will require the adoption of new technology and the implementation of new processes to manage sales and inventory in a digitized and automated way. The system will replace the traditional pen-and-paper method of tracking sales and inventory, which will require staff to be trained in the use of the new technology.

New roles will be created to manage the system and ensure its proper functioning. The manager will have access to the system's reporting tools to generate daily, weekly, monthly, and yearly reports on sales and inventory. The system will also require the creation of a database of products that the store offers, and this will need to be updated and maintained regularly.

The proposed project will bring a positive impact to the organizational processes, increasing the efficiency and accuracy of sales and inventory tracking. The store staff will be able to manage the stock level in real-time, making restocking more efficient and reducing the risk of stockouts. The system will also provide better insight into product performance and inventory management, allowing for better decision-making and more informed business strategies.

The plan for the Bregghan POS System involves the creation of a website and mobile application that will be powered by Amazon Web Services (AWS) for the database. AWS is a type of cloud service that allows businesses to rent computing resources like servers, storage, and databases. The developers chose AWS for the mini grocery store due to its scalability, allowing the store to scale up or down easily to meet changing demands in the future without worrying about managing their infrastructure. AWS is also highly reliable and can handle large volumes of traffic and data without slowing down. The data migration process will ensure that all necessary data is transferred to the new system, and the new system will undergo thorough testing to ensure reliability, efficiency, and security.

This section provides a broad overview of the Bregghan POS System, which encompasses a description, its goals and objectives, performance criteria, assumptions, constraints, and major milestones.

The project will develop a sales and stock tracing system to address the business problem of Bregghan mini grocery store which is the lack of efficient monitoring of their stocks and sales. The purpose of the project is to develop a digital application that will provide the staff and manager of the store with an efficient way of monitoring their stocks and sales in real time, reducing the workload and potential for human errors. The project will consist of developing a POS-like system where users can monitor the items that go in and out of the store and can compute the total prices, and a system for generating and storing digital copies of receipts. The system will be developed using modern software development practices and technologies. The project will be executed in three terms, with clear milestones and deliverables to ensure that it stays on track and within scope.

The project team intends to accomplish the project as effectively as possible to help and improve the current system of Bregghan Store. The following listed objectives are the team needed to accomplish:

• To develop a responsive web application that accurately tracks sales and inventory for Bregghan mini grocery store, enabling real-time monitoring and reporting.
• Decreases the number of steps that the user can do in the whole transaction for faster checkouts.
• To fully digitize the recording of stocks and sales for Bregghan mini grocery store, ensuring that all inventory and sales transactions are accurately captured and stored electronically.
• To implement a notification system that alerts the user when stock levels reach a critical threshold, ensuring timely replenishment and avoiding stockouts.
• To automate the computation of sold items, ensuring accurate and efficient tracking of sales data.

Assessing the project performance of a Point of Sale (POS) system project involves evaluating various aspects of the project to determine its progress, adherence to objectives, and overall success. Listed below are the project assessment of the Bregghan Point of Sale System:

• Schedule Performance

  The team will have to evaluate the project's schedule performance by comparing the planned timeline with the actual progress. This assessment involves monitoring the achievement of milestones and deliverables within the defined timeframes and analyzing the schedule variance and schedule performance index. These indicators help determine if the project is progressing as scheduled or if there are delays.

• Project Cost Performance

  The project team must assess the project’s cost performance by comparing the planned budget with the actual expenditure. This evaluation involves analyzing the cost variance and cost performance index to determine if the project is staying within the budget or if there are cost overruns. It is also essential to evaluate the effectiveness of cost control measures in place to manage expenses effectively.

• Quality Performance

  The project team must evaluate quality performance by assessing the project's adherence to quality objectives and metrics defined for the POS system. This assessment involves examining the level of compliance with quality standards and customer requirements, as well as identifying and addressing any quality issues, defects, or customer complaints. The effectiveness of corrective actions taken to resolve quality issues should also be assessed.

• Scope Performance

  The scope performance should be assessed by reviewing the alignment of project deliverables and scope with the initial project requirements and objectives. This evaluation involves analyzing any scope changes that have occurred and assessing their impact on the project's timeline and budget. It is crucial to evaluate the scope variance and the effectiveness of scope control measures implemented to ensure that the project stays on track.

• Risk Performance

  The risk performance should be evaluated by the project team by assessing the identification and mitigation of project risks. This involves examining the effectiveness of risk response strategies implemented and identifying any emerging risks that may pose a threat to the project's success. Proactive risk management is essential to minimize the impact of risks on the project.

• Stakeholder Satisfaction

  Finally, it is crucial for the project team to gather feedback from various stakeholders, including users, management, and other relevant parties, to ensure their satisfaction. Obtaining feedback from these stakeholders helps assess their level of involvement and contentment with the project's results. Additionally, it provides valuable insights that can be used to pinpoint areas that require enhancement based on the stakeholders' input.

Listed below are the main assumptions for the project:

• All necessary funding and resources will be secured and available for the duration of the project.
• All stakeholders will be available and able to provide input as needed throughout the project lifecycle.
• There will be no major technological or market disruptions that would impact the project's success.
• The project team will have the necessary expertise and skill sets to complete the project successfully.
• All regulatory and legal requirements will be met and any necessary permits or approvals will be obtained.
• The project will be completed within the proposed timeline and budget.
• The project scope will remain consistent throughout the project lifecycle, and any changes will be managed through a formal change control process.
• The project team will be able to effectively communicate and collaborate throughout the project lifecycle.
• The project will not have a significant negative impact on the environment, community, or stakeholders.
• The project will result in the anticipated benefits and outcomes as described in the business case.

Listed below are the following constraints of the production of the project:

• Budget constraints: The project cannot exceed a certain budget, which may limit the scope or timeline of the project.
• Time constraints: The project must be completed within the designated timestamp of the subject course Project Management (PROJMAN).
• Resource constraints: The project team may have limited staff, expertise, or technology available to complete the project.

Milestones	Duration
Project Initiation	03/28/2023 - 04/28/2023
Project Planning and Preparation	05/01/2023 - 05/18/2023
Phase I: Analysis	05/19-2023 - 05/26/2023
Phase II: Design and Development	05/29/2023 - 07/08/2023
Phase III: Testing	07/11/2023 - 08/15/2023
Phase IV: Implementation	08/16/2023 - 09/06/2023
Project Closeout/Completion	09/07/2023 - 09/19/2023

The strategic alignment of the Bregghan Point of Sale (POS) system refers to how well the project aligns with the organization's overarching strategic objectives and goals. The POS system should be designed and implemented in a manner that supports the organization's long-term vision and strategic initiatives.

To achieve strategic alignment, it is crucial for the project team to have a deep understanding of the organization's strategic direction and determine how the POS system can contribute to its success. This entails conducting a comprehensive analysis of the organization's business processes to identify areas where the POS system can enhance efficiency, improve the customer experience, or drive revenue growth.

Moreover, the project team must align the scope, features, and functionalities of the POS system with the organization's strategic priorities. This involves prioritizing the development and implementation of system components that are most critical to achieving the organization's strategic objectives.

Regular and effective communication and collaboration between the project team and key stakeholders, including senior management, play a vital role in ensuring strategic alignment. It is essential to actively involve stakeholders throughout the project lifecycle and seek their feedback to validate that the POS system is meeting strategic goals and delivering the desired impact on the organization's overall performance.

The following section in the document provides a detailed examination of the costs and benefits of the Bregghan POS System project. The aim of this analysis is to assess the financial viability of the project, considering the expenses as well as the projected advantages of the suggested system. The findings of the analysis will assist in determining if the project is a valuable investment for the client.

The costs considered in the cost benefit analysis include both upfront expenses, such as software development, hardware, and implementation costs, as well as ongoing operational costs like maintenance, upgrades, and support. These costs are carefully estimated and aggregated to provide a comprehensive understanding of the financial investment required for the POS system.

Costs:

The costs related to the Bregghan POS System project are outlined as follows:

Approved Budget	₱ 1,000,000.00
Manpower Cost	₱ 546,240.00
Hardware Cost	₱ 178,418.00
Software Cost	₱ 3,654.00
Contingency Cost:	₱ 36,415.60
Total Project Cost:	₱ 764,727.60

Benefits

Implementing a Point of Sale (POS) system in the Bregghan store can bring about a multitude of valuable advantages. Listed below are the several potential benefits:

• • Improved Efficiency

  A POS system automates various processes, such as inventory management, sales tracking, and transaction processing. This will reduce the number of steps in the current manual system of the Bregghan store.

• Enhanced Accuracy

  With a POS system, the chances of human errors in recording sales, calculating prices, or managing inventory are minimized. This leads to more accurate data and reduces discrepancies in stock levels and financial records.

• Real-time Inventory Management

  A POS system allows for real-time tracking of inventory levels, enabling the store to maintain optimal stock levels, avoid stockouts or overstocks, and improve inventory turnover. This ensures that popular products are readily available for customers while minimizing holding costs.

• Improved Customer Service

  With a POS system, store staff can quickly access product information, inventory availability, and customer purchase history, enabling them to provide personalized and efficient customer service. This enhances the overall shopping experience and fosters customer loyalty.

Alternative systems offer different approaches to address the limitations of the current manual system and provide various benefits to the Bregghan store.

• Status Quo: The first alternative considered was to maintain the current process and not implement any changes.

  Pros: No upfront costs or disruption to existing processes and systems.

  Cons: Manual data entry and calculations are susceptible to human errors, such as miscounts, data inaccuracies, or calculation mistakes, which can impact inventory management, sales tracking, and financial records. Manual systems may struggle to handle increased volumes of data or business growth, as they often lack the scalability and efficiency of automated systems. Manual systems typically do not provide real-time data updates, making it challenging to have immediate insights into inventory levels, sales performance, and other critical business metrics.

• Manual Process Improvement: The second alternative considered was to improve the existing manual process by introducing new tools and technologies, such as automation software.

  Pros: By introducing new tools and technologies, the manual process can be enhanced incrementally, allowing for a smoother transition, and minimizing disruption to ongoing operations.

  Cons: While introducing new tools and technologies can enhance the manual process, it may not fully automate all tasks, leading to ongoing manual effort and potential inefficiencies. The effectiveness of the improved manual process is still dependent on human input and diligence, making it susceptible to human errors, inconsistencies, and potential variations in execution.

• Outsourcing: The third alternative considered was to outsource the process to a third-party vendor. However, this option was rejected due to the lack of control over the process and potential security risks associated with sharing confidential company information with external parties.

  Pros: Outsourcing provides access to specialized skills and expertise that may not be available within the organization. This allows for the optimization of the process through industry knowledge and experience. By outsourcing, Bregghan can save costs by avoiding the need to hire and train additional staff, invest in infrastructure, and maintain software or hardware systems.

  Cons: Outsourcing relinquishes control over certain aspects of the process, such as decision-making, quality control, and data security, potentially affecting effective management and oversight. Working with external vendors may introduce challenges related to communication and coordination, including time zone differences, language barriers, or cultural variations. These can lead to misunderstandings and project delays.

The approval of the project should be obtained from the main stakeholder, Ms. Devilyn C. Ligligen, who is the owner of the business.

Ever since the establishment of the Bregghan mini grocery store, it has been using a pen and paper to track the stocks and sales that are going in and out of the store. In addition, the store’s current Point of Sales System is a manual computation, and the receipts are handwritten. With the integration of the project, it will provide technology solutions which produces efficiency among workload in the said company.

This section of the paper will explain the purpose of the project that will be implemented which is the Bregghan Point of Sale System. Furthermore, the business case will also discuss why the project is needed since it is related to how the small business operates.

The Bregghan Point Sales System Application was created to change the manual recording of pen and paper which is used by the company to track sales and stocks, into a digitized version that will be used by the owner and their employees. This integration of technology solution will aid the client in utilizing stocks, analytical reports, and faster recording of sales throughout the day. The Bregghan mini grocery store perceived that the use of pen and paper to records stocks and sales takes up the time and efficiency. The company also noticed that the integration of this technological solution will allow them to ease the workload when checking the stocks and manual recording of sales.

The business objectives for the project are listed below:

• Supply grocery needs to sundry stores in the area.
• Provide groceries to people in the area.
• Provide transparent pricing for items.
• Provide faster checkouts for customers.

This integration of technology solution will aid the client in utilizing stocks, analytical reports, and faster recording of sales throughout the day. The Bregghan mini grocery store perceived that the use of pen and paper to records stocks and sales takes up the time and efficiency and the company also noticed that an integration of this technology solution will allow them to ease the workload when checking the stocks and manual recording of sales. This will be done by implementing systems for the admin and its employee connected with each other, the admin monitoring the sales and stocks while the employee’s system or Point-of-Sale will handle outgoing stocks from the grocery.

The project team intends to accomplish the project as effectively as possible to help and improve the current system of Bregghan Store. The following listed objectives are the team needed to accomplish:

• To develop a responsive web application that accurately tracks sales and inventory for Bregghan mini grocery store, enabling real-time monitoring and reporting.
• Develop an admin system that can monitor the stocks and sales real time.
• To fully digitize the recording of stocks and sales for Bregghan mini grocery store, ensuring that all inventory and sales transactions are accurately captured and stored electronically.
• To implement a notification system that alerts the user when stock levels reach a critical threshold, ensuring timely replenishment and avoiding stockouts.
• To automate the computation of sold items, ensuring accurate and efficient tracking of sales data.

To achieve success, the project must meet the following requirements:

• Sales and Inventory Management: The system should enable us to track sales and manage inventory. Stock quantities should automatically update when purchases are made. It should provide real-time monitoring.
• Reports and Analytics: The system should generate transaction reports and analytics, including the top-selling products, sales and which category of products are sold often.
• Flexibility: Different businesses have unique needs; the system should offer customized options to adapt to the business rules.

The following constraints pertain to the Bregghan Point of Sale System:

• Budget constraints: The project cannot exceed a certain budget, which may limit the scope or timeline of the project.
• Time constraints: The project must be completed within the designated timestamp.
• Resource constraints: The project may have limited staff, expertise, or technology available to complete the project.

The following is the list of the assumptions. Upon agreement and accepting this document at the end, all parties acknowledge that these assumptions are true and correct:

• The completed system will only be accessible for the client (Bregghan Mini Grocery Store)
• The developers that will work on this project will utilize open-source development tools and all the necessary tools for the testing environment will be provided by the client.
• The Bregghan Mini Grocery Store has the environment to reinforce the development, implementation, and the maintenance of the project.
• The budget and the project timeline will remain unchanged throughout the project's development.
• The project will be managed and foreseen by the project sponsor and stakeholder. All the approvals or permission necessary will be gained promptly.
• The staff and the manager of the of the Bregghan Mini Grocery Store will gain all the necessary knowledge and skills to adapt to their new system as the developers will provide adequate time to teach them.

The scope of the project contains the development of two systems one for the manager and one for the cashier. The system will include features that can help the manager track the remaining stocks left and identify which items are sold. Furthermore, it can be used to transact items with customers and it holds all of the sales transacted within the day. The system will also include analytical reports in order for the manager to successfully restock on time. The project’s completion will be determined by the success of its deployment to the client and its staff. Another part that will determine the completion of the project is with the implementation of the new system to the client and completely digitizing the current use manual pen and paper. Moreover, the project will include the support needed and training for the manager and the cashier of the mini grocery store.

The following risks for the Bregghan Point-of-Sale system project is identified. The project manager should implement avoidance strategies appropriate to minimize the likelihood of these risks:

• Equipment failure: Backlogs due to equipment breakdown.
• Limited resources: the risk of insufficient resources which are budget, personnel, and equipment to attain the completion of the project.
• Human error: There might be a risk of mistakes made by the project developers which can affect the project's completion.
• Unforeseen instances: There is a risk that could impact the project in unforeseen scenarios like natural disasters.
• Scope creep: There is a risk that the scope may gain growth (additional requirements or features) that may lead to delays and budget overrun.
• Dependencies on other parties: There is a risk that the project may depend on the performance and capabilities of external parties that can lead to other issues such as backlogs.
• Technological Changes: There is a risk that there might be some changes in technology or the industry standards that may result in additional work or resources for the project.

The deliverables listed must be met to acknowledge the completion of the project. All changes that might arise within these deliverables must be approved by the project sponsor.

• An Admin system that can monitor the sales of the mini grocery store.
• An Admin system that can give analytical reports for the manager showing the top selling items.
• A system that keeps tracks of the items left on the grocery store.
• An Admin system that generates a sales report showing the trend for the total amount.
• A cashier POS (Point of Sale) that can compute for the items bought by the customer.
• A cashier POS that can print a receipt for a customer.

Summary Milestone Schedule
Project Milestone	Target Date
Project Initiation	March 28, 2023
Project Planning and Preparation	May 01, 2023
Phase I: Analysis	May 19, 2023
Phase II: Design and Development	May 29, 2023
Phase III: Testing	July 11, 2023
Phase IV: Implementation	August 16, 2023
Project Closeout/Completion	September 07, 2023

Success of the Bregghan Point of Sale System will be achieved when the admin system and POS system is fully tested with the time and cost as being mentioned in this charter. We fully anticipate the need for this proposed solution to ease the workload of the client and their employees. The project sponsor, Ms. Devilyn Ligligen, will also approve the project by the project’s success.

Benedict Elloso is named as the Project Manager for the duration of the project. Mr. Elloso’s responsibility is to manage all project tasks including the scheduling and communication through the client regarding this project.

This document's purpose is to identify and analyze all stakeholders of this project as they will have an impact and interest on the project. Moreover, this document will serve as a strategic roadmap to gain a better relationship with stakeholders and attain an efficient utilization of stakeholder support. In addition, the information about the stakeholders adjacent to the deliverables is found within this document.

Identifying stakeholders is important to attain continuous updates and refinement as the project progresses as they will be the ones that will give support and communication to ensure success on the project development. The stakeholder identification will include the internal and external stakeholders which contains the project team members, sponsors, owner, and customers. To identify the prioritization of stakeholders, the project team utilizes a stakeholder analysis which identifies the power and interest of each stakeholder. Furthermore, having methodologies such as consultation meetings and document reviews can help the team in further identifying those people that have a personal interest in the project.

The key stakeholders of the Bregghan Point of Sale System are the business owner/manager and their cashier. These individuals will directly impact the project as they are the people that will use the system and cater to their mini grocery store’s customers. Moreover, the needs and the concerns of these key stakeholders must be met during project development. With the usage of the Bregghan Point of Sale System, it would enable the stakeholders to integrate a faster approach with regards to transactions and stocks management.

Name	Position	Internal/External	Contact Information
Ms. Devilyn Ligligen	Business Owner/Manager	Internal	[email protected]
Cashier	Cashier Employee	Internal	[email protected]
Ramon Benedict Elloso	Project Manager	Internal	[email protected]
Carlos Ligligen	Team Member	Internal	[email protected]
Andrei Gabriel Palma	Team Member	Internal	[email protected]
Donne Paolo Tarinay	Team Member	Internal	[email protected]
Customer	Customer	External	[email protected]

The stakeholder analysis is an important part of this documentation as it helps the project manager identify which stakeholders have the biggest influence on the project. In addition, having a stakeholder analysis can determine which stakeholders should be considered throughout the project development. With this part of the document, the project team could identify stakeholders that need prioritization so that they would know how to communicate with them throughout the project's development. The table listed identifies the project stakeholders which shows their corresponding impact on the project.

Name	Power	Interest	Roles	Stakeholder Contribution	Strategic Engagement on Stakeholder
Ms. Devilyn Ligligen	High/High	High	Project Sponsor/Internal User of the system	Approval of the Project and usage of the system	Schedule meetings
Cashier	Low/High	High	Internal user of the system	Usage of the system	Schedule meetings
Ramon Benedict Elloso	High/High	High	Project Manager	Manage the team and project development	Schedule meetings
Carlos Ligligen	Low/High	High	Back-End Developer	Create the back-end system	Schedule meetings
Andrei Gabriel Palma	Low/High	High	QA (Quality Assurance) Tester	Test functionality and usability of the system	Schedule meetings
Donne Paolo Tarinay	Low/High	High	Front-End Developer	Create the front-end of the system	Schedule meetings
Customer	Low/High	Low	---	---	---

With a pen and paper, the Bregghan Mini Grocery business now maintains track of the sales that enter and exit the business each day. The store's current point-of-sale system also relies on handwritten receipts and manual calculations. The stocks are only restocked when they discover that an item is already critical on count, and the fast- and slow-moving items at the mini-grocery store are not being effectively tracked.

In order to build a strong foundation for the project objective and the deliverables that will be reached within each sprint, the team gathered as many requirements from the client as possible before implementing the project objectives. This was done to learn more about the circumstances of the Bregghan Mini-Market. Additionally, the store only uses receipt records to keep track of sales and inventory, which is laborious for the employees because they must maintain the receipts to know what stock is still in stock and because they solely rely on the information contained in those receipts. By integrating a stock and sales responsive webapp, the group hopes to improve their current system and improve the store's inventory management and point of sale.Therefore, the digitization of the mini grocery stores' sales activities should be visible by the project's or deployment's conclusion, making it easier for customers to utilize and calculate all the items they purchase. The project's deliverables include mostly liveupdated documentation and progress reports, as well as the finished product itself.

The scope approach of the project team ensures that every deliverable will be given in allotted time to the business owner. The client's criteria, which include a system that allows users to efficiently obtain copies of the goods that are sold, a sales and stock tracer, and other requirements, are the only ones that can be included in the project's management scope.

As for who has the authority and responsibility, the product manager is held accountable for the outcomes as for the scope measure to when we can call it verified for deployment. The project will reach the completion stage once all inquiries of the client are met and all commands that are developed by the project team are implemented from back to front end. The project deliverables are verified or approved by the client and the project manager before final changes.

Project Team	Roles	Responsibilities
Ms. Devilyn C. Ligligen	Project Stakeholder	Review deliverables provided by the team within specified dates.
Ramon Benedict Elloso	Project Manager	Responsible for overseeing and coordinating all aspects of the project, ensuring its successful planning, execution, and completion.
Carlos Ligligen	Back-end Developer	Develop the back-end architecture and ensure the proper functioning of the server, database, and APIs (Applications Programming Interface).
Andrei Gabriel Palma	Quality Assurance Tester	Identifying and reporting bugs, conducting various testing methodologies, and collaborating with the development team to resolve any issues.
Done Paolo Tarinay	Front-end Developer	Responsible for creating the user interface and user experience of a website or application.

The project’s scope is limited to the requirements which are provided by the client which is the sales and stock tracer and a system wherein the user can have a copy of the items that are sold in an efficient way, and both need to be in an application. The project focuses on addressing the pain points of the Bregghan mini grocery store which is the lack of monitoring in sales, stocks, and they are limited to pen and paper only. In addition, the store only uses the receipts as a basis to track the stocks and the items that are sold.

The project team used meetings, whether they were physical or virtual, to conduct instructions and more clear points to be taken from the project adviser to consider during the sprint of the project and finalize the scope that the project should aim for. In order for project deliverables to meet the date need, the project group followed project management steps from planning to executing. In terms of the project's documentation, the team updates any modifications made during consultations with the adviser or the customer to make sure that each stage of development is monitored before the finished product is delivered. As for the analysis of the product the use of the POS system was widely used as center for the project as the main goal being to digitize and benefit the client with an application that would help keep track of operations inside the bregghan mini grocery store.

Project Scope Description	• To develop a responsive web application that digitizes the recording of stocks and sales, automates computation of sold items, and produces reports. By implementing this solution, the staff and manager of Bregghan mini grocery store will be able to monitor stocks and sales in real-time, reducing workload and minimizing human error. This will lead to more efficient inventory management and faster checkouts, resulting in improved customer satisfaction. The system will also provide alerts when stock levels reach a critical point, allowing the store to replenish inventory on time and avoid potential revenue loss due to out-of-stock items. Furthermore, the application's capability to produce detailed sales reports will provide useful insights to the business, allowing for data-driven decision-making to further optimize operations and profitability.
Project Acceptance Criteria	• Functionality: The POS system should have a comprehensive set of features and capabilities to support various sales transactions, including inventory management, product catalog management, and reporting. It should accurately calculate prices, handle discounts and promotions, manage stock levels, and generate receipts. Reliability: The POS system should consistently perform its intended functions without errors or disruptions. It should be available for use during store operating hours and should not encounter frequent system crashes or downtime that would impact business operations. The system should be designed to handle high transaction volumes without compromising its performance. Usability: The design of the POS system should prioritize a user-friendly interface and easy-to-use navigation. It should enable store employees to quickly grasp its operation and carry out their responsibilities with efficiency. The system should provide clear guidance, logical workflows, and visual cues that facilitate smooth navigation through its diverse functions. Performance: The POS system should ensure optimal performance, with quick response times for processing transactions, executing search queries, and generating reports. The system should be capable of handling high transaction volumes during peak periods without compromising its efficiency.
Project Deliverables	To develop a responsive web application that accurately tracks sales and inventory for Bregghan mini grocery store, enabling real-time monitoring and reporting. Decreases the number of steps that the user can do in the whole transaction for faster checkouts. To fully digitize the recording of stocks and sales for Bregghan mini grocery store, ensuring that all inventory and sales transactions are accurately captured and stored electronically. To implement a notification system that alerts the user when stock levels reach a critical threshold, ensuring timely replenishment and avoiding stockouts. To automate the computation of sold items, ensuring accurate and efficient tracking of sales data.
Project Exclusions	The project cannot exceed a certain budget, which may limit the scope or timeline of the project. The project must be completed within the designated timestamp of the subject course Project Management. The project must comply with specific laws, regulations, or standards that may limit the project's scope or approach. The project may be limited by the available technology or infrastructure.
Project Constraints	Budget constraints: The project cannot exceed a certain budget, which may limit the scope or timeline of the project. Time constraints: The project must be completed within the designated timestamp.
Project Assumptions	All necessary funding and resources will be secured and available for the project's duration. All stakeholders will be available and able to provide input as needed throughout the project lifecycle. There will be no major technological or market disruptions that would impact on the project's success. The project team will have the necessary expertise and skill sets to complete the project successfully.

The Work Breakdown Structure (WBS) is a hierarchical representation of the project scope that divides the project into smaller, more manageable components. Each level in the WBS represents a progressively more detailed view of the project, starting with the highest level and moving down to the lowest level.

Bregghan Point of Sale System

1.1 Project Initation
1.1.1 Business Case
1.1.2 Feasibility Study
1.1.3 Project Charter
1.1.4 Identify Stakeholders
1.1.5 Final Review

1.2 Project Planning
1.2.1 Project Description
1.2.2 Cost Management Plan
1.2.3 Schedule Management Plan
1.2.4 Scope Management Plan

1.3 Phase I: Analysis
1.3.1 Project Risk Analysis
1.3.2 Cost Benefit Analysis

1.4 Phase II: Design and Development
1.4.1 Admin System
1.4.1.1 Admin Log-in
1.4.1.2 Admin Home Page
1.4.1.3 Inventory
1.4.1.4 Transactions
1.4.1.5 Analytics Report
1.4.2 Point of Sale System
1.4.2.1 Cashier Log-in
1.4.2.2 Home Screen
1.4.2.3 Checkout Screen
1.4.2.4 Generate Receipt 

1.5 Phase III: Testing

1.5.1 Requirements Analysis

1.5.2 Test Planning

1.5.3 Test Design

1.5.4 Test Execution /ul>
1.5.5 Test Evaluation
1.5.6 System Integration Testing
1.5.7 User Acceptance Testing
1.5.8 System Testing

1.6 Phase IV: Implementation
1.6.1 Deployment Planning
1.6.2 Installation
1.6.3 Data Migration
1.6.4 User Training
1.6.5 Monitor Progress
1.6.6 Post Implementation Review

1.7 Project Closeout/Completion
1.7.1 Finalize Project Deliverables 
1.7.2 Confirm Project Completion
1.7.3 Review All Contracts
1.7.4 Review Documentation

This section is verifying Bregghan Point of Sales System to match with the features allocated by the project team Aurora. It ensures that every detail that is within the scope and objectives as well as specifications of the project will be met by the end of the project sprint and will be able to provide satisfactory results to the client the verification process is to be discussed by the project team as well as the project stakeholders.

Furthermore, Inspection of the final output will be done regularly by the developers to ensure that all features and programs will work accordingly to the original blueprint to compare, a thorough understanding of the scope and the actual deliverable is necessary. Following the inspection process to be done by the project team a set of factors like quality and performance measurements should be considered to provide consistency with the product structure and will reach acceptance rate by the project stakeholders.

The Scope Control of the project as stated from the verification shows how the product will undergo different series of inspection by the project team, developers, stakeholders, and project manager. This part covers every aspect of the final product, including its features, functionalities, service, and quality. The project team also ensures that the product is regularly inspected to ensure that all developer-specified goals are achieved by the conclusion of the sprint.

During the inspection that will be done by the project team whenever there would be changes that needs to be conducted within the product the project manager will be the one tasked to ensure the monitoring of the progress should there be one and with the collaboration from the stakeholders as well as the developers and that any changes to the system should be documented to keep track of the output milestones however not any changes will be based on the project manager. The stakeholders, developers, and the project team can also inquire about changes they think that can improve the user experience of the client by the time the project is released and to also brainstorm every aspect that needs to be improved during this stage.

The Cost Management Plan is developed to ensure effective management of project costs throughout the project's lifecycle. It outlines the procedures and guidelines for measuring, reporting, and controlling costs associated with the Bregghan Store Point of Sale System. This plan's purpose is to identify the cost management approach, roles and responsibilities, and procedures for managing costs consistently and effectively.

This plan is to establish a systematic method for efficiently overseeing and regulating the financial components of the POS (Point of Sale) system project. It empowers Bregghan to make well-informed choices, optimize the allocation of resources, and guarantee that the project is accomplished within the set budgetary limitations.

The cost management approach for the Bregghan Store POS project will be to ensure that all costs are identified and monitored throughout the project lifecycle. This will be done by tracking all costs associated with the project and comparing them against the project budget. Any deviations from the budget will be analyzed, and corrective action will be taken to keep costs within the approved budget.

The cost management approach for Bregghan Store POS System will be based on the following principles:

Clear definition of costs

This will create and establish an estimate financial resource required for the POS system implementation. It ensures that all relevant expenses are identified and accounted for, enabling us to develop a realistic budget.

Budget development and tracking

This involves creating a comprehensive budget plan that will help set clear financial parameters and constraints for the POS system project. It involves estimating the costs associated with hardware, software, licensing, implementation, training, maintenance, and any other relevant expenses. By defining the budget, this will determine the financial boundaries within which the project should be executed.

Cost estimates

By having a clear understanding of the anticipated costs, this will evaluate different options, assess their financial feasibility, and select the most suitable solutions for the POS system

Cost variance analysis

Through the comparison of actual incurred costs and budgeted costs, this will evaluate the project's alignment with the intended financial plan. This assessment allows for a comprehensive understanding of the project's effective management of financial resources.

Cost management roles and responsibilities

This guarantees that every team member understands their individual responsibilities in overseeing costs. With clearly defined roles, team members can actively participate in activities such as estimating costs, creating budgets, tracking expenses, and implementing cost control measures.

Approval process for changes

By establishing an approval process, this can thoroughly assess and evaluate any suggested modifications to the project's scope, requirements, or budget to determine their potential cost implications. This structured approach enables a thorough examination of the financial consequences before proceeding with any changes.

Reporting and communication

This allows for timely decision-making, as stakeholders can assess the financial health of the project and take necessary actions if deviations from the plan occur. Additionally, clear communication channels enable effective coordination and collaboration among team members, ensuring that everyone is aligned with the project's financial goals and responsibilities.

The Cost Management Plan for the Bregghan POS System project will include a detailed approach for measuring project costs using Earned Value Management (EVM). This will include analyzing and reporting on various Earned Value metrics, such as:

The project team intends to assess the project's schedule performance by computing the Schedule Variance (SV) through subtracting the Planned Value (PV) from the Earned Value (EV). The Earned Value refers to the actual value obtained in the project, while the PV pertains to the value anticipated in the project plan for the current point. By considering the deviation between the planned and actual value, the project team can determine if the project is on schedule, ahead of schedule, or behind schedule, according to the baseline schedule in the project plan.

The team will determine the project's budget performance by calculating the Cost Variance (CV), obtained by subtracting Actual Costs (AC) from Earned Value (EV). EV represents the actual value earned in the project, while AC reflects the actual costs incurred to date. Therefore, by subtracting the actual costs from the EV, the team can determine whether the budget is above or below budget. If the CV is zero, it means the project is on budget. A CV greater than zero indicates that you are earning more value than planned, and the project is under budget.

Thea team will use Schedule Performance Index (SPI) to evaluate the actual progress made against the planned progress. It is calculated by dividing EV by PV. If the value of EV is equal to PV, then the SPI is 1. If EV is lower than PV, the SPI is less than 1, indicating the project is behind schedule. If EV is greater than PV, the SPI is greater than 1, indicating the project is ahead of schedule. An efficient project should have an SPI that is as close to 1 as possible, or even slightly below 1.

The team will utilize the Cost Performance Index (CPI) to contrast the value of completed work with the corresponding actual cost. The CPI is calculated using the formula EV/AC, with EV denoting the actual value achieved in the project and AC representing the total actual costs incurred thus far. If the CPI equals 1, the project is within the budgetary confines. If the CPI surpasses 1, the project is operating under the budget, while a CPI below 1 indicates that the project is exceeding the budget.

The team will provide provides a structured and standardized way to communicate cost-related information within the project.

The report will include the following:

1. Earned Value Metrics

Cost Performance Index (CPI): [CPI]

Schedule Performance Index (SPI): [SPI]

Cost Variance (CV): [CV]

Schedule Variance (SV): [SV]

The monthly project status report will feature a specific segment dedicated to cost management. Within this section, the report will display the earned value metrics, including the cost performance index (CPI), schedule performance index (SPI), cost variance (CV), and schedule variance (SV).

2. Cost Variances

Any cost variances outside the thresholds specified in the Cost Management Plan will be reported, including the following details:

Description of the variance

Magnitude of the variance

Impact on project budget

Planned corrective actions to address the variance.

Any cost discrepancies that surpass the predetermined thresholds outlined in the Cost Management Plan will be documented and reported. This includes providing a detailed explanation of the variance, quantifying its magnitude, assessing its impact on the project budget, and outlining the corrective actions that are planned to address the deviation.

3. Change Requests

Change Requests triggered by project cost overruns will be identified and tracked in this report, including the following details:

Description of the change request

Reason for the change

Estimated impact on project cost.

Status and progress of the change request

Any change requests triggered by cost overruns will be identified and tracked, including their description, reason, estimated impact on project cost, and status. The report will also summarize the overall project cost, including the total budgeted cost, actual cost incurred to date, remaining budget, and estimated cost at completion.

4. Summary

Provide a summary of the cost management status and any significant findings or observations related to project costs.

5. Attachments

Include any relevant supporting documents or reports related to cost management.

The Cost Variance Response Process for the Point-of-Sale System project is outlined below:

Identify and Assess Cost Variances

The project team reviews the financial information and evaluates it in relation to the predefined thresholds or benchmarks outlined in the Cost Management Plan. When there is a substantial difference between the actual costs and the planned budget, it signifies the presence of a cost variance.

Analyze the Causes

The project team will examine the underlying causes and investigate various elements such as changes in scope, unexpected expenses, resource allocation issues, inaccurate cost estimations, or external factors impacting the project budget.

Assess the Impact

Assess the consequences of the cost variances on the project's schedule, resources, and overall goals while considering the potential impact on other project constraints, including quality, scope, and stakeholder contentment.

Develop Corrective Actions

After analyzing the root causes and evaluating the consequences, the project team will identify and outline precise corrective measures to tackle the cost variances. These measures might involve modifying the budget, reallocating resources, reevaluating the project scope, or implementing cost-reduction strategies.

Implement Corrective Actions

The project team must implement the defined corrective actions and closely monitor their efficacy in mitigating or resolving the cost variances. This could entail adjusting the project plan, reallocating resources, renegotiating contracts, or pursuing additional funding if required

Monitor and Control

The project will have to monitor and regularly observe its financial progress and assess the impact of the applied corrective measures through ongoing monitoring.

The cost change control process will adhere to the existing procedure for project change requests. The team will ensure that any proposed changes related to project budget or costs are carefully evaluated, documented, and reviewed by relevant stakeholders.

Identification of Change

All suggested alterations that could affect the project's expenses are recognized and recorded. This encompasses modifications to the project's scope, requirements, resources, or any other aspect that could potentially result in financial consequences. Any proposed changes to the project budget or costs must be submitted to the project manager in writing using the Cost Change Request Form.

Change Assessment

The proposed change is assessed to determine its impact on the project budget. A comprehensive analysis is performed to gauge the financial implications, considering the potential increase or decrease in costs.

Cost Estimation

The project team evaluates the monetary consequences of the suggested alteration. This entails estimating the direct and indirect expenses linked to implementing the change, considering factors such as labor, materials, equipment, and overhead costs.

Cost Analysis

The analyzed cost estimates are examined to comprehend the broader effect on the project's budget. This examination aids in evaluating the practicality of the change and its alignment with the project's financial goals.

Approval Process

The proposed change is presented for approval using the established change management process. Relevant stakeholders such as project sponsor and key decision-makers evaluate the change request and decide considering its impact, feasibility, and alignment with the project's financial limitations.

Implementation

Once the change receives approval, it is executed following the agreed-upon protocols. This could entail modifying the project plan, adjusting the budget, reallocating resources, or undertaking any required measures to accommodate the approved change.

Documentation

All changes, including the associated costs, approvals, and implementation details, are documented for future reference. This documentation helps in maintaining an accurate record of cost changes and provides a historical reference for similar situations in the future.

The budget for this project is detailed below. Costs for this project are presented in various categories:

Approved Budget	₱ 1,000,000.00
Manpower Cost	₱ 546,240.00
Hardware Cost	₱ 178,418.00
Software Cost	₱ 3,654.00
Contingency Cost:	₱ 36,415.60
Total Project Cost:	₱ 764,727.60

The Schedule Management Plan offers instructions for creating, tracking, and managing the project schedule. It contains details on the schedule creation, identifying project milestones, tracking, and reporting progress, and managing schedule adjustments. The schedule management plan will also include how the team will monitor the project’s schedule and manage the changes in accordance with the approved baseline schedule.

This schedule management approach creates an outline for the processes used for the project. This section of the paper will also ensure that the project will be completed on time, within the given budget, and the client's features and requirements are met. All changes to the project schedule will be communicated to the stakeholders promptly. To ensure that the project is on time and in adherence to the schedule, monitoring of the project should be implemented.

Regular meetings are required for the team to discuss all the progress and address any issue that may arise.

The assigned project manager will be responsible for the regular status reports to all stakeholders and the project sponsor for them to be informed about the project's progress.

The assigned project manager will be responsible for monitoring the project’s progress regarding the schedule, budget, issues, potential delays, and risk mitigation.

The project team will utilize software on project management to attain a strong adherence to the deadlines.

The schedule control will ensure that the schedule is being followed and maintained by the team in accordance with the project’s progress. The procedure the team will incorporate to manage the project's schedule control is schedule reporting.

The team’s project schedule will be constantly monitored by the project manager and the stakeholder. With this, any changes will be constantly reviewed. In addition, the project manager is also responsible for the updates with regards to the meetings, reports, and schedule.

The project team is also responsible for the weekly updates in coordination with the project manager. Furthermore, they are the ones that will communicate any changes of dates to the project manager.

The project stakeholder is responsible for maintaining awareness of the project schedule and will review or approve any changes that might occur in the future in collaboration with the project manager.

The team process to control the project schedule is by using schedule reporting. This will be done in a weekly basis and should adhere to the following:

• Report of the members stating the percentage of their task completion within a given time.
• Weekly team meetings
• Risk and mitigation strategies raised by the project team members
• Communication with stakeholders every week

All the changes that will occur or be raised will be reviewed by the project manager, and he will request a meeting with the team and the stakeholders for the change's evaluation. With these, before a change is implemented, its effects on the project schedule and other project parameters must be assessed. After the assessment of the change, the project manager will determine if the changes should be addressed and will proceed to the submission of the schedule change request which can be found at the end of this document. Only the project manager can submit the schedule change request form to the stakeholder/project sponsor. Once done, the project manager must inform the project team members about the changes and must update the project schedule.

Submittal of a schedule request change request to the project stakeholder for approval is required if either of the following conditions is true:

• The proposed modification will either result in an individual work package's duration increasing or decreasing by 10% or more.
• If the approach will reduce or increase the project’s duration with regards to the schedule by 10%.

With the establishment of processes and thresholds for the schedule changes, the team will have control over the project’s progress. Furthermore, having these will ensure that all the changes will be monitored, reviewed, and will be addressed in a timely manner.

All changes in project scope approved by the project sponsor will require the team to assess the scope change's effect in the current schedule. The proposal of a change would be possible is when a problem develops in the project that necessitates a significant modification of the project scope. Furthermore, any change should be approached by the team with caution as any outcome would positively or negatively affect the project’s progress. The changes can be raised by any team member and the project stakeholder must receive all the change requests in the form of a project change request document.

The Work Breakdown Structure (WBS) is a vital project management tool that offers a structured method for organizing and overseeing project deliverables, tasks, and subtasks. This introductory section seeks to provide a thorough understanding of the WBS, its objectives, and the advantages it offers in project planning and execution. The main goal of introducing the WBS is to establish a shared understanding among stakeholders, project managers, and team members regarding the importance of the WBS. It highlights the significance of developing a well-organized WBS, which acts as a guide for achieving project success.

The Outline view in a Work Breakdown Structure (WBS) presents a hierarchical depiction of the project's deliverables, tasks, and subtasks. It provides a structured and systematic approach to dividing the project scope into manageable parts, enhancing the ability to plan, track, and manage the project effectively.

Bregghan Point of Sale System

1.1 Project Initation
1.1.1 Business Case
1.1.2 Feasibility Study
1.1.3 Project Charter
1.1.4 Identify Stakeholders
1.1.5 Final Review

1.2 Project Planning
1.2.1 Project Description
1.2.2 Cost Management Plan
1.2.3 Schedule Management Plan
1.2.4 Scope Management Plan

1.3 Phase I: Analysis
1.3.1 Project Risk Analysis
1.3.2 Cost Benefit Analysis

1.4 Phase II: Design and Development
1.4.1 Admin System
1.4.1.1 Admin Log-in
1.4.1.2 Admin Home Page
1.4.1.3 Inventory
1.4.1.4 Transactions
1.4.1.5 Analytics Report
1.4.2 Point of Sale System
1.4.2.1 Cashier Log-in
1.4.2.2 Home Screen
1.4.2.3 Checkout Screen
1.4.2.4 Generate Receipt 

1.5 Phase III: Testing

1.5.1 Requirements Analysis

1.5.2 Test Planning

1.5.3 Test Design

1.5.4 Test Execution /ul>
1.5.5 Test Evaluation
1.5.6 System Integration Testing
1.5.7 User Acceptance Testing
1.5.8 System Testing

1.6 Phase IV: Implementation
1.6.1 Deployment Planning
1.6.2 Installation
1.6.3 Data Migration
1.6.4 User Training
1.6.5 Monitor Progress
1.6.6 Post Implementation Review

1.7 Project Closeout/Completion
1.7.1 Finalize Project Deliverables 
1.7.2 Confirm Project Completion
1.7.3 Review All Contracts
1.7.4 Review Documentation

The hierarchal structure is similar to the outline view but without indentation. The hierarchal structure is similar to the outline view but without indentation. This is divided using level, WBS Code and Element Name.

Level	WBS Code	Element Name
2	1.1	Project Initiation
3	1.1.1	Business Case
3	1.1.2	Feasibility Study
3	1.1.3	Project Charter
3	1.1.4	Identify Stakeholders
3	1.1.5	Final Review
2	1.2	Project Planning and Preparation
3	1.2.1	Project Description
3	1.2.2	Cost Management Plan
3	1.2.3	Schedule Management Plan
3	1.2.4	Scope Management Plan
2	1.3	Phase I: Analysis
3	1.3.1	Project Risk Analysis
3	1.3.2	Cost Benefit Analysis
2	1.4	Phase II: Design and Development
3	1.3.1	Comments Matrix
3	1.4.1	Admin System
4	1.4.1.1	Admin Log-in
4	1.4.1.2	Admin Home Page
4	1.4.1.3	Inventory
4	1.4.1.4	Transactions
4	1.4.1.5	Analytics Report
3	1.4.2	Point of Sale
4	1.4.2.2	Home Screen
4	1.4.2.3	Checkout Screen
4	1.4.2.4	Generate Receipt
2	1.5	Phase III: Testing
3	1.5.1	Requirement Analysis
3	1.5.2	Test Planning
3	1.5.3	Test Design
3	1.5.4	Test Execution
3	1.5.5	Test Evaluation
3	1.5.6	System Integration Testing
3	1.5.7	User Acceptance Testing
3	1.5.8	System Testing
2	1.6	Phase IV: Implementation
3	1.6.1	Deployment Planning
3	1.6.2	Installation
3	1.6.3	Data Migration
3	1.6.4	User Training
3	1.6.4/p>	Creation of Component and Deployment Diagram
3	1.6.5	Monitor Progress
3	1.6.6	Post Implementation Review
2	1.7	Project Closeout/Completion
3	1.7.1	Finalize Project Deliverables
3	1.7.2	Confirm Project Completion
3	1.7.3	Review All Contracts
3	1.7.4	Review Documentation

The Tree Structure View is the most popular format for the WBS. It presents an easy to understand view into the WBS; however, it is also tricky to create without an application specifically designed for creating this organizational chart structure. The Tree Structure below was created using only Microsoft Word and the SmartArt graphics option under the insert menu.

This section outlines the strategies and practices necessary to effectively manage the human resources involved in the project. By aligning the project's goals with the skills and expertise of the team members, the Human Resource Management Plan ensures the project is staffed with the right individuals, promotes a collaborative work environment, and supports the achievement of project objectives.

By utilizing this strategy, the project manager and team can efficiently oversee the project by guaranteeing that each team member comprehends their tasks and obligations, promoting transparent and efficient communication, and monitoring and handling performance in a manner that contributes to the overall achievement of the project.

An effective human resource plan is necessary for the execution of the Bregghan Point-of-Sale project. This will ensure the project team has the appropriate skills and expertise to effectively execute the project. By clearly defining roles and responsibilities, the human resource plan helps minimize confusion, improve coordination and collaboration among team members, and increase overall project efficiency. It also facilitates effective communication and accountability within the project team, leading to better project outcomes.

</tr>

Roles	Authority	Responsibility	Competency
Project Sponsor	The project sponsor plays a role in endorsing the project's business case and budget, offering strategic guidance, allocating resources, facilitating stakeholder support, and resolving significant challenges and disputes.	Make critical decisions related to the project, including approving the project's initiation, scope, and major changes. Provide guidance and direction to the project manager, endorse the allocation of resources, and facilitate stakeholder engagement.	Have a diverse set of skills and abilities that allow them to effectively carry out their responsibilities. These encompass exceptional leadership and persuasive skills, strategic thinking, the capability to align projects with organizational objectives, expertise in stakeholder management and communication, financial proficiency, and a comprehensive understanding of the organization's operations and industry.
Project Manager	Overseeing and managing the entire project from initiation to completion.	Make decisions and take necessary actions within the project's scope. Have the power to allocate resources, set timelines, and enforce project policies and procedures.	Accountable for the project's outcomes and ensuring that it meets its objectives. Responsible for creating a project plan, defining deliverables, managing risks, and ensuring that the project is executed within budget and on schedule.
Frond-end Developer	Responsible for creating the user interface and user experience of a website or application.	They have the authority to design and implement the visual elements, layout, and interactivity, ensuring a seamless and visually appealing user interface.	It is crucial for a front-end developer to possess strong coding skills, proficiency in front-end technologies such as HTML, CSS, and JavaScript, and a deep understanding of user-centered design principles to effectively fulfill their role.
Back-end Developer	Accountable for creating and executing the server-side logic and database features of a website or application.	Develop the back-end architecture and ensure the proper functioning of the server, database, and APIs (Applications Programming Interface).	Proficiency in programming languages such as Java, Python, or PHP, database management, server administration, and problem-solving skills to handle complex back-end operations and ensure smooth data processing and retrieval.
Quality Assurance Tester	Evaluate and test software applications or systems to ensure they meet quality standards and requirements.	Identifying and reporting bugs, conducting various testing methodologies, and collaborating with the development team to resolve any issues.	Strong analytical skills, attention to detail, proficiency in testing tools and techniques, and the ability to effectively communicate and document test results.
Manager (User of Admin System)	Holds the responsibility of overseeing the entire store's operations, which encompass sales and inventory tracking, facilitated by the digitized system. The manager plays a vital role in fostering efficiency, enhancing inventory management, boosting sales, improving the customer experience, and upholding a competitive edge	The manager possesses significant decision-making power concerning the admin system, exerting high authority in this regard. They are accountable for making strategic choices concerning the system's implementation, customization, and utilization. Additionally, the manager has the authority to allocate resources efficiently, encompassing budgetary decisions for the system's implementation and ongoing maintenance.	Responsible for providing guidance and support to the staff in utilizing the admin system, ensuring that it is used to its full potential. They are also responsible for tracking key performance indicators, analyzing data generated by the system, and making informed decisions based on the insights obtained.
Staff (User of POS (Point of Sale) System)	Responsible for utilizing the system to process customer transactions, manage inventory, and provide accurate sales information.	The staff members have the authority to access and operate the POS system within their designated roles. They can perform tasks such as scanning products, processing payments, updating inventory levels, and generating sales reports.	The staff members are responsible for using the POS system accurately and efficiently. This includes ensuring that all customer transactions are processed correctly, maintaining accurate inventory records, and promptly reporting any system issues or discrepancies to the manager.

This portion offers a visual representation of the Bregghan Point-of-Sale System project's tasks and team members. The objective is to demonstrate the responsibilities of each team member in relation to the project tasks. The Business owner oversees managing the admin system and the project’s overall success. Next in line is the Project Manager who oversees the entire project from initiation up to the completion phase of the project. Additionally, the front end and back-end developers of the project team are responsible for creating the Bregghan Point-of-Sale System that will be used by the store manager and the cashier of the Bregghan store. The organizational chart functions as a valuable resource for defining the duties and obligations of each team member, encouraging synchronization with the project's goals, and facilitating efficient teamwork.

The Staffing Management Plan is a vital element of the Bregghan Point-of-Sale system project, playing a crucial role in its effective implementation. It details the approaches and procedures for acquiring, overseeing, and releasing human resources during the various stages of the project

The staffing management plan will outline the process for acquiring the necessary human resources for the POS project. This includes determining the required skill sets, job roles, and responsibilities, and identifying the recruitment methods to attract qualified candidates.

The staffing management plan will address any skill gaps identified among the project team members. It will define the training and development programs to enhance their skills and ensure they have the necessary competencies to perform their roles effectively.

The plan will establish a framework for conducting performance reviews to assess the individual and team performance on the project. It will outline the criteria for evaluation, the frequency of reviews, and the process for providing feedback to team members

The staffing management plan will include a rewards and recognition system to motivate and acknowledge the achievements of team members. It will define the criteria for rewards, such as bonuses or promotions, and outline the process for recognizing exceptional performance.

Roles	Project Responsibility	Skills Required	Performance Reviews	Recognition and Rewards
Project Team Leader	Responsible for overseeing and coordinating all aspects of the project, ensuring its successful planning, execution, and completion.	Being a project team leader requires strong leadership, communication, and problem-solving skills, and the ability to effectively manage resources, mitigate risks, and drive project progress.	Assess the ability to effectively lead the team, meet project objectives, foster collaboration, and demonstrate strong decision-making and problem-solving skills.	Acknowledging their exceptional leadership, successful project delivery, and the ability to inspire and motivate team members, resulting in project success and positive outcomes.
Project Team Member	Actively participating in project activities, collaborating with team members, and delivering assigned tasks and deliverables within the given times.	Effective collaboration and communication skills, the ability to work well in a team environment, and a strong commitment to meeting project objectives and deadlines. This will also include skills like web development, database management, etc.	Assess each contribution to the project, adherence to deadlines, quality of work, teamwork, and their ability to meet project objectives.	Provide exceptional performance, dedication, teamwork, and valuable contributions to the project's success.

This plan intends to direct and aid in the smooth changeover from the existing system to a new innovative system. Bregghan will experience major change when a new POS (Point of Sale) system is implemented since it affects many distinct parts of operations, procedures, and personnel.

This Change Management Plan's objective is to present an organized plan that will aid in ensuring a seamless transition to the new POS system. It will offer a precise road map for dealing with change's difficulties, including stakeholders, and promoting the adoption and integration of the new system into routine operations. We want to reduce interruptions, increase user acceptability, and achieve the intended business objectives by actively managing the transition.

This Change Management Plan's objective is to present an organized plan that will aid in ensuring a seamless transition to the new POS system. It will offer a precise road map for dealing with change's difficulties, including stakeholders, and promoting the adoption and integration of the new system into routine operations. We want to reduce interruptions, increase user acceptability, and achieve the intended business objectives by actively managing the transition.

A crucial step in the change management procedure of an organization is the Change Control Board (CCB). It acts as a governing body charged for examining, assessing, and accepting or rejecting suggestions for modifications to the documentation inside a project or throughout the entire business. The main goal of the CCB is to make sure that all changes or updates to documents are well studied, in line with business objectives, and compliant with accepted standards and procedures. The table below shows the information of each stakeholder in charge of Change Control Board:

Change Control Board Role	Role	Name	Contact	Responsibilities
Change Control Board Chair	Project Sponsor	Ms. Devilyn C. Ligligen	[email protected]	Approve or deny high impact changes. Has the responsibility. To review the minimal impact changes and can overturn decisions made by the Project Manager about change requests.
Change Control Board Member	Project Manager	Ramon Benedict V. Elloso	[email protected]	Determines if the impact of the change request is high or low. Approve or deny minimal impact changes Responsible for formulating an action plan to implement change request if approved Communicates the required actions to implement the changes. Update the project plan, budget, and schedule as needed.
Change Control Board Member	Change coordinator	Carlos C. Ligligen	[email protected]	Ensures that the Change Management process is properly implemented. Responsible for updating the changes logs accordingly. Prepare change status report. Create a report at the end of each month summarizing the status of the contents of the change control logs

The responsibilities for each project participant during the change management process are listed in the following table:

Name	Project Role	Responsibilities
Ms. Devilyn C. Ligligen	Project Sponsor	Communicate the change message effectively to all stakeholders. Engage and influence stakeholders throughout the change process. Identify, assess, and manage risks associated with the change effort.
Store Manager	Internal user of the system	Test and quality assurance. Monitor the system performance and gather feedback.
Cashier Staff	Internal user of the system	Test and quality assurance. Monitor the system performance and gather feedback.
Ramon Benedict V. Elloso	Project Manager	Assess the impact of proposed changes on various aspects such as processes, systems, and personnel. Coordinate the implementation of changes, ensuring that they are executed according to plan and within specified timelines. Manage the entire change request process in collaboration with the Change Coordinator.
Carlos C. Ligligen	Back-End Developer	Review and understand proposed changes to the back-end systems. Collaborate with the project team to plan and implement back-end changes.
Andrei Gabriel B. Palma	QA (Quality Assurance) Tester	Review and understand proposed changes and their impact on the system.
Donne Paolo Y. Tarinay	Front-End Developer	Review and understand proposed changes to the back-end systems. Collaborate with the project team to plan and implement front-end changes.

The process of change control for a document encompasses a sequence of steps and protocols to effectively handle alterations, revisions, and updates to the document. It guarantees thorough review, approval, implementation, and communication of changes. Below is an outline of the change control process for a document:

Process step	Description	Change Log Status
Change Request Initiation	Any stakeholder who identifies the need for a change in the document will initiate a change request. This can be done by communicating through a meeting.	Submitted
Change Request Review	The change request will be reviewed by the project team. They evaluate the characteristics, consequences, and practicality of the suggested modifications.	In Review
Change Impact Assessment	A comprehensive evaluation is conducted to analyze how the proposed changes will affect the document. This assessment encompasses an examination of their potential impact on the project schedule.	In Review
Approval	Change control board reviews and grants approval for the change request, ensuring that the proposed modifications are in accordance with organizational standards, regulatory obligations, and document management policies.	Approved or Denied
Change Implementation	After receiving approval for the change request, the document undergoes the necessary modifications.	Ready for Implementation

To monitor the progress of change requests, each step is associated with a specific status, as indicated in the table provided below:

Status	Description
Submitted	A change request log submitted by a member of the project team or key stakeholders awaits review by the Change Control Board to perform an impact analysis.
In Review	An analysis is being conducted to assess the potential impact
Status	Description
Approved	The change request has received approval and is now ready for implementation
Denied	The change request has been rejected.
Ready for Implementation	The change request is prepared and ready to be implemented.

The communication management plan will provide a structured approach for managing ang controlling project communications. Furthermore, it will help guarantee that all the information delivered to the stakeholders are true, accurate, and correct by using the most effective communication channels. With this, the team can mitigate risks, engage more with the stakeholder, and improve coordination.

This document also supports the processes for communication which can help minimize misunderstandings and facilitate project success. Furthermore, it defines the communication methods, key messages, and certain expectations on how the communication will flow. With this document, the team can identify which type of communication best suits a specific scenario for an effective communication within the project and ensure that every information conveyed to the stakeholders is true and correct.

The Communications Management Approach will be handled by the project manager and will ensure effective communication in the project. Furthermore, the project manager will ensure foreseeing the project and reporting the performance of each team member. He will also be responsible for seeing with the project stakeholders and is responsible for organizing meetings, meetings with the team members, and implementing a project plan.

The main communication zone for the team would be the creation of a team in Microsoft Teams in which all the documentation, minutes of the meeting, and status reports would be placed. Moreover, implementing this would ensure that all the team members would collaborate with each other in terms of accomplishing their tasks and at the same time adhere to the deadlines. With this, the project manager can convey all the necessary information to ensure stakeholder satisfaction.

Effective project-related communications will be made possible by the project manager. The project manager will be held responsible for monitoring the project and reporting on its progress to the project team members and stakeholders. With this, there are some constraints that might hinder the project's progress, and it is important to identify these for the project manager and the team to produce risk mitigation. Some of the constraints that could limit the communication process among the stakeholders are within these factors:

Stakeholder availability

With busy schedules and conflicting priorities, project stakeholders might find it difficult to attend meetings which can hinder the team in obtaining feedback which might lead to delayed communication.

Time constraints

This factor might affect the communication process of the team and the project due to the strict adherence to the deadlines, it can limit the communication activities which can result in a limited opportunity. These things are spending more time on meetings for in-depth discussions which can have an impact resulting in more comprehensive communication.

Technical issues

This would affect the communication process as there would be times when online meetings are necessary. Some of the factors that affect this would be the internet connection, the condition of the device, and the technological experience.

The stakeholder communication requirements emphasize identifying the guidelines needed for effective communication throughout the project. Moreover, this part of the document will show all the requirements needed to build trust, credibility, and satisfaction among stakeholders. These are the things that are necessary to be standardized to attain a better relationship with the stakeholders:

Ensure information accuracy and relevance

The project team should understand and identify the specific needs of each stakeholder and it should be tailored within their interests, responsibilities, and roles. Furthermore, only the relevant information should be conveyed to each stakeholder to ensure confidentiality.

Identify the communication channels

Identify the most effective communication channels for the stakeholders. This would ensure the project team had a better engagement with the stakeholders.

Give rapid regular updates

This would ensure that all the possible risks that might arise are conveyed to the stakeholders as soon as possible. Furthermore, this would also guarantee that all necessary or relevant information is conveyed to the stakeholders promptly.

Project Sponsor The project sponsor is one of the key stakeholders which provides support for the project. They are also responsible for reviewing any changes to the project. Furthermore, they provide finances and processes necessary for the direction of the project. Lastly, their involvement and support are vital for the project’s successful completion.

Project Manager The project manager is the one that plans, executes, and oversees the successful completion of the project. He/she is also responsible for maintaining the schedule, scope, budget, and the resources. In addition, their role is vital to the project team coordination as they will convey all the necessary requirements and critical decisions that would lead to a successful project. Lastly, their role is vital in communication with project stakeholders as they will be the ones that will convey all the changes and updates. The project manager is also responsible for all the documentation needed for the project. He/she is the one that gives updates that might occur in the project development. Furthermore, their role is to ensure that all the documentation in the project lifecycle is up to date, accurate, and accessible.

Development Team The development team are the ones responsible for implementing the technical aspects of the project. They are the ones responsible for developing, testing, and designing the project. Furthermore, their role is to ensure that the project’s vision will turn into reality. Lastly, their task is to achieve the project’s objectives.

The following table presents contact information for all persons identified in this communications management plan. The email addresses and phone numbers in this table will be used to communicate with these people.

Roles	Name	Title	Type of Stakeholder	Email
Project Sponsor	Ms. Devilyn Ligligen	Bregghan Mini Grocery store owner	Internal	[email protected]
Project Manamer	Ramon Benedict Elloso	Project Manager	Internal	[email protected]
Development Team	Donne Paolo Tarinay	Front–end developer	Internal	[email protected]
Development Team	Carlos Ligligen	Back-end developer	Internal	[email protected]
Development Team	Andrei Gabriel Palma	Quality Assurance Tester	Internal	[email protected]

For effective communication with the stakeholders, the project team needs consistent communication, especially when it comes to meetings. With this, misunderstandings would be prevented, and better relationships or rapport will be established between the stakeholders and the project team. In addition, constant updates and the project team being open with each other, including the stakeholders, will result in a decent work environment which can result in giving the best quality output. With this relationship, the project team members can give timely updates and offer the stakeholders a better understanding of project development.

Having the necessary utilities such as project management software and Microsoft Teams will help the project team in conveying all the necessary information to the stakeholders for them to be updated and satisfied.

Some of the factors determined to have the best communication methods are:

Budget Aligned: the method of communication should be adjacent to the allocated budget.

Preference of Stakeholders: To attain the best communication, it is important to adjust with the chosen stakeholders on whatever communication channels are available (face to face, or online). Both can work, and the team can schedule a meeting by then.

Conveying Information: depending on the stakeholders, the team can utilize both sending an email and links of documents. The document's links would include the weekly reports or updates, issues that might arise, and all requirements needed to assure stakeholders.

Communication	Purpose	Delivery media	Frequency	Audience
Project Planning	Maintain the progress of the project team	Teams Meeting	Once before the development starts	Project Team,Project Manager, Project Sponsor
Sprint Planning	Have a monthly goal	Teams Meeting	Once before and after the development starts	Project Team,Project Manager, Project Sponsor
Release Planning	Handle all the dependencies	Teams Meeting	Once every month	Project Team,Project Manager, Project Sponsor
Product Backlog	Notify all the stakeholders about the unfinished process	Teams Meeting	If necessary, only	Project Team,Project Manager, Project Sponsor
Project Consultation	Maintain project coordination	Teams Meeting	Once every week	Project Team,Project Manager, Project Sponsor
Project Updates	Progress or updates about the project	Teams Meeting	Once every week	Project Team,Project Manager, Project Sponsor

The guidelines for meetings part of the document make sures that all the meetings held in the project lifecycle are well-organized and contribute to the success of the project. Furthermore, the guidelines will serve as an outline on how the project team should run a meeting with or without the project stakeholders. With this, the project team can enhance their communication and collaboration with one another which can help create a positive impact in the project development.

The following steps will aid the project team members with regards to scheduling a successful meeting:

1. Define the purpose and objectives: the meeting should have a clearly defined purpose and objective correlated to the project.

2. Make an agenda: making an agenda with the outlines of the topics should be present and it is important to prioritize the agenda items based on their relevance to the project’s objectives.

3. Identify the attendees and the roles: it is important to identify the necessary participants regarding their roles and responsibilities. Furthermore, it is important to include the key stakeholders that impact the topic being discussed.

4. Meeting Facilitation: managing the time effectively is important in a project team meeting as it will allow efficient progress through the topics or agendas. Furthermore, it is important to start the meeting on time to minimize delays.

5. Encourage active participation and engagement: it is encouraged for all the project team members to speak up with relevance to the topic. This will promote open communication and active listening.

6. Meeting Minutes: creating minutes for the meeting will help the project team in identifying the resources that need attention. This will also serve as an attendance and progress report on where the project team is on the project. Furthermore, sending the minutes to participants after the meeting is necessary as it will serve as their reminder aid about the future topics and topics discussed.

7. Meeting Evaluation: Meeting effectiveness should be evaluated to improve project communication by participant feedback. In addition, giving meeting updates based on past meetings is also important as it raises the possibility if a project team member successfully finished his/her assigned task.

• Clear and concise communication: terminologies must be clear and easily understood by stakeholders. Furthermore, communication should focus on the relevant information and is based on objectives.
• Active listening: it is important for the project team members to attain active listening as it encourages a great environment for the meeting, and it encourages honesty and openness.
• Proper Engagement: it is important to seek input and feedback from the relevant stakeholders as it may help emphasize any suggestions for improvement. Proper engagement can also promote collaboration as it requires each member to ask relevant questions and seek clarifications. Lastly, it is important to avoid unnecessary questions that may lead to uncertainty.
• Summarize from discussions: this can attain improvement on any topic that needs clarifications from discussions, and it can help each team member retain focus on every meeting as everyone is on the same page.
• Communication channels: identifying the best communication channel can help the team in conveying necessary resources with each other and the stakeholders. Moreover, it is important that each team member should know the appropriate communication channel (email, online meeting platforms, or project management tools).
• Schedule regular team meetings: the project team should schedule team meetings every week to discuss any updates, issues, or progress. This will also ensure that everyone is complying with the project schedule and that all assigned tasks are completed promptly.

The communication escalation process ensures that the communication issues are identified and resolved effectively, resulting in better project communication among the project team members and stakeholders. The escalation process should be adaptable along with the project lifecycle as it can ensure that all communication issues can be resolved quickly.

The communication escalation process for the Bregghan Point of Sale System is listed below:

1. Communicate directly to the project team members: With this, risks and issues can be resolved promptly. In addition, other topics such as discussions and updates should be directly communicated as a part of a routine.

2. Manager involvement: Escalate the issue to the team's designated project manager if any communication issues persist. It is necessary for the team to escalate the communication problem to the project manager if they cannot resolve it. The project manager's role is to help the team produce the best decision and try to resolve the issue.

3. Involvement of the Project Stakeholder: Whenever there are issues related to the end users and is not resolvable in the team level, it is important to escalate it to the project stakeholder and with this, necessary steps such as scheduling a meeting or sending a report stating how the team tried to resolve it should be taken into consideration.

4. Written report about the issue: After resolving any communication problem, a written report will be issued to prevent any future communication problems. Furthermore, this can help the team analyze and improve on the communication issues that arise.

Terms	Definition
Information Accuracy	All the information given is true and up to date.
Active Listening	Giving your full attention, focus, and understanding to a speaker.
Communication channels	These are various methods or mediums to which certain information is conveyed.
Team Meetings	Team Meetings refer to the scheduled meetings scheduled by the project manager to get updates and reports from one another.
Meeting Minutes	A type of document that includes the timeline, attendance, and topics/agendas discussed in a scheduled meeting.
Meeting Evaluation	Meeting evaluation refers to the feedback gained from a team member after every meeting.
Project Manager	An assigned person that plans, executes, and oversees the successful completion of the project.
Meeting Facilitation	The process of identifying if the meeting duration is consumed effectively and efficiently.
Budget Aligned	A term referring to a certain topic that is strictly adhered to the budget allocated.
Proper Engagement	This term refers to the respective actions of each team member on the scheduled meeting.