Skip to content

Group 02 Team Developmentality BARANGAY SOUTH SIGNAL VILLAGE WEB APP

enmaOP edited this page Jun 1, 2023 · 94 revisions

Table of Contents

1. PROJECT TITLE

Barangay South Signal Village Web App

2. PROJECT MEMBERS

2.1 Project Professor

NAME

EMAIL

Jose Eugenio L. Quesada

[email protected]

2.2 Project Adviser

NAME

EMAIL

Alvin C. Limpin

[email protected]

2.3 Project Team

NAME

ROLE

EMAIL

Mikedale B. Dellera

Project Manager

[email protected]

Wilkins V. Caducio

Product Owner

[email protected]

Jakerson B. Bermudo

Scrum Master

[email protected]

Rark Mowen L. Alcantara

Scrum Team Member

[email protected]

Carl James A. Garcia

Scrum Team Member

[email protected]

Princess Joy H. Ferrer

Documentation Manager

[email protected]

3. COMPANY PROFILE

The Barangay South Signal Village is one of the 28 barangays of Taguig City, Philippines. South Signal was formerly a part of Barangay Signal Village before being divided into four other barangays. The South Signal Village is composed of segregated areas from other barangays of Signal Village. The COMELEC Board of Canvassers duly confirmed the Barangay South Signal Village on December 19, 2008.

The Barangay South Signal Village heavily relies on papers, and most of its records and documents are stored in its physical filing cabinets. With the advancement of technology, selected barangays are already using computers and electronic devices to provide service and carry out official transactions. However, most barangays are still stuck with manual-based operations. Every request made by their client would take minutes to perform because of the tedious search for records stored in their physical file cabinets, which delays client service. All the essential and relevant information is encoded into a spreadsheet or a logbook, which uses many papers. The team would like to introduce the document management system to keep track of records, providing services and complaints in a modern approach with the use of computers as a primary medium that can speed up the process and reduce the consumption of paper. 

4. BUSINESS CASE

4.1 Executive Summary

Barangay South Signal Village is facing challenges in providing efficient, transparent, and accessible services and information to its residents. The system involves manual processes, limited access to crucial data, and potential service delays. This situation negatively affects residents' overall satisfaction and trust in their Barangay.

To address these issues, the proposed Barangay South Signal Village Web Application project aims to create a digital platform that improves access to information and service provisions. This platform will improve residents' access to vital services, facilitate community and local government communication, and promote transparency.

The web application will provide a range of benefits, including reduced processing time and effort for residents, support for vulnerable community members, error elimination through online forms, real-time insights for barangay staff, secure cloud-based data storage, and reliable information dissemination.

Aligned with the organization's strategic goals, the project supports the continuous improvement of residents' quality of life, adaptation, and innovation to meet evolving needs, and increased satisfaction and trust in local government through exceptional service and support.

Upon successful implementation, the Barangay South Signal Village Web Application project will contribute to the long-term success of the community, creating a more connected, efficient, and transparent environment for residents to thrive in.

4.1.1 Issue

The proposed project aims to address several problems with the current system of Barangay South Signal Village. These problems include long processing time, which can take up to an hour; the risk of acquiring disease/s due to in-person requests; common errors in manual input; the need for manual search of records; and the lack of secure data storage. These issues impact the efficiency, accuracy, and safety of the barangay's processes.  

4.1.2 Anticipated Outcomes

The project anticipates a functional centralized and live web application that can manage, and process request barangay, as well as submit concerns from the residents of Barangay South Signal Village to the Barangay South Signal Officials by the end of year 2023. This web app will be implemented and deployed in the cloud server managed by the Barangay Administrator who will maintain the overall system. The proposed system should include all necessary functionalities, such as the general web pages of the web application, resident and barangay employee dashboards, and processing requested barangay documents and concerns. 

If the proposed project is implemented, the Barangay South Signal Village Officials will primarily benefit from its ability to digitize their transactions and share valuable information about their barangay. It will also provide a new and easier way to process and record paperless barangay documents and concerns online, streamlining their operations and improving efficiency. The project will provide barangay staff with real-time insights on the number of requests per day, the number of pending requests, the number of online requests, and the number of registered accounts via their dashboards, which will help with their statistics. Additionally, the project will help officials to securely store data in the cloud, which saves data over the internet and can only be accessed by the administrator or the barangay employee by logging in to their account. This makes data more secure and easier to access than using filing cabinets. 

Barangay South Signal Village Residents will also benefit from this project when implemented because they will have a new and effortless way to access public information about their barangay. It will also help them to have a new and easier way to request barangay documents ahead of time without having to wait in line and spend time requesting at the barangay.  

4.1.3 Recommendation

After careful analysis of the needs and requirements of Barangay South Signal Village, we strongly recommend the development and implementation of a web app to enhance the communication and service delivery of the barangay to its constituents. The proposed web app will serve as a one-stop-shop platform that will allow the residents of Barangay South Signal Village to access information, request services, and interact with the barangay officials and employees through a user-friendly and secure interface. The web app will be accessible through desktop and mobile devices, making it convenient for all residents to use. 

We believe that the web app is necessary and beneficial for Barangay South Signal Village for several reasons. For starters, the web app will facilitate efficient communication between the barangay officials and the residents, thereby improving transparency, and accountability, and fostering a closer relationship between the barangay and its constituents. Second, the web app will streamline the delivery of services and reduce the need for physical visits to the barangay hall, increasing the efficiency of the barangay's operations and reducing waiting times for residents. Third, the web app will be a cost-effective solution compared to the traditional methods of communication and service delivery, resulting in cost savings for the barangay and improving the utilization of resources. Fourth, the web app will provide a centralized platform for data management, allowing the barangay officials to easily access and analyze data on the residents' requests, complaints, and feedback. Finally, the web app will give Barangay South Signal Village a competitive advantage in terms of service delivery and communication compared to other barangays that do not have a similar platform, thereby enhancing its reputation and attracting more residents and businesses to the area. 

4.1.4 Justification

Digitalizing the manual and paper processes of Barangay South Signal Village will increase productivity and decrease the errors brought upon by manual processes. Having a web application also increases the range of the services that the barangay can give, from on-site to remote services, which results in a projected increase in sales.  

If the Barangay South Signal Web App is not implemented, the barangay stays with manual transactions that (according to the barangay secretary) has an estimated amount of 5-6 documents per 10 requests which contain errors. The barangay will also be putting the residents and the employees at risk through physical transactions which have been proven by the recent pandemic. 

4.2 Business Case Analysis Team

ROLE

DESCRIPTION

NAME

Product ManageR

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

Mikedale B. Dellera

Product Owner

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

Wilkins V. Caducio

Scrum Master

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

Jakerson B. Bermudo

Documentation Manager

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

Princess Joy H. Ferrer

Scrum Team Member

They are responsible for developing the project deliverables and working together with the rest of the team to ensure the success of the project

Rark Mowen L. Alcantara

Carl James Garcia

Stakeholder

She is responsible for providing input on the project's scope, including requirements and expectations. She is also responsible for accepting the project deliverables as defined by the project's scope.

Hon. Michelle Odevilas

Class Adviser

He is responsible for providing guidance and support to the Project Manager and team. He should ensure that the project aligns with any relevant academic requirements and provide advice on best practices for managing project scope.

Jose Eugenio L. Quesada

Project Adviser

He is responsible for providing guidance and support to the Project Manager and team. He should ensure that the project aligns with the overall goals and objectives of the organization and provide advice on best practices for managing project scope.

Alvin C. Limpin

4.3.1 Problem Statement

Barangay South Signal Village is a local community in the Philippines where residents often face difficulties accessing vital information and services the local government provides. Currently, there needs to be a centralized platform for residents to access the necessary resources and services, leading to inefficiencies in communication and service delivery. 

The absence of a user-friendly and accessible web application has resulted in delays and dissatisfaction for residents who require information on local policies, programs, and services. Furthermore, the manual processes for availing various services, such as securing permits and filing complaints, contribute to longer waiting times and potential errors. 

The Barangay South Signal Village Web Application project aims to address these challenges by developing an integrated and accessible platform that streamlines residents' access to information and services. This will help improve communication between the local government and its constituents, enhance service delivery, and ultimately raise the overall quality of life for the residents. 

4.3.2 Organizational Impact

The barangay south signal village web application is to build a centralized and live web application for barangay south signal village residents. Wherein they can post their barangay profile, history, demography, and organizational chart. They can also list their contacts and requirements guidelines here. The proposed project will also implement a new role for their barangay employees to manage and work the app, these are the barangay secretary, web-app administrator, and the barangay captain. This will help them to manage and sort out everything easier and more quickly compared to their current system. 

4.3.1 Technology Migration

The development of the Barangay South Signal Village Web App will involve the use of different web development technologies. For the back end of the web application, the team will use LARAVEL, an open-source PHP web framework known for its ease of use and powerful features. In front-end development, BLADE.PHP, a templating engine used in the Laravel PHP framework that offers a simple and effective way to create reusable front-end designs using HTML, CSS, JavaScript, and PHP syntax, will be utilized by the team. For managing the data in the web app, the team will use MYSQL, a popular and reliable database management system that enables data storage and retrieval. By utilizing these technologies, the Barangay South Signal Village Web App will be developed to deliver an optimal user experience and meet the needs of the stakeholders. 

In terms of data migration, all raw data can be accessed and modified either in the Barangay Employee portal of the web app or in GoDaddy’s cPanel where it will be deployed. The data can be exported into Excel, CSV, or pdf files from the database.  

4.4 Project Overview

4.4.1 Project Description

In order to address the issue of manual transactions having long processing times and leading to typographical errors as well as potential harm to the health of both the residents and the employees, the project aims to develop a web application that digitalizes processes through online forms which help reduce typographical errors by up to 90% that also lessens the processing time for the residents by automating the information to be filled out in the forms. Through the digitalization of the processes, physical transactions and interactions will be lessened since the resident will have a schedule of when they can receive the document they requested and not fall in line just to create a single request. 

The project projected an increase to about 2x the number of processes that can be processed per day through manual transactions. This will provide efficiency and effectiveness and transparency for the residents of the barangay. 

4.4.2 Goals and Objectives

This project aims to improve the experience faced by Barangay South Signal Village residents. The web application aims to provide online services to the barangay community. The project aims to provide a better user experience for the residents and prevent unnecessary delays, confusion, and inefficiencies in accessing information and availing services. 

To achieve these goals, the specific objectives of the project are: 

  • Develop a web application to handle online document requests, reducing the processing time and effort for barangay residents by up to 80%. 
  • Assist vulnerable residents, such as PWDs and seniors, by allowing them to request documents through the web app, reducing direct contact and the risk of contagious diseases like COVID-19. 
  • Implement online forms to eliminate errors from illegible handwriting and decrease manual input mistakes by up to 90% through guided form filling. 
  • Through a statistics dashboard, provide barangay staff with real-time insights on request metrics, pending requests, online submissions, and registered accounts. 
  • Build a secure, cloud-based storage solution for data, accessible only to authorized personnel, offering 90% greater security than traditional filing cabinets. 

4.4.3 Project Performance

The success of the web app project for Barangay South Signal Village will be measured based on the following performance indicators: 

  • User Adoption: The web app will be successful if it is widely adopted and used by the residents of Barangay South Signal Village. The adoption rate will be monitored through analytics and feedback mechanisms on the web app. 
  • Service Delivery: The web app will be successful if it improves the efficiency and effectiveness of the barangay's service delivery. The time it takes to process requests, the number of complaints resolved, and the resident satisfaction levels will be monitored and measured through the web app.  
  • Cost Savings: The web app will be successful if it results in cost savings for the barangay. The cost of development, maintenance, and marketing of the web app will be compared to the cost savings achieved through the reduction of physical infrastructure and manual processing. 
  • Data Management: The web app will be successful if it provides a centralized platform for data management and analysis. The accuracy and completeness of data on the web app, as well as the insights and decisions derived from the data, will be monitored and measured.  
  • Competitive Advantage: The web app will be successful if it gives Barangay South Signal Village a competitive advantage in terms of service delivery and communication. The reputation of the barangay, as well as the number of new residents and businesses attracted to the area, will be monitored and measured.  
Based on these performance indicators, we believe that the web app project for Barangay South Signal Village has a high potential for success. The web app will be monitored and evaluated regularly to ensure that it meets the performance targets and achieves the desired outcomes for the barangay and its constituents. 

4.4.4 Project Assumptions

  1. It is assumed that key stakeholders, including community leaders, government officials, and residents of Barangay South Signal Village, will be engaged throughout the project to ensure their needs and concerns are considered in the planning and implementation phases. 
  2. The project budget has been estimated based on current market prices and industry standards. However, it is assumed that unforeseen cost overruns may occur due to changes in market conditions or unforeseen circumstances. 
  3. The availability of necessary resources, including personnel, equipment, and materials, has been assumed to be sufficient to complete the project within the proposed timeline. However, potential resource constraints or unforeseen delays may impact project completion.
  4. The project assumes that the necessary technology and infrastructure required for the project will be available and functional. However, unforeseen technical issues may arise that could impact project timelines and success. 
  5. It is assumed that all necessary permits and regulations required for the project will be obtained and adhered to. However, delays or complications in the permitting process may occur that could impact project timelines.
  6. The success of the project relies heavily on the acceptance and support of the community in Barangay South Signal Village. It is assumed that the community will be receptive to the project and actively participate in its implementation. However, community opposition or resistance may impact project success. 
  7. The project assumes that weather conditions will be favorable for project implementation. However, unforeseen weather events, such as typhoons or flooding, may impact project timelines and success. 
  8. The number of requests per year will increase by 10% after the implementation of the project. 

4.4.5 Project Constraints

Below are the project constraints the team needs to identify and address that may impact on the project’s timeline. 

  • Time: The project has a deadline, the team needs to construct the project, launch the project, and meet the regulatory requirements. The team needs to plan to plot their project and finish the project within the given time frame.  
  • Scope: The team needs to address their available resources such as their equipment and technology limitations. The team needs to make sure that they can work and finish the task to meet their project objectives.  
  • Resources: This will include their skills in how to make and create the project by using the full potential of their available materials and equipment to finish the project. The team should have the necessary resources to complete the project successfully.  
  • Stakeholder expectations: The team needs to plan, address, and ensure that they can meet the stakeholder expectations but still consider their project constraints.  
The project manager's role is important here because they need to identify and manage the constraints the team will face to ensure their project is finished and completed successfully. 

4.4.6 Major Project Milestones

The project Summary Milestone Schedule is presented below. As requirements are more clearly defined this schedule may be modified. Any changes will be communicated through project status meetings by the project manager.

Summary Milestone Schedule - List key project milestones relative to project start.

Project Milestone

Target Date
(mm/dd/yyyy)

Project Start

03/30/2022 )

Planning
- Midterm Presentation (Sprint 1)
- Final Presentation (Sprint 2)


03/05/2022
04/06/2022

Analysis and Design
- Pre-midterm presentation (Sprint 3)
- Midterm Presentation (Sprint 4)
- Final Requirement (Sprint 5)
- Pre-final Presentation (Sprint 5)
- Final Presentation (Sprint 6)


09/23/2022
09/28/2022
10/03/2022
10/28/2022
11/02/2022

Development
- Initial Release 1 Prototype
- Release 2
- Release 3
- Pre-midterm Presentation (Sprint 7)
- Midterm Presentation (Sprint 8)
Final Presentation (Sprint 9)


08/22/2022
08/28/2022
01/12/2023
01/09/2023
01/09/2023
03/03/2023

Implementation
- Midterm Presentation (Sprint 10)
- Final Presentation (Sprint 11)


05/04/2023
06/26/2023

Close-out
- System and Documentation Handover
- Gain Formal Acceptance
Project Close out meeting


06/05/2023
06/13/2023
06/25/2023

4.5 Strategic Alignment

The Barangay South Signal Village Web Application project, aligned with the organization's strategic goals and objectives, aims to maximize value, and contribute to the community's long-term success. 

  • The South Signal Village Web App seeks to enhance the quality of life for Barangay South Signal Village residents.
    This project supports this goal by simplifying access to information and services, improving communication, and promoting transparency within the local government. These enhancements will lead to a better living experience and foster a more connected and engaged community. 
  • The organization aims to adapt and innovate to address residents' evolving needs continuously.
    The web application project supports this goal by modernizing and consolidating access to local government services and information. The project will help the community stay up-to-date and competitive in an ever-changing world by embracing digital technologies and processes. 
  • The project aims to improve service delivery efficiency and accuracy, reduce delays, and ensure easy access to reliable information.
    By providing a higher level of service and support, the project will lead to increased satisfaction and trust among residents in their local government. 
  • The web app's goals and objectives are aligned with the barangay's priorities. 
    The web app is aimed at achieving the priorities of the barangay, which are to enhance public safety, promote economic development, and improve access to healthcare and education, by offering information and services related to these areas to help the barangay achieve its objectives. 

4.6 Cost Benefit Analysis

COST

  • Manpower Estimated Cost
    This includes the cost of the team members who will work on the project for 12 months. The team consists of:
  1. Project Manager : The average salary per month is ₱50,605.00, and the total salary for 12 months is ₱607,260.00.
  2. Product Owner : The average salary per month is ₱58,500.00, and the total salary for 12 months is ₱702,000.00.
  3. Scrum Master/Developer : The average salary per month is ₱79,500.00, and the total salary for 12 months is ₱954,000.00.
  4. Scrum Member/Laravel Junior Developer : The average salary per month is ₱40,000.00, and the total salary for 12 months is ₱960,000.00 (2 team members).
  5. Documentation Manager : The average salary per month is ₱41,059.00, and the total salary for 12 months is ₱492,708.00.
The total manpower cost estimate is ₱3,715,968.00 .
  • Maintenance Estimated Cost
    This includes the cost of maintaining the website after it has been developed. The cost elements are:
  1. Managed SSL Services : The cost is ₱4,999.00 per year.
  2. Website Security (Premium) : The cost is ₱799.00 per month, which amounts to ₱9,588.00 per year.
  3. Website Backup : The cost is ₱99.00 per month, which amounts to ₱1,188.00 per year.
  4. Scrum Member/Laravel Junior Developer : The average salary per month is ₱40,000.00, and the total salary for 12 months is ₱960,000.00 (2 team members).
  5. System Administrator : The average salary per month is ₱41,059.00, and the total salary for 12 months is ₱492,708.00.
Maintenance (yearly): The total cost for maintenance per year is ₱375,775.00 .
  • Hosting and DNS Cost
    This includes the cost of hosting and domain name system (DNS) protection for the website. The cost element is:
  1. Hosting w/ DNS protection (36 months) : The cost is ₱12,992.72 every 3 years.
  • Indirect Cost
    This includes the cost of utilities, which is covered by the barangay.
  1. Equipment : No cost element is included for equipment.
  2. Administrative Roles : No cost element is included for administrative roles.

This table displays the estimated cost of the project, which includes the allocated budget and its duration. The budget of this project is estimated around ₱4,104,735.72 which intended to cover the 12-month duration of the project. In the table, the team shows four types of costs in this project which are the Manpower Estimated Cost, Maintenance Estimated Cost, Hosting and DNS Cost, and the Indirect cost. The total maintenance cost per year is ₱375,775.00.

BENEFITS


This table presents the estimated revenue of the barangay for each year. The number of estimated requests was provided by the barangay secretary, and the project team estimates that there will be 70,000 requests per year at a cost of ₱50.00 each. This will result in a total revenue of ₱3,500,000.00 per year.

COST BENEFIT ANALYSIS '



Diagrams display the estimated yearly savings, with negative savings expected in the first year due to the cost of developing the project. However, in the following years, the project is expected to yield positive savings. The team expected that the number of requests would increase per year by 10% .

In the year 2, the cost will be amounted to the maintenance of the web app and the salary of the System Administrator which has the total sum of ₱375,775.00 . Additionally, every three years, the cost of renewing the hosting and DNS services, amounting to ₱12,992.72 , will be added to the cost.

4.7 Alternative Analysis

1. Do nothing (status quo) the organization would continue to use the current system and maintain the current system process. 

  • Pros: It can avoid unintended consequences because change can often lead to unintended consequences. It can also conserve resources such as money, time, and effort by making changes to the project. 
  • Cons: One of the downsides of status quo is it can miss out opportunities, it can lead to missing out potential opportunities for the organization and company. Also, failing to adapt to changing environments and continuously evolving markets may lead to stagnation and irrelevance.
2. Jira Service Management because it is used for software development to plant, track, and manage the work and projects. It is a flexible and powerful project management tool that can help the team increase their productivity to finish and complete the project. 
  • Pros: One advantage of Jira is its customizability; the Jira is highly customizable that allows organizations and companies to edit to their specific needs for their project. It can improve efficiency and productivity. It is also scalable that makes it more suitable for small companies with complex IT (Information Technology) operations.  
  • Cons: Main disadvantage of Jira is its Complexity because it can be overwhelming for inexperienced users for its advanced features that makes it complex. It required effort and time to configure it properly. Lastly is its cost, Jira is a paid software tool, and it can be an obstacle to some company or team that has not enough funds for their project. 
3. Request Tracker the team chose this because it is an open-source system that can be configured to handle document requests for the barangay south signal village web app.  
  • Pros: It is an Open-source software that makes it free to use and can be edited to fit the specific needs of a company and organization. Also, it is scalable because it can handle large volumes of tickets and is suitable for small organizations with complex ticketing requirements.  
  • Cons: One disadvantage is its complexity; it can be complex because of its high degree of customization making it hard to configure. It will require technical expertise to use properly. 

5. PROJECT CHARTER

5.1 Executive Summary

The product is a Web Application for Barangay South Signal Village that aims to provide an online service that takes on document requests and a ticketing system for inquiries to the community of the barangay. The Web Application will contain substantial information about the barangay such as organizational chart, history, demography, mission, vision and the hazard map.

The Barangay South Signal Village Web Application customers will only be limited to the Barangay South Signal Village residents.

The Barangay South Signal Village heavily relies on papers and most of their records and documents are stored in physical file cabinets, making their client wait for minutes that delay client service as well as their data being unsecured. Integrate its current system into the digital setting by making a web application that provides information about the barangay and online service/s for their community in a more efficient, effective, and transparent way.

The team consists of 6 members who are currently studying and taking the Bachelor of Science course in Information Technology. All members of the team are students at Asia Pacific College.

5.2 Project Purpose/Justification

This project's purpose is to provide online services to the barangay community. Which also contains information about the barangay, including its current officials and location. The reason is there are multiple problems identified in the current system of the Barangay South Signal Village, such as long processing time, common errors using manual input, manual search records of database and more. The result of this project may be beneficial to the officials and residents of Barangay South Signal Village.

5.2.1 Business Need/Case

The business need for the Barangay South Signal Village Web App project is to address the long processing times and inefficiencies in the current manual processes used by the barangay administration. Residents experience delays and need more transparency when accessing community services and information.

By developing a user-friendly web app that centralizes essential barangay information and services, the project will streamline communication and service delivery for both the administration and community members. This unified platform will eliminate confusion, reduce processing times, and improve accuracy in service requests and other interactions.

The intended effect of this business case is to enhance efficiency and effectiveness in the barangay operations, allowing the administration to focus on other crucial tasks like addressing community concerns and managing resources. The web app will also improve transparency, enabling residents to monitor the progress of requests and access important information about the barangay. Ultimately, the Barangay South Signal Village Web App project will help the local administration better serve Its community, promote transparency, and improve overall satisfaction among residents.

5.2.2 Business Objectives

This objectives statement states the goal of the barangay and the plans to achieve it. This project is in direct support of our corporate strategic plan to improve the web-application of the Barangay South Signal Village.

  • For the barangay to deploy the web app to the residents of Barangay South Signal Village within the timeline and track the number of residents using it to determine its success.
  • For the Barangay to see an improvement in the paperwork system by 90% that can reduce the risk of errors or discrepancies. It gives the officials time for other tasks, such as providing direct services to citizens or addressing pressing issues within the community.
  • For the Barangay see the increase of residents using the web app by at least 30% in the next few months with the given the resources and opportunities for optimization.
  • To achieve a 10% yearly increase in the number of requests after the deployment of the Barangay South Signal Village Web Application by the end of each calendar year.
By setting up SMART objectives, barangay may determine their objectives and create a plan to achieve them. It enables tracking of development along the path and guarantees that objectives are reasonable and reachable.

5.3 Project Description

The Barangay South Signal Village Web App is a centralized and live web application for the residents of the Barangay South Signal Village that provides information about the barangay and caters to online services such as requesting documents online and submitting concerns to the barangay officials. On the barangay web app homepage, users (resident or non-residents of the barangay) can visit barangay information such as the announcements on the Homepage, barangay information on the About Us page, safety guidelines and map book of the barangay in the Safety Section page, list of contact information in Contact page, and the guidelines for requesting documents in Requirements Guidelines page.

The barangay residents can register in the web application wherein they will have their resident dashboard that will utilize the functions of the web app, such as requesting documents online, submitting concerns, tracking their requests, and viewing the transaction history.

On the client side, the web app will implement different roles, namely as the Barangay Secretary, Web-App administrator, and the Barangay Captain, wherein they will have their dashboard with different tasks and functions such as processing the online requests and concerns of the residents, manage the barangay employee accounts and resident's account in the web application, generating reports, and managing web applications.

5.3.1 Project Objectives and Success Criteria

The proposed web-application would be successful when the following standards have been upheld:

  1. To create a web application that can handle online document requests that will reduce the processing time and time consumption for the constituents of the barangay to up to 80%.
  2. To help the community, especially the vulnerable residents such as PWDs and senior residents, to lessen the risk of acquiring contagious diseases such as COVID-19 in requesting barangay documents by applying through the web app that lessens their direct contact with other people.
  3. To create online forms to totally remove errors regarding illegible handwriting as well as reduce manual input errors by up to 90% through proper guidance in each part of information to be filled up in the form.
  4. To provide barangay staff with real-time insights regarding the number of requests per day, number of pending requests/s, number of online requests, and number of registered accounts by going through a statistics dashboard/page.
  5. To build a secure and safe storage location for data by the use of cloud, which saves data over the internet, and this can only be access by the administrator or the barangay staff itself by logging in the account making it 90% more secure than using file cabinet/s.
  6. To provide the community with credible information through an official web application.

5.3.2 Requirements

To be successful, this project, Barangay South Signal Village Web App, must comply with the following requirements:

  1. The project should pass functional testing process, in which the team, along with any client representatives and some IT professionals, will evaluate the functionality of the program, determining whether the function is performing according to the required specification.
  2. The project must be accomplished without disturbance to the client’s operations.
  3. The barangay employees involved in the web app should understand how it operates on the client side and how to maintain it.
As the project progresses, more criteria may be added as needed, with the project client’s permission.

5.3.3 Constraints

The following constraints pertain to the Barangay South Signal Village Web Application

  • Limited budget for the project
  • The availability of some hardware and software that will be necessary in this project.
  • Legal requirements and procedures due to being under the Local Government Unit (LGU) must be followed.

5.3.4 Assumptions

The following is a list of assumptions. Upon agreement and signature of this document, all parties acknowledge that these assumptions are true and correct:

  • This project has the full support of the project sponsor, stakeholders, and all departments.
  • The purpose of this project will be communicated throughout the Barangay South Signal Village prior to deployment.
  • The IT personnel will provide additional resources if necessary.

5.3.5 Preliminary Scope Statement

The Barangay South Signal Village Web App project will include the design, testing, and delivery of an improved current system of the Barangay South Signal Village in requesting barangay documents and reporting for any problem within the vicinity of the barangay. It also includes the main web app that will display the information of the barangay, including the safety guidelines, contact information, history of the barangay, mission, vision, demography, and the organizational chart of the barangay officials. The project team, along with their project adviser and consultants, will oversee the whole project development process, from paperwork through analysis and design and up to software resources. The project team will organize the manual and training for the barangay employees who will be part of the web app. The team will also conduct a session with the Administrator, who will handle the maintenance of programming codes for the web app.

5.4 Risks

The following are the risks for the Barangay South Signal Village Web-Application that the team have identified. To reduce the likelihood of these hazards, the project manager will choose and use the proper risk reduction and avoidance measures.

  • External threats that may breach the web-app's security.
  • Potential disruption of work due to internet outage or power outage.
  • Potential data theft or data loss due to potential security breaches.

5.5 Project Deliverables

The following deliverables must be met upon the successful completion of the Barangay South Signal Web-Application.

  1. Fully functional web-application and the source code.
  2. Project documentation for the web-application solution
  • User’s Manual
  • Business Case
  • Stakeholders Management Strategy Plan
  • Scope Management Plan
  • Cost Management Plan
  • Time Management Plan
  • Human Resource Management Plan
  • Communication Management Plan
  • Procurement Management Plan
  • Project Status Reports Distribution plan
  • Change Request Documentation
  • Project Execution Monitoring Report
  • Implementation Plan
  • Change Management Plan
  • Project Status Reports
  • Transition-Out Plan
  • Project Turn-Over Plan
  • Post Project Review Plan
  1. Recommendation lists for hardware and software that will be used.

5.6 Summary Milestones Schedule

The project Summary Milestone Schedule is presented below. As requirements are more clearly defined this schedule may be modified. Any changes will be communicated through project status meetings by the project manager.

Summary Milestone Schedule - List key project milestones relative to project start.

Project Milestone

Target Date
(mm/dd/yyyy)

Project Start

03/30/2022 )

Planning
- Midterm Presentation (Sprint 1)
- Final Presentation (Sprint 2)


03/05/2022
04/06/2022

Analysis and Design
- Pre-midterm presentation (Sprint 3)
- Midterm Presentation (Sprint 4)
- Final Requirement (Sprint 5)
- Pre-final Presentation (Sprint 5)
- Final Presentation (Sprint 6)


09/23/2022
09/28/2022
10/03/2022
10/28/2022
11/02/2022

Development
- Initial Release 1 Prototype
- Release 2
- Release 3
- Pre-midterm Presentation (Sprint 7)
- Midterm Presentation (Sprint 8)
Final Presentation (Sprint 9)


08/22/2022
08/28/2022
01/12/2023
01/09/2023
01/09/2023
03/03/2023

Implementation
- Midterm Presentation (Sprint 10)
- Final Presentation (Sprint 11)


05/04/2023
06/26/2023

Close-out
- System and Documentation Handover
- Gain Formal Acceptance
Project Close out meeting


06/05/2023
06/13/2023
06/25/2023

5.7 Summary Budget

The estimated budget allocated for the proposed project, assuming that the project will meet the necessary deadlines, and is according to the milestone schedule, is as follows:


This table displays the estimated cost of the project, which includes the allocated budget and its duration. The estimated budget of this project is at least ₱4,104,735.72 which intended to cover the 12-month duration of the project. In the table, the team shows four types of costs in this project which are the Manpower Estimated Cost, Maintenance Estimated Cost, Hosting and DNS Cost, and the Indirect cost.

5.8 Project Approval Requirements

The Barangay South Signal Village Web-Application will only be deemed successful if it has undergone thorough testing and all project material has been thoroughly distributed across the whole barangay within the constraints set forth in this charter. A recommendation for the ideal hardware and software specifications will also be included to fully measure the web- app's success. Success will be determined by the Project Client, Hon. Michelle Odevilas, who will also authorize the project's completion.

5.9 Project Manager

Mikedale B. Dellera is named Project Manager for the duration of the Barangay South Signal Web-Application. Mr. Dellera’s responsibility is to manage all project tasks, scheduling, consultation, and communication regarding the Barangay South Signal Village Web-Application. His team, consisting of a scrum master and four scrum members, will support the project. Mr. Dellera will coordinate all resource requirements through the course adviser, Prof. Jose Eugenio L. Quesada. Mr. Dellera is authorized to approve all changes regarding the documentation and the prototype. Any clarification and major changes must be requested through the Project Client, Hon. Michelle Odevilas. Mr. Dellera will provide timely updates to the Project Client.

6. STAKEHOLDER MANAGEMENT STRATEGY

6.1 Introduction

Stakeholder management is a critical aspect of any project, and it is especially important in the development and implementation of a web app for Barangay South Signal Village. The success of the project depends on the support and involvement of key stakeholders, including community leaders, government officials, residents, and other interested parties. A comprehensive stakeholder management strategy is essential to ensure that these stakeholders are engaged, informed, and their needs and concerns are addressed throughout the project. This section outlines the stakeholder management strategy for the development and implementation of the web app in Barangay South Signal Village. It includes an overview of the key stakeholders, their roles and responsibilities, and the communication and engagement activities that will be used to manage their involvement in the project. The stakeholder management strategy is designed to ensure that the web app aligns with the needs and priorities of the community and that it is well-received and utilized by all stakeholders.



There are a number of strategies that could be employed to improve stakeholder management for the Barangay South Signal Village Web-App, such as:

  • Improved Access to Information:
    The web-app will provide stakeholders with easy access to relevant and up-to-date information about public safety, economic development, healthcare, and education.
  • Enhanced Communication:
    The web-app will facilitate communication between stakeholders, including community leaders, government officials, residents, and other interested parties, to help address concerns, share information, and collaborate on initiatives.
  • Increased Efficiency:
    The web-app will streamline access to services and information, reducing the need for time-consuming and often confusing manual processes.
  • Empowering Community Members:
    The web-app will provide community members with the tools and resources to take a more active role in their community's development and decision-making processes.
  • Cost Savings:
    The web-app will help stakeholders save time and money by providing access to information and services online, reducing the need for in-person visits and paperwork.
  • Greater Transparency:
    The web-app will promote greater transparency in local governance by providing stakeholders with access to information about government initiatives, policies, and decisions.

6.2 Identify Stakeholders

The team has brainstormed the following steps to identify project stakeholders:

  • using a stakeholder analysis to locate all prospective stakeholders. This entails identifying internal and external stakeholders such as Barangay residents. Internal stakeholders include the employees within the barangay.
  • Creating a list of stakeholders based on how they will influence the web app, the power that they will have within the web app and lastly how they will be impacting the project.
These steps will ensure proper engagement and communication between the team and the stakeholders within the project. Communications include the needs and the concerns of the stakeholders that need to be addressed. Completing these steps will guarantee that the project is on the right track.

6.3 Key Stakeholders

Key stakeholders in the development and implementation of the web app for Barangay South Signal Village include:

  • Barangay Captain:
    These are influential people in the Barangay community, such as captains, councilors, and other community organization leaders. They will play a key role in promoting the web app and ensuring that it meets the needs of their community.
  • Barangay Secretary:
    They are responsible for maintaining the administrative and record-keeping functions of a Barangay. They play a key role in keeping accurate records of all meetings, ordinances, and transactions of the barangay. They ensure smooth and efficient operation in the Barangay.
  • Barangay Council:
    Barangay officials and other municipal officials will be the key stakeholders in the project. They will be responsible for providing the funds, resources, and support for the project and ensuring that it aligns with the local government's priorities.
  • Barangay South Signal Residents:
    The web app is designed to serve the needs of the residents of Barangay South Signal Village, so they are considered also essential stakeholders. They will be the primary users of the web app and will be able to provide valuable feedback on its functionality and effectiveness.
These stakeholders have been identified as key stakeholders due to their potential influence over the project, their potential impact on the project's success, and their potential resistance to the change represented by the project. It is important to engage them early and often in the project's lifecycle and seek their feedback on their desired level of participation and communication.

6.4 Key Stakeholders

Name

Department / Company

Position

Advisers

Objectives, Requirements, Interests

Influence

Project Contribution

Resistance

Hon. Michelle Odevilas

Barangay South Signal Village Official

Barangay Captain

 

Enhance Communication, Promote Transparency, Secure Data Management, and Community Development.

High

Supervised the team on what function should the system have and approve the overall project.

Cost Concerns, Privacy and Security, Illiteracy, and Limited Technical Knowledge '

Nerisa Caducio

Barangay South Signal Village Official

Barangay Secretary

 

Enhance Communication, Promote Transparency, Secure Data Management, and Community Development.

Medium

Support the team with required documents and address inquiries.

Increase Workload, Limited Technical Knowledge, and Concerns about Data Accuracy.'

Kgd. Norman H. Hortilano

Barangay South Signal Village Official

Barangay Council (Representative)

 

Enhance Communication, Promote Transparency, Secure Data Management, and Community Development.

Medium

Give supporting ideas, possible risk, and deep analysis.

Security Concerns, Transparency Concerns. '

Etelinda Villaret

Barangay South Signal Village Official

Barangay South Signal Village Resident

 

Access to Reliable and up-to-date Information, Accessibility to Different Request Documents and Submit Concerns Online.

High

Providing Input and Feedback and Active Engagement.

Privacy Concerns, Technological Barriers, Resistance to Change, and Mistrust in the Local Government '

7. SCOPE MANAGEMENT PLAN

7.1 Introduction

The scope of a project defines what work the team will do, and what deliverables they will produce. It is essential to manage a project's scope carefully to ensure it remains on track and within budget. This Scope Management Plan outlines the processes and procedures used to define, document, verify, and control the team's project scope.

The team follows a five-step process for Project Scope Management.

  1. Collection Requirements
    Schedule one-on-one or group meetings with stakeholders to discuss their needs, wants, and expectations for the project. Use open-ended questions to encourage stakeholders to share as much detail as possible about their requirements. Take notes and document their responses.
  2. Define Scope
    Review all project documentation, including contracts, agreements, and statements of work, to ensure that they align with the project's goals, objectives, and constraints. Use this information to help define the project's scope.
  3. Create WBS
    Involve the project team in its creation to ensure it is comprehensive and accurate. Use brainstorming sessions to gather input from team members and identify all the work packages required to complete the project.
  4. Verify Scope
    Perform a walkthrough of the project deliverables with stakeholders to ensure that they meet their needs and expectations. Allow stakeholders to provide feedback and make suggestions for improvement.
  5. Control Scope
    Update the project scope statement as needed to reflect any changes in the project's goals, objectives, or constraints. Communicate any changes to stakeholders to ensure that they are aware of the project's scope.

7.2 Scope Management Approach

The scope of the Barangay South Signal Village Web App is defined in Scope Definition, Project Scope Statement, Work Breakdown Structure (WBS) and WBS dictionary. The primary objective of the project is to develop a web application for the Barangay South Signal Village community. The web app will provide a platform for residents to access essential information, services, and resources provided by the barangay. The scope of the project includes the planning of the web app's functionalities, analyzing and designing the web app, developing the web app's functionalities, testing the web app for functionality, usability, and performance, and providing user manuals, training, and support.

Scope Change Management:

To manage any changes to the project scope, the project team will follow the following procedures:

  1. All project scope changes will be documented and communicated to all relevant stakeholders. This ensures that all project participants are informed of any changes and understand how they may affect the project.
  2. The project team will examine the scope change's impact on the project's timeframe, budget, and resources. This study will help establish whether the change is possible and what changes to the project plan may be required.
  3. The project sponsor or steering committee will approve or reject changes to the project scope. This ensures that any adjustments are consistent with the overall project goals and priorities, and that all stakeholders support the proposed changes.
  4. If the change is approved, the project team will make the necessary changes to the scope, timeline, budget, and resources. This will aid in keeping the project on schedule and ensuring that all modifications are correctly accounted for in the project plan.
By adhering to these rules, the project team will be able to efficiently manage any modifications to the project scope and ensure that the project is finished on time, on budget, and to the satisfaction of all stakeholders.

7.3 Roles and Responsibilities

The following roles and responsibilities have been assigned in relation to scope management:

  1. Project Manager: The Project Manager is responsible for managing the project's scope and ensuring that it remains within the defined boundaries. This includes identifying and managing any changes to the scope, communicating scope changes to the team and stakeholders, and ensuring that the project's deliverables align with the scope. The Project Manager is also responsible for ensuring that the project is completed on time and meets the specified quality standards.
  2. Product Owner: The Product Owner is responsible for defining and prioritizing the project requirements and ensuring that the final product meets the needs of the stakeholders. They work closely with the Project Manager and Scrum Team to ensure that the project deliverables align with the scope.
  3. Scrum Master: The Scrum Master is responsible for facilitating the agile development process and ensuring that the team is following the Scrum framework. They work closely with the Project Manager and Product Owner to ensure that the project is progressing according to the defined scope. The Scrum Master is also responsible for identifying and managing any scope-related risks or issues.
  4. Scrum Team: The Scrum Team is responsible for developing the project deliverables and working together with the rest of the team to ensure the success of the project. This includes understanding and adhering to the project's scope, identifying any scope-related risks or issues, and communicating these to the Project Manager and Scrum Master.
  5. Documentation Manager: The Documentation Manager is responsible for managing the project documentation and ensuring that it is complete and accurate. They work closely with the Project Manager and team to ensure that all project documentation aligns with the scope.
  6. Stakeholders: Stakeholders are responsible for providing input on the project's scope, including requirements and expectations. They are also responsible for accepting the project deliverables as defined by the project's scope. It is important for the Project Manager to communicate regularly with stakeholders to ensure that the project remains aligned with their needs and expectations.
  7. Class Adviser: The Class Adviser is responsible for providing guidance and support to the Project Manager and team. They should ensure that the project aligns with any relevant academic requirements and provide advice on best practices for managing project scope.
  8. Project Adviser: The Project Adviser is responsible for providing guidance and support to the Project Manager and team. They should ensure that the project aligns with the overall goals and objectives of the organization and provide advice on best practices for managing project scope.

7.4 Scope Definition

The Barangay South Signal Village Web Application Online Service is a comprehensive digital platform designed to provide essential information and services for residents of South Signal Village Barangay. The project scope involves developing a user-friendly dashboard for barangay announcements, news, and updates, a repository for essential documents such as resolutions, ordinances, and certificates, and various online services like barangay clearance, ID issuance, and permit processing. Additionally, a reporting module will allow residents to communicate concerns and complaints to barangay officials. The platform will ensure user data security and privacy through a secure account creation and management system requiring identity verification through government-issued IDs and robust security measures. Overall, this initiative aims to enhance the efficiency and effectiveness of community engagement and service delivery in the barangay.

7.5 Project Scope Statement

The project scope statement for the Barangay South Signal Village Web App will detail the project’s deliverables and the work necessary to create these deliverables.

7.5.1 Project Scope Description

The Barangay South Signal Village Web App is a centralized and live web application for the residents of the Barangay South Signal Village that provides information about the barangay and caters to online services such as requesting documents online and submitting concerns to the barangay officials.

On the barangay web app homepage, users (resident or non-residents of the barangay) can visit barangay information such as the announcements on the Homepage, barangay information on the About Us page, safety guidelines and map book of the barangay in the Safety Section page, list of contact information in Contact page, and the guidelines for requesting documents in Requirements Guidelines page.

The barangay residents can register in the web application wherein they will have their resident dashboard that will utilize the functions of the web app, such as requesting documents online, submitting concerns, tracking their requests, and viewing the transaction history.

On the client side, the web app will implement different roles, namely as the Barangay Secretary, Web-App administrator, and the Barangay Captain, wherein they will have their dashboard with different tasks and functions such as processing the online requests and concerns of the residents, manage the barangay employee accounts and resident's account in the web application, generating reports, and managing web applications.

7.5.2 Product Acceptance Criteria

The Barangay South Signal Village Web App will be deemed successful once the following criteria are met:

  • All features, modules, and functionalities outlined in the project scope statement have been developed and tested using the team's and the client's representative's approved test cases.
  • The web app must be user-friendly and easy to navigate, with a clear and intuitive user interface (UI) and user experience (UX) design.
  • The web app must be secure and protected from unauthorized access or data breaches.
  • The web app has been successfully deployed by the barangay.
  • The team has created all necessary project deliverables, including the user manual for the barangay.

7.5.3 Project Deliverables

The following list of deliverables will be provided upon successful completion of the project:

  • Fully functional web-application and the source code.
  • Recommendation lists for hardware and software that will be used.
  • Project documentation for the web-application solution:
  • User’s Manual 
  • Business Case 
  • Stakeholders Management Strategy Plan 
  • Scope Management Plan 
  • Cost Management Plan 
  • Time Management Plan 
  • Human Resource Management Plan 
  • Communication Management Plan 
  • Procurement Management Plan  
  • Project Status Reports Distribution plan 
  • Change Request Documentation 
  • Project Execution Monitoring Report 
  • Implementation Plan 
  • Change Management Plan 
  • Project Status Reports 
  • Transition-Out Plan 
  • Project Turn-Over Plan 
  • Post Project Review Plan 

7.5.4 Project Exclusions

The following work is outside the scope of this project and will not be included:

  • Online Payment for requesting barangay documents.
  • Integration of other systems or software that are not specifically mentioned in the project scope statement.
  • Full deployment process of this project.

7.5.5 Project Constraints

The following constraints pertain to the Barangay South Signal Village Web Application:

  1. Limited budget for the project
  2. The availability of some hardware and software that will be necessary in this project.
  3. Legal requirements and procedures due to being under the Local Government Unit (LGU) must be followed.

7.5.6 Project Assumptions

The following is a list of assumptions. Upon agreement and signature of this document, all parties acknowledge that these assumptions are true and correct:

  • This project has the full support of the project sponsor, stakeholders, and all departments.
  • The purpose of this project will be communicated throughout the Barangay South Signal Village prior to deployment.
  • The IT personnel will provide additional resources if necessary.

7.6 Work Breakdown Structure

In this WBS, the project is divided into five main sections: Project Planning, Analysis and Design, System Development, Implementation, and Closeout. Each section is then further broken down into more specific tasks and subtasks. The WBS helps to provide a clear and organized view of the project scope and can aid in managing the project's progress and ensuring that all aspects are accounted for.

1.1 PLANNING

1.1.1 Project Preparation

  • 1.1.1.1 Creation of Project Groups
  • 1.1.1.2 Choose Project/Client
  • 1.1.1.3 Choose Adviser/Consultant
  • 1.1.1.4 Design Thinking 1

1.1.2 MNTSDEV Team consultation

  • 1.1.2.1 Team meeting with Project adviser
  • 1.1.2.2 Team meeting with Project Sponsor

1.1.3 MNTSDEV Creation of Midterm Paper

  • 1.1.3.1 Chapter 1 (Introduction)
  • 1.1.3.2 Chapter 2 (RRL/RRS)
  • 1.1.3.3 Chapter 3 (Methodology)
  • 1.1.3.4 Chapter 4 (Results and Discussions)
  • 1.1.3.5 Chapter 5 (Conclusion)
  • 1.1.3.6 Proofreading
  • 1.1.3.7 Creation of presentation deck

1.1.4 MNTSDEV Midterm Evaluation

  • 1.1.4.1 Midterm (Sprint1)
  • 1.1.4.2 Comment Matrix

1.1.5 Initial Design

  • 1.1.5.1 Initial wireframe
  • 1.1.5.2 Initial low-fidelity prototype

1.1.6 MNTSDEV Progression of Paper/Final Paper

  • 1.1.6.1 Chapter 1 (Introduction)
  • 1.1.6.2 Chapter 2 (RRL/RRS)
  • 1.1.6.3 Chapter 3 (Current System)
  • 1.1.6.4 Chapter 4 (Proposed System)
  • 1.1.6.5 Chapter 5 (Requirement Analysis)
  • 1.1.6.6 Chapter 6 (Conclusion)
  • 1.1.6.7 Proofreading
  • 1.1.6.8 Creation of presentation deck
  • 1.1.6.9 Submission of final Requirements for Final Presentation

1.1.7 MNSTDEV Finals Evaluation

  • 1.1.7.1 Final Presentation (Sprint 2)
  • 1.1.7.2 Revision for Comment Matrix and Final Paper
  • 1.1.7.3 Submission of MNSTDEV FINAL Documents

1.2 ANALYSIS AND DESIGN

1.2.1 MSYADD Project Progression

  • 1.2.1.1 Initial analysis for Chapter 5 (Requirement Analysis)
  • 1.2.1.2 Submission of MNSTDEV final documents
  • 1.2.1.3 Implementation of GitHub Repository
  • 1.2.1.4 Request letter for Adviser/Consultant

1.2.2 MSYADD Team consultation

  • 1.2.2.1 Team meeting with Project adviser
  • 1.2.2.2 Team meeting with Project Sponsor

MSYADD Inpidual Deliverables

  • 1.2.4 MSYADD Release Plan

MSYADD Release Plan

  • 1.2.4.1 Release Plan 1.1
  • 1.2.4.2 Release Plan 1.2

1.2.5 MSYADD Week 3 - Week 4

  • 1.2.5.1 Event Table
  • 1.2.5.2 Use Case Diagram
  • 1.2.5.3 Use Case Full Description
  • 1.2.5.4 Data Flow Diagram
  • 1.2.5.5 Context Flow Diagram
  • 1.2.5.6 Entity Relationship Diagram

1.2.6 MSYADD Week 5 - Week 7

  • 1.2.6.1 Activity Diagram
  • 1.2.6.2 Object Diagram
  • 1.2.6.3 Class Diagram

1.2.7 MSYADD Midterm Evaluation

  • 1.2.7.1 Pre-midterm Presentation (Sprint 3)
  • 1.2.7.2 Midterm Presentation (Sprint 4)
  • 1.2.7.3 Revision Midterm

1.2.8 MSYADD Week 8 - Week 9

  • 1.2.8.1 Sequence Diagram
  • 1.2.8.2 State Machine Diagram
  • 1.2.8.3 Package Diagram
  • 1.2.8.4 Deployment Diagram
  • 1.2.8.5 Component Diagram

1.2.9 MSYADD Final Evaluation

  • 1.2.9.1 MSYADD Pre-final Presentation (Sprint 5)
  • 1.2.9.2 MSYADD Final Presentation (Sprint 6)
  • 1.2.9.3 Revision for Final Paper
  • 1.2.9.4 Submission of Final Requirements

1.3 DEVELOPMENT 

1.3.1 MCSPROJ Project Progression

  • 1.3.1.1 Submission of MSYADD Final Documents
  • 1.3.1.2 Request letter for Adviser/Consultant

1.3.2 MCSPROJ Release Plan

  • 1.3.2.1 Finalizing Release 1
  • 1.3.2.2 Release Plan 2
  • 1.3.2.3 Release Plan 3

1.3.3 MCSPROJ Midterm Deliverables

  • 1.3.3.1 Creation of Gantt Chart
  • 1.3.3.2 Creation of WBS
  • 1.3.3.3 Creation of Activity List
  • 1.3.3.4 Creation of Project Vision and Scope Progression
  • 1.3.3.5 Creation of Statement of Work Progression
  • 1.3.3.6 Creation of Project Charter Progression
  • 1.3.3.7 Pre-midterm Presentation (Sprint 7)

1.3.4 MCSPROJ Team consultation

  • 1.3.4.1 Team meeting with Project adviser
  • 1.3.4.2 Team meeting with Project Sponsor

1.3.5 MCSPROJ Midterm Evaluation

  • 1.3.5.1 Submission of Midterm Requirement
  • 1.3.5.2 MCSPROJ Final Presentation (Sprint 8)

1.3.6 MCSPROJ Finals Deliverables

  • 1.3.6.1 Creation of Test Case
  • 1.3.6.2 Creation of Quality Plan
  • 1.3.6.3 Creation of User Acceptance
  • 1.3.6.4 Creation of Change Management Plan
  • 1.3.6.5 Updating MCSPROJ Final Paper
  • 1.3.6.6 Creation of Proofreading Endorsement

1.3.7 MCSPROJ Finals Evaluation

  • 1.3.7.1 Submission of MCSPROJ Final Requirements
  • 1.3.7.2 MCSPROJ Final Presentation (Sprint 9)

1.4 IMPLEMENTATION

1.4.1 PROJMAN Project Progression

  • 1.4.1.1 Submission of MCSPROJ Final Documents
  • 1.4.1.2 Request Letter for Adviser/Consultant

1.4.2 PROJMAN Week 1-3

  • 1.4.2.1 Creation of Project Charter
  • 1.4.2.2 Creation of Business Case
  • 1.4.2.3 Creation of Stakeholders Management Strategy Plan

1.4.3 PROJMAN Week 4-6

  • 1.4.3.1 Creation of Scope Management Plan
  • 1.4.3.2 Creation of Cost Management Plan
  • 1.4.3.3 Creation of Time Management Plan
  • 1.4.3.4 Creation of Work Breakdown Structure
  • 1.4.3.5 Creation of Work Packages based on WBS.

1.4.4 System Updates

  • 1.4.4.1 Testing 1

1.4.5 PROJMAN Midterm Evaluation

  • 1.4.5.1 Submission of PROJMAN Midterm Requirements
  • 1.4.5.2 PROJMAN Midterm presentation (Sprint 10)

1.4.6 PROJMAN Week 8-10

  • 1.4.6.1 Creation of HR Management Plan
  • 1.4.6.2 Creation of Quality Management Plan
  • 1.4.6.3 Creation of Risk Management Plan
  • 1.4.6.4 Creation of Communications Management Plan
  • 1.4.6.5 Creation of Procurement Management Plan

1.4.7 PROJMAN Week 11

  • 1.4.7.1 Creation of Project Status Reports Distribution Plan
  • 1.4.7.2 Creation of Change Request Documentation
  • 1.4.7.3 Creation of Project Execution Monitoring Report
  • 1.4.7.4 Creation of Implementation Plan

1.4.8 PROJMAN Week 12

  • 1.4.8.1 Creation of Change Management Plan
  • 1.4.8.2 Creation of Project Status Reports
  • 1.4.8.3 Creation of Transition-Out Plan
  • 1.4.8.4 Creation of Project Turn-Over Plan
  • 1.4.8.5 Creation of Post Project Review Plan

1.4.9 PROJMAN Week 13

  • 1.4.9.1 Creation of Consolidated Project Plan

1.4.10 PROJMAN Final Evaluatio

  • 1.4.10.1 Submission of PROJMAN Final Requirements
  • 1.4.10.2 PROJMAN Final presentation (Sprint 11)

1.5 CLOSEOUT

1.5.1 System and documentation handover

  • 1.5.1.1 System and documentation handover

1.5.2 Gain Formal Acceptance

  • 1.5.2.1 Gain Formal Acceptance

1.5.3 Project close-out meeting.

  • 1.5.3.1 Project close-out meeting.

7.7 Scope Verification

The project team that facilitates the Barangay South Signal Web App project will conduct scope verification with the client and the project adviser every meeting to ensure that the deliverables are in line with the original scope. This will guarantee that the deliverables are accepted by the client and the project advisor and will ensure that the project will be finished on time and within the scope and budget.

7.8 Scope Control

The project team will make sure that every change that happens within the project's scope is effectively communicated with the client and approved. The team will also adhere to proper documentation regarding the change within the scope to ensure that there is transparency between the team and the client.

8. COST MANAGEMENT PLAN

8.1 Introduction

The Cost Management Plan for the Barangay South Signal Village Web App project is designed to ensure that all costs associated with the project are effectively managed throughout its lifecycle. The plan outlines the format and standards by which the project costs will be measured, reported, and controlled.

  1. Cost management responsibilities
  • The Project Manager will be responsible for overall cost management of the project and will be the primary point of contact for all cost-related issues.
  • The Finance Team will be responsible for monitoring project costs and ensuring that they are within the approved budget.
  1. Cost change approval
  • All cost changes must be approved by the Project Manager before they are implemented.
  • If the cost change exceeds 10% of the total project budget, it must be approved by the Project Sponsor before it can be implemented.
  1. Cost measurement and reporting
  • Costs will be measured and reported monthly, using a cost performance index (CPI) and a schedule performance index (SPI).
  • Reports will be presented to the Project Sponsor on a monthly basis.
  1. Budget format and standards'
  • The budget will be presented in a clear and concise format, using a spreadsheet format such as Excel.
  • The budget will be broken down into individual line items, with detailed cost estimates for each item.
  • The budget will be updated on a monthly basis, with any changes clearly highlighted.
Overall, the Cost Management Plan for the Barangay South Signal Village Web App project is designed to ensure that all costs associated with the project are effectively managed and controlled, so that the project can be completed within the approved budget. This will help ensure that the project is completed successfully and on time.

8.2 Cost Management Approach

The cost management approach for the Barangay South Signal Village Web App will be based on the following principles:

  1. Cost Estimating:
    The project team will use a bottom-up approach to estimate the costs associated with developing and launching the web app. This approach involves breaking down the project into smaller tasks and estimating the cost of each task based on the resources required. The team will use historical data from similar projects, industry benchmarks, and expert judgment to estimate costs accurately.
  2. Budget Development
    Based on the cost estimates, the project team will develop a comprehensive project budget that covers all the costs associated with developing and launching the web app. The budget will be reviewed and approved by the project sponsor or steering committee before it is finalized.
  3. Cost Control
    Throughout the project, the project team will monitor actual costs against the approved budget to ensure that the project is on track financially. Any deviations from the approved budget will be documented and analyzed to determine the root cause. If necessary, corrective action will be taken to bring the project back in line with the budget.
  4. Change Management
    Any changes to the project scope, timeline, or resources may have an impact on the project budget. Therefore, all changes will be reviewed by the project sponsor or steering committee to assess their impact on the budget. If the changes are approved, the project budget will be updated accordingly.
  5. Reporting
    Regular cost reports will be produced and distributed to the project team, stakeholders, and the project sponsor or steering committee. These reports will show actual costs to date, compared to the approved budget, and any deviations from the budget. The reports will also include an analysis of the causes of any deviations and any corrective actions taken.
By following this Cost Management Approach, we aim to ensure that the Barangay South Signal Village Web App project is completed within the approved budget, while still meeting the project objectives and delivering a high-quality product that satisfies the needs of the community.

8.3 Measuring Project Costs

8.4 Reporting Format

The project team will generate a Monthly Project Status Report to update stakeholders on the cost status of the project. This report will include a "Cost Management" section that will highlight the Earned Value Metrics (EVM) previously mentioned, such as Schedule Variance (SV), Cost Variance (CV), Schedule Performance Index (SPI), and Cost Performance Index (CPI), to evaluate the project's progress and cost performance. In case the project's cost exceeds the predefined thresholds, the report will include details of the issue along with the planned corrective actions. The report will also monitor any change requests resulting from cost overruns to ensure that they align with the project budget. These updates will be shared with stakeholders on a monthly basis to maintain transparency and ensure timely decision-making.

8.5 Cost Variance Response Process

Develop a corrective action plan to address the cost variance. The plan should include specific actions to reduce or eliminate the cost variance, as well as timelines and responsibilities for each action. Communicate with stakeholders to keep them informed about the cost variance and the corrective action plan. Be transparent about the impact on the project's budget, schedule, and scope. Re-evaluate the project plan to ensure that it is still feasible given the cost variance. Consider whether any adjustments need to be made to the project's schedule, scope, or quality to bring it back in line with the budget.

The Control Thresholds for this project are a CPI or SPI of less than 0.8 or greater than 1.2. If the project reaches one of these Control Thresholds a Cost Variance Corrective Action Plan is required. The Project Manager will present the Project Sponsor with options for corrective actions within five business days from when the cost variance is first reported. Within three business days from when the Project Sponsor selects a corrective action option, the Project Manager will present the Project Sponsor with a formal Cost Variance Corrective Action Plan. The Cost Variance Corrective Action Plan will detail the actions necessary to bring the project back within budget and the means by which the effectiveness of the actions in the plan will be measured. Upon acceptance of the Cost Variance Corrective Action Plan it will become a part of the project plan and the project will be updated to reflect the corrective actions.

8.6 Cost Change Control Process

The South Signal Village Barangay Web Application project aims to create a comprehensive digital platform that consolidates essential information and services for the residents, enhancing community engagement and service delivery efficiency in the barangay.

  • Project Deliverables:
  1. A fully functional South Signal Village Barangay Web Application, including
    1. A user-friendly dashboard for barangay announcements, news, and updates.
    2. A repository for important documents such as barangay resolutions, ordinances, and certificates.
    3. An integrated online services system for barangay clearance, ID issuance, and permit processing.
    4. A reporting module for residents to communicate concerns and complaints to barangay officials. ## A scheduling module to display the availability of barangay officials and facilitate appointments.
  2. A secure account creation and management system, including a. Identity verification using government-issued IDs. b. Robust security measures to prevent unauthorized access and protect user data.
  3. Documentation for the design, development, and implementation processes.
  4. User manuals and training materials for barangay officials and residents.
  5. Ongoing maintenance and support services as required.
  • Project Work Breakdown:
  1. Web Application Development:
    1. Design a responsive and accessible web application interface.
    2. Develop the dashboard, document repository, and online services modules.
    3. Implement the reporting and scheduling modules.
  2. Testing and Deployment: a. Conduct thorough web application testing for functionality, usability, and security. b. Deploy the web application and provide Training to barangay officials and residents.
  3. Documentation and Training:
    1. Create documentation of the design, development, and implementation processes.
    2. Develop user manuals and training materials for barangay officials and residents.

8.7 Project Budget

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

  • Direct Costs:
1. Manpower Cost

Project Manager

₱ 607,260.00

Product Owner

₱ 702,000.00

Scrum Master / Developer x 2

₱ 954,000.00

Scrum Member / Laravel Junior Developer

₱ 960,000.00

Documentation Manager 

₱ 492,708.00

2. Maintenance (Yearly after project closure)

Managed SSL Services

₱ 4,999.00

Website Security (Premium)

₱ 9,588.00

Website Backup

₱ 1,188.00

System Administrator

₱ 360,000.00

3. Hosting and DNS (Every 3 years after project closure)

Hosting w/ DNS protection (36 months)

₱ 12,992.72

  • Indirect Costs:
  1. Utilities
  2. Equipment
  3. Administrative Roles

9. SCHEDULE MANAGEMENT PLAN

9.1 Introduction

The purpose of this Schedule Management Plan is to establish a clear, organized framework for managing the development and implementation of the South Signal Village Barangay Web Application Project. The significance of this plan lies in its ability to define the project timeline, coordinate team activities, ensure alignment with project goals, and allow for effective response to any changes or unexpected challenges.

This plan provides an overview of the project's key phases, from initial planning to final project closeout, each broken down into manageable sprints according to Agile methodologies within the Software Development Life Cycle (SDLC). It lays out the critical milestones, target dates, and corresponding activities, ensuring every step of the project is clearly outlined.

Moreover, the plan outlines the roles and responsibilities of each team member and stakeholder in maintaining the schedule and managing deviations. It introduces the approach for managing schedule changes and scope alterations, with a focus on thorough evaluation, documentation, and communication.




9.2 Schedule Management Approach

Team Developmentality will utilize the Software Development Life Cycle (SDLC) throughout the project, specifically using the Agile Methodologies. The Software Development Cycle is one of the fundamental methods in developing software in a series of different phases. With the Agile method, the project will be broken down into smaller and more manageable parts called sprints. Each sprint focuses on delivering specific features or functionality that will guide the team thoroughly.

  • A. Scheduling Tool
    The team will use Project Libre to plan and record the project's progress by activities and phases. Based on the team schedule and the project scope, the project will be divided into five main phases:
  1. Plannings
    During this phase, the team defines the project's goals, requirements, scope, and objectives. The team then uses this information to develop a high-level project plan and a specific Sprint plan describing each sprint's activities and objectives.
  2. Analysis and Design
    During this phase, the team evaluates the system analysis and detailed design identified in the planning phase. The primary goal of this phase is to create necessary system requirements that will guide the development team in creating the software.
  3. Development
    During this phase, the team will write codes and create the web app according to the created system analysis and detailed designs.
  4. Implementation
    During this phase, the team will test the system using functional and performance testing to ensure the web app works appropriately based on the client's needs. The team will create necessary documents in this phase, such as the user manual for the Closeout phase.
  5. Closeout
    his phase will be the last phase of the project, wherein the team will hand over the system to the client.
  • B. Schedule Milestones
    The project Summary Milestone Schedule is presented below. As requirements are more clearly defined, this schedule may be modified. Any changes will be communicated through project status meetings by the project manager.



Summary Milestone Schedule - List key project milestones relative to project start.

Project Milestone

Target Date
(mm/dd/yyyy)

Project Start

03/30/2022 )

Planning
- Midterm Presentation (Sprint 1)
- Final Presentation (Sprint 2)


03/05/2022
04/06/2022

Analysis and Design
- Pre-midterm presentation (Sprint 3)
- Midterm Presentation (Sprint 4)
- Final Requirement (Sprint 5)
- Pre-final Presentation (Sprint 5)
- Final Presentation (Sprint 6)


09/23/2022
09/28/2022
10/03/2022
10/28/2022
11/02/2022

Development
- Initial Release 1 Prototype
- Release 2
- Release 3
- Pre-midterm Presentation (Sprint 7)
- Midterm Presentation (Sprint 8)
Final Presentation (Sprint 9)


08/22/2022
08/28/2022
01/12/2023
01/09/2023
01/09/2023
03/03/2023

Implementation
- Midterm Presentation (Sprint 10)
- Final Presentation (Sprint 11)


05/04/2023
06/26/2023

Close-out
- System and Documentation Handover
- Gain Formal Acceptance
Project Close out meeting


06/05/2023
06/13/2023
06/25/2023

9.3 Schedule Control

Schedule Control is essential for project success and requires collaborative work from all team members and stakeholders. To ensure the schedule is under control, different roles and responsibilities for schedule development are as follows:

  1. Project Manager
    responsible for developing and maintaining the project schedule, communicating progress to stakeholders, identifying, and managing schedule-related risks and issues, and updating the schedule as needed.
  2. Product Owner
    works with the Project Manager and Scrum Team to ensure project deliverables align with the schedule, prioritize requirements according to the schedule, and provide input on changes to the schedule.
  3. Scrum Master'
    ensures the team follows the schedule and Scrum framework, manages schedule-related risks and issues, and works with the Project Manager and Product Owner to ensure the project progresses according to the schedule.
  4. Scrum Team
    develops project deliverables according to the schedule, communicates schedule-related risks or issues to the Project Manager and Scrum Master, and adheres to the schedule.
  5. Documentation Manager
    ensures project documentation aligns with the schedule and provides updates on any changes to the schedule.
  6. Stakeholders
    accept project deliverables as defined by the schedule and provide input on changes to the schedule.
  7. Class Adviser and Project Adviser
    provide guidance on managing the project schedule and ensure alignment with relevant requirements and goals.
To control the project schedule, it will be monitored, reviewed, and revised as needed, and the team will participate in updates and meetings, collaborate on changes, and resolve schedule variances. The Project Manager will update the client on the schedule status and submit any schedule change requests for approval.

9.4 Schedule Changes and Thresholds

The boundary conditions will be thoroughly discussed by the team with the project client. The team will monitor the project schedule as the project progresses, this includes all the changes made outside of the original plan. The team will then identify if these changes exceed the boundary conditions and thresholds and how much it will affect the project schedule. If the project manager determines the changes go beyond the boundary conditions and does not meet the change threshold, a schedule change request will be created. The changes that do not meet the threshold will be discussed with the project sponsor for approval. Once the change request is approved, the project manager will be in charge of modifying the schedule and communicating any changes and their effects on the plan. The project manager must also let the project team, project sponsor, and stakeholders know about the changes that have been accepted.

9.5 Scope Change

The team needs to document all scope changes, including the reason for the change, the impact on the project, and any changes to the project schedule or budget. Update the project plan to reflect any scope changes. Communicate all scope changes to stakeholders, including the impact on the project's budget, schedule, and quality. Be transparent about the reasons for the change and the expected outcomes.

10. WORK BREAKDOWN STRUCTURE

10.1 Introduction

The Work Breakdown Structure or WBS is a hierarchical breakdown of the project deliverables into smaller, more manageable components. The WBS provides a framework for the team for organizing their project work and helps them to identify the activities needed to complete their project.

The purpose of the WBS is to break down the project into manageable work packages that can be planned, monitored, and controlled. By breaking down the project into smaller components, it is easier for the team to estimate the effort required to complete each task, assign responsibilities to team members, and track progress against the project plan. It is an essential tool for project managers and provides a visual representation of the project scope and objectives. The WBS is a key component of the project management plan and is developed during the project's planning phase. The WBS helps the team to ensure that all project activities are accounted for, and nothing is overlooked or missed.

Listed below are the project deliverables, project work, activities required to complete each deliverable and the resources needed to complete the project. Such as choosing a project client, choosing a consultant, creating all papers needed for the project, and the expected labor to cost.

The Work Breakdown Structure presented here represents all the work required to complete this project.

10.2 Outline View

The Barangay South Signal Village Web App is a comprehensive project aimed at developing a web application that caters to the needs of the residents in the Barangay. The project is divided into four phases, namely planning, analysis and design, development, and implementation, with each phase having specific tasks and deliverables.

                 1. Barangay South Signal Village Web App

  1.1 PLANNING
    1.1.1 Project Preparation
        1.1.1.1 Creation of Project Groups
        1.1.1.2 Choose Project/Client
        1.1.1.3 Choose Adviser/Consultant
        1.1.1.4 Design Thinking 1
    1.1.2 MNTSDEV Team consultation
        1.1.2.1 Team meeting with Project adviser
        1.1.2.2 Team meeting with Project Sponsor
    1.1.3 MNTSDEV Creation of Midterm Paper
        1.1.3.1 Chapter 1 (Introduction)
        1.1.3.2 Chapter 2 (RRL/RRS)
        1.1.3.3 Chapter 3 (Methodology)
        1.1.3.4 Chapter 4 (Results and Discussions)
        1.1.3.5 Chapter 5 (Conclusion)
        1.1.3.6 Proofreading
        1.1.3.7 Creation of presentation deck
    1.1.4 MNTSDEV Midterm Evaluation
        1.1.4.1 Midterm (Sprint1)
        1.1.4.2 Comment Matrix
    1.1.5 Initial Design
        1.1.5.1 Initial wireframe
        1.1.5.2 Initial low-fidelity prototype
    1.1.6 MNTSDEV Progression of Paper/Final Paper
        1.1.6.1 Chapter 1 (Introduction)
        1.1.6.2 Chapter 2 (RRL/RRS)
        1.1.6.3 Chapter 3 (Current System)
        1.1.6.4 Chapter 4 (Proposed System)
        1.1.6.5 Chapter 5 (Requirement Analysis)
        1.1.6.6 Chapter 6 (Conclusion)
        1.1.6.7 Proofreading
        1.1.6.8 Creation of presentation deck
        1.1.6.9 Submission of final Requirements for Final Presentation
    1.1.7 MNSTDEV Finals Evaluation
        1.1.7.1 Final Presentation (Sprint 2)
        1.1.7.2 Revision for Comment Matrix and Final Paper
        1.1.7.3 Submission of MNSTDEV FINAL Documents

  1.2 ANALYSIS AND DESIGN
    1.2.1 MSYADD Project Progression
        1.2.1.1 Initial analysis for Chapter 5 (Requirement Analysis)
        1.2.1.2 Submission of MNSTDEV final documents
        1.2.1.3 Implementation of GitHub Repository
        1.2.1.4 Request letter for Adviser/Consultant
    1.2.2 MSYADD Team consultation
        1.2.2.1 Team meeting with Project adviser
        1.2.2.2 Team meeting with Project Sponsor
    1.2.3 MSYADD Individual Deliverables
    1.2.4 MSYADD Release Plan
        1.2.4.1 Release Plan 1.1
        1.2.4.2 Release Plan 1.2
    1.2.5 MSYADD Week 3 - Week 4
        1.2.5.1 Event Table
        1.2.5.2 Use Case Diagram
        1.2.5.3 Use Case Full Description
        1.2.5.4 Data Flow Diagram
        1.2.5.5 Context Flow Diagram
        1.2.5.6 Entity Relationship Diagram
    1.2.6 MSYADD Week 5 - Week 7
        1.2.6.1 Activity Diagram
        1.2.6.2 Object Diagram
        1.2.6.3 Class Diagram
    1.2.7 MSYADD Midterm Evaluation
        1.2.7.1 Pre-midterm Presentation (Sprint 3)
        1.2.7.2 Midterm Presentation (Sprint 4)
        1.2.7.3 Revision Midterm
    1.2.8 MSYADD Week 8 - Week 9
        1.2.8.1 Sequence Diagram
        1.2.8.2 State Machine Diagram
        1.2.8.3 Package Diagram
        1.2.8.4 Deployment Diagram
        1.2.8.5 Component Diagram
    1.2.9 MSYADD Final Evaluation
        1.2.9.1 MSYADD Pre-final Presentation (Sprint 5)
        1.2.9.2 MSYADD Final Presentation (Sprint 6)
        1.2.9.3 Revision for Final Paper
        1.2.9.4 Submission of Final Requirements

  1.3 DEVELOPMENT
    1.3.1MCSPROJ Project Progression
        1.3.1.1 Submission of MSYADD Final Documents
        1.3.1.2 Request letter for Adviser/Consultant
    1.3.2 MCSPROJ Release Plan
        1.3.2.1 Finalizing Release 1
        1.3.2.2 Release Plan 2
        1.3.2.3 Release Plan 3
    1.3.3 MCSPROJ Midterm Deliverables
        1.3.3.1 Creation of Gantt Chart
        1.3.3.2 Creation of WBS
        1.3.3.3 Creation of Activity List
        1.3.3.4 Creation of Project Vision and Scope Progression
        1.3.3.5 Creation of Statement of Work Progression
        1.3.3.6 Creation of Project Charter Progression
        1.3.3.7 Pre-midterm Presentation (Sprint 7)
    1.3.4 MCSPROJ Team consultation
        1.3.4.1 Team meeting with Project adviser
        1.3.4.2 Team meeting with Project Sponsor
    1.3.5 MCSPROJ Midterm Evaluation
        1.3.5.1 Submission of Midterm Requirement
        1.3.5.2 MCSPROJ Final Presentation (Sprint 8)
    1.3.6 MCSPROJ Finals Deliverables
        1.3.6.1 Creation of Test Case
        1.3.6.2 Creation of Quality Plan
        1.3.6.3 Creation of User Acceptance
        1.3.6.4 Creation of Change Management Plan

        1.3.6.5 Updating MCSPROJ Final Paper
        1.3.6.6 Creation of Proofreading Endorsement
    1.3.7 MCSPROJ Finals Evaluation
        1.3.7.1 Submission of MCSPROJ Final Requirements
        1.3.7.2 MCSPROJ Final Presentation (Sprint 9)

  1.4 IMPLEMENTATION
    1.4.1 PROJMAN Project Progression
        1.4.1.1 Submission of MCSPROJ Final Documents
        1.4.1.2 Request Letter for Adviser/Consultant
    1.4.2 PROJMAN Week 1-3
        1.4.2.1 Creation of Project Charter
        1.4.2.2 Creation of Business Case
        1.4.2.3 Creation of Stakeholders Management Strategy Plan
    1.4.3 PROJMAN Week 4-6
        1.4.3.1 Creation of Scope Management Plan
        1.4.3.2 Creation of Cost Management Plan
        1.4.3.3 Creation of Time Management Plan
        1.4.3.4 Creation of Work Breakdown Structure
        1.4.3.5 Creation of Work Packages based on WBS.
    1.4.4 System Updates
        1.4.4.1 Testing 1
    1.4.5 PROJMAN Midterm Evaluation
        1.4.5.1 Submission of PROJMAN Midterm Requirements
        1.4.5.2 PROJMAN Midterm presentation (Sprint 10)
    1.4.6 PROJMAN Week 8-10
        1.4.6.1 Creation of HR Management Plan
        1.4.6.2 Creation of Quality Management Plan
        1.4.6.3 Creation of Risk Management Plan
        1.4.6.4 Creation of Communications Management Plan
        1.4.6.5 Creation of Procurement Management Plan
    1.4.7 PROJMAN Week 11
        1.4.7.1 Creation of Project Status Reports Distribution Plan
        1.4.7.2 Creation of Change Request Documentation
        1.4.7.3 Creation of Project Execution Monitoring Report
        1.4.7.4 Creation of Implementation Plan
    1.4.8 PROJMAN Week 12
        1.4.8.1 Creation of Change Management Plan
        1.4.8.2 Creation of Project Status Reports
        1.4.8.3 Creation of Transition-Out Plan
        1.4.8.4 Creation of Project Turn-Over Plan
        1.4.8.5 Creation of Post Project Review Plan
    1.4.9 PROJMAN Week 13
        1.4.9.1 Creation of Consolidated Project Plan
    1.4.10 PROJMAN Final Evaluation
        1.4.10.1 Submission of PROJMAN Final Requirements
        1.4.10.2 PROJMAN Final presentation (Sprint 11)

  1.5 CLOSEOUT
        1.5.1.1 System and documentation handover
        1.5.1.2 Gain Formal Acceptance
        1.5.1.3 Project close out meeting.

10.3 Hierarchical Structure

The hierarchical structure makes it easy to see how the different components of a project fit together and how the work is distributed across the project team. It also helps to ensure that all the necessary work is identified and accounted for, which can reduce the risk of schedule delays or cost overruns for the team.

Level WBS Code Element Name
1 1 Barangay South Signal Village Web App
2 1.1 Planning
3 1.1.1 Project Preparation
4 1.1.1.1 Creation of Project Groups
4 1.1.1.2 Choose Project/Client
4 1.1.1.3 Choose Adviser/Consultant
4 1.1.1.4 Design Thinking 1
3 1.1.2 MNTSDEV Team consultation
4 1.1.2.1 Team meeting with Project adviser
4 1.1.2.2 Team meeting with Project Sponsor
3 1.1.3 MNTSDEV Creation of Midterm Paper
4 1.1.3.1 Chapter 1 (Introduction)
4 1.1.3.2 Chapter 2 (RRL/RRS)
4 1.1.3.3 Chapter 3 (Methodology)
4 1.1.3.4 Chapter 4 (Results and Discussions)
4 1.1.3.5 Chapter 5 (Conclusion)
4 1.1.3.6 Proofreading
4 1.1.3.7 Creation of presentation deck
3 1.1.4 MNTSDEV Midterm Evaluation
4 1.1.4.1 Midterm (Sprint1)
4 1.1.4.2 Comment Matrix
3 1.1.5 Initial Design
4 1.1.5.1 Initial wireframe
4 1.1.5.2 Initial low-fidelity prototype
3 1.1.6 MNTSDEV Progression of Paper/Final Paper
4 1.1.6.1 Chapter 1 (Introduction)
4 1.1.6.2 Chapter 2 (RRL/RRS)
4 1.1.6.3 Chapter 3 (Current System)
4 1.1.6.4 Chapter 4 (Proposed System)
4 1.1.6.5 Chapter 5 (Requirement Analysis)
4 1.1.6.6 Chapter 6 (Conclusion)
4 1.1.6.7 Proofreading
4 1.1.6.8 Creation of presentation deck
4 1.1.6.9 Submission of final Requirements for Final Presentation
3 1.1.7 MNSTDEV Finals Evaluation
4 1.1.7.1 Final Presentation (Sprint 2)
4 1.1.7.2 Revision for Comment Matrix and Final Paper
4 1.1.7.3 Submission of MNSTDEV FINAL Documents
2 1.2 Analysis and Design
3 1.2.1 MSYADD Project Progression
4 1.2.1.1 Initial analysis for Chapter 5 (Requirement Analysis)
4 1.2.1.2 Submission of MNSTDEV final documents
4 1.2.1.3 Implementation of GitHub Repository
4 1.2.1.4 Request letter for Adviser/Consultant
3 1.2.2 MSYADD Team consultation
4 1.2.2.1 Team meeting with Project adviser
4 1.2.2.2 Team meeting with Project Sponsor
3 1.2.3 MSYADD Individual Deliverables
3 1.2.4 MSYADD Release Plan
4 1.2.4.1 Release Plan 1.1
4 1.2.4.2 Release Plan 1.2
3 1.2.5 MSYADD Week 3 - Week 4
4 1.2.5.1 Event Table
4 1.2.5.2 Use Case Diagram
4 1.2.5.3 Use Case Full Description
4 1.2.5.4 Data Flow Diagram
4 1.2.5.5 Context Flow Diagram
4 1.2.5.6 Entity Relationship Diagram
3 1.2.6 MSYADD Week 5 - Week 7
4 1.2.6.1 Activity Diagram
4 1.2.6.2 Object Diagram
4 1.2.6.3 Class Diagram
3 1.2.7 MSYADD Midterm Evaluation
4 1.2.7.1 Pre-midterm Presentation (Sprint 3)
4 1.2.7.2 Midterm Presentation (Sprint 4)
4 1.2.7.3 Revision Midterm
3 1.2.8 MSYADD Week 8 - Week 9
4 1.2.8.1 Sequence Diagram
4 1.2.8.2 State Machine Diagram
4 1.2.8.3 Package Diagram
4 1.2.8.4 Deployment Diagram
4 1.2.8.5 Component Diagram
3 1.2.9 MSYADD Final Evaluation
4 1.2.9.1 MSYADD Pre-final Presentation (Sprint 5)
4 1.2.9.2 MSYADD Final Presentation (Sprint 6)
4 1.2.9.3 Revision for Final Paper
4 1.2.9.4 Submission of Final Requirements
2 1.3 DEVELOPMENT
3 1.3.1 MCSPROJ Project Progression
4 1.3.1.1 Submission of MSYADD Final Documents
4 1.3.1.2 Request letter for Adviser/Consultant
3 1.3.2 MCSPROJ Release Plan
4 1.3.2.1 Finalizing Release 1
4 1.3.2.2 Release Plan 2
4 1.3.2.3 Release Plan 3
3 1.3.3 MCSPROJ Midterm Deliverables
4 1.3.3.1 Creation of Gantt Chart
4 1.3.3.2 Creation of WBS
4 1.3.3.3 Creation of Activity List
4 1.3.3.4 Creation of Project Vision and Scope Progression
4 1.3.3.5 Creation of Statement of Work Progression
4 1.3.3.6 Creation of Project Charter Progression
4 1.3.3.7 Pre-midterm Presentation (Sprint 7)
3 1.3.4 MCSPROJ Team consultation
4 1.3.4.1 Team meeting with Project adviser
4 1.3.4.2 Team meeting with Project Sponsor
3 1.3.5 MCSPROJ Midterm Evaluation
4 1.3.5.1 Submission of Midterm Requirement
4 1.3.5.2 MCSPROJ Final Presentation (Sprint 8)
3 1.3.6 MCSPROJ Finals Deliverables
4 1.3.6.1 Creation of Test Case
4 1.3.6.2 Creation of Quality Plan
4 1.3.6.3 Creation of User Acceptance
4 1.3.6.4 Creation of Change Management Plan
4 1.3.6.5 Updating MCSPROJ Final Paper
4 1.3.6.6 Creation of Proofreading Endorsement
3 1.3.7 MCSPROJ Finals Evaluation
4 1.3.7.1 Submission of MCSPROJ Final Requirements
4 1.3.7.2 MCSPROJ Final Presentation (Sprint 9)
2 1.4 Implementation
3 1.4.1 PROJMAN Project Progression
4 1.4.1.1 Submission of MCSPROJ Final Documents
4 1.4.1.2 Request Letter for Adviser/Consultant
3 1.4.2 PROJMAN Week 1-3
4 1.4.2.1 Creation of Project Charter
4 1.4.2.2 Creation of Business Case
4 1.4.2.3 Creation of Stakeholders Management Strategy Plan
3 1.4.3 PROJMAN Week 4-6
4 1.4.3.1 Creation of Scope Management Plan
4 1.4.3.2 Creation of Cost Management Plan
4 1.4.3.3 Creation of Time Management Plan
4 1.4.3.4 Creation of Work Breakdown Structure
4 1.4.3.5 Creation of Work Packages based on WBS.
3 1.4.4 System Updates
4 1.4.4.1 Testing 1
3 1.4.5 PROJMAN Midterm Evaluation
4 1.4.5.1 Submission of PROJMAN Midterm Requirements
4 1.4.5.2 PROJMAN Midterm presentation (Sprint 10)
3 1.4.6 PROJMAN Week 8-10
4 1.4.6.1 Creation of HR Management Plan
4 1.4.6.2 Creation of Quality Management Plan
4 1.4.6.3 Creation of Risk Management Plan
4 1.4.6.4 Creation of Communications Management Plan
4 1.4.6.5 Creation of Procurement Management Plan
3 1.4.7 PROJMAN Week 11
4 1.4.7.1 Creation of Project Status Reports Distribution Plan
4 1.4.7.2 Creation of Change Request Documentation
4 1.4.7.3 Creation of Project Execution Monitoring Report
4 1.4.7.4 Creation of Implementation Plan
3 1.4.8 PROJMAN Week 12
4 1.4.8.1 Creation of Change Management Plan
4 1.4.8.2 Creation of Project Status Reports
4 1.4.8.3 Creation of Transition-Out Plan
4 1.4.8.4 Creation of Project Turn-Over Plan
4 1.4.8.5 Creation of Post Project Review Plan
3 1.4.9 PROJMAN Week 13
4 1.4.9.1 Creation of Consolidated Project Plan
3 1.4.10 PROJMAN Final Evaluation
4 1.4.10.1 Submission of PROJMAN Final Requirements
4 1.4.10.2 PROJMAN Final presentation (Sprint 11)
2 1.5 Closeout
3 1.5.1 System and documentation handover
3 1.5.2 Gain Formal Acceptance
3 1.5.3 Project close out meeting

10.4 Tabular View

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

10.5 Tree Structure View

10.6 WBS Dictionary

The WBS Dictionary is a document that contains all the essential details of the Work Breakdown Structure (WBS) required to complete a project successfully. It includes a definition of each Work Package, which acts as a mini scope statement. The WBS Dictionary is an important reference for project resources to understand the scope of the Work Package assigned to them. Typically, the WBS Dictionary includes more information than what is shown in the sample, such as Level of Effort, Cost Control Numbers, Resource Assignments, Responsibility Assignments, and other relevant information.

Level 1

Level 2

Level 3

Level 4

1. Barangay South Signal Village Web App

1.1 Planning

1.1.1 Project Preparation

1.1.2 MNTSDEV Team consultation

1.1.3 MNTSDEV Creation of Midterm Paper

1.1.4 MNTSDEV Midterm Evaluation

1.1.5 Initial Design

1.1.6 MNTSDEV Progression of Paper/Final Paper

1.1.7 MNSTDEV Finals Evaluation

1.1.1.1 Creation of Project Groups

1.1.1.2 Choose Project/Client

1.1.1.3 Choose Adviser/Consultant

1.1.1.4 Design Thinking 1

1.1.2.1 Team meeting with Project adviser

1.1.2.2 Team meeting with Project Sponsor

1.1.3.1 Chapter 1 (Introduction)

1.1.3.2 Chapter 2 (RRL/RRS)

1.1.3.3 Chapter 3 (Methodology)

1.1.3.4 Chapter 4 (Results and Discussions)

1.1.3.5 Chapter 5 (Conclusion)

1.1.3.6 Proofreading

1.1.3.7 Creation of presentation deck

1.1.4.1 Midterm (Sprint1)

1.1.4.2 Comment Matrix

1.1.5.1 Initial wireframe

1.1.5.2 Initial low-fidelity prototype

1.1.6.1 Chapter 1 (Introduction)

1.1.6.2 Chapter 2 (RRL/RRS)

1.1.6.3 Chapter 3 (Current System)

1.1.6.4 Chapter 4 (Proposed System)

1.1.6.5 Chapter 5 (Requirement Analysis)

1.1.6.6 Chapter 6 (Conclusion)

1.1.6.7 Proofreading

1.1.6.8 Creation of presentation deck

1.1.6.9 Submission of final Requirements for Final Presentation

1.1.7.1 Final Presentation (Sprint 2)

1.1.7.2 Revision for Comment Matrix and Final Paper

1.1.7.3 Submission of MNSTDEV FINAL Documents

1.2.1.1 Initial analysis for Chapter 5 (Requirement Analysis)

1.2.1.2 Submission of MNSTDEV final documents

1.2.1.3 Implementation of GitHub Repository

1.2.1.4 Request letter for Adviser/Consultant

1.2.2.1 Team meeting with Project adviser

1.2.2.2 Team meeting with Project Sponsor

1.2.4.1 Release Plan 1.1

1.2.4.2 Release Plan 1.2

1.2.5.1 Event Table

1.2.5.2 Use Case Diagram

1.2.5.3 Use Case Full Description

1.2.5.4 Data Flow Diagram

1.2.5.5 Context Flow Diagram

1.2.5.6 Entity Relationship Diagram

1.2.6.1 Activity Diagram

1.2.6.2 Object Diagram

1.2.6.3 Class Diagram

1.2.7.1 Pre-midterm Presentation (Sprint 3)

1.2.7.2 Midterm Presentation (Sprint 4)

1.2.7.3 Revision Midterm

1.2.8.1 Sequence Diagram

1.2.8.2 State Machine Diagram

1.2.8.3 Package Diagram

1.2.8.4 Deployment Diagram

1.2.8.5 Component Diagram

1.2.9.1 MSYADD Pre-final Presentation (Sprint 5)

1.2.9.2 MSYADD Final Presentation (Sprint 6)

1.2.9.3 Revision for Final Paper

1.2.9.4 Submission of Final Requirements

1.2 Analysis and Design

Level 1

Level 1

1.3 Development

1.3.1 MCSPROJ Project Progression

1.3.2 MCSPROJ Release Plan

1.3.3 MCSPROJ Midterm Deliverables

1.3.4 MCSPROJ Team consultation

1.3.5 MCSPROJ Midterm Evaluation

1.3.6 MCSPROJ Finals Deliverables

1.3.7 MCSPROJ Finals Evaluation

1.3.1.1 Submission of MSYADD Final Documents

1.3.1.2 Request letter for Adviser/Consultant

1.3.2.1 Finalizing Release 1

1.3.2.2 Release Plan 2

1.3.2.3 Release Plan 3

1.3.3.1 Creation of Gantt Chart

1.3.3.2 Creation of WBS

1.3.3.3 Creation of Activity List

1.3.3.4 Creation of Project Vision and Scope Progression

1.3.3.5 Creation of Statement of Work Progression

1.3.3.6 Creation of Project Charter Progression

1.3.3.7 Pre-midterm Presentation (Sprint 7)

1.3.4.1 Team meeting with Project adviser

1.3.4.2 Team meeting with Project Sponsor

1.3.5.1 Submission of Midterm Requirement

1.3.5.2 MCSPROJ Final Presentation (Sprint 8)

1.3.6.1 Creation of Test Case

1.3.6.2 Creation of Quality Plan

1.3.6.3 Creation of User Acceptance

1.3.6.4 Creation of Change Management Plan

1.3.6.5 Updating MCSPROJ Final Paper

1.3.6.6 Creation of Proofreading Endorsement

1.3.7.1 Submission of MCSPROJ Final Requirements

1.3.7.2 MCSPROJ Final Presentation (Sprint 9)

1.4 Implementation

1.4.1 PROJMAN Project Progression

1.4.2 PROJMAN Week 1-3

1.4.3 PROJMAN Week 4-6

1.4.4 System Updates

1.4.5 PROJMAN Midterm Evaluation

1.4.6 PROJMAN Week 8-10

1.4.7 PROJMAN Week 11

1.4.8 PROJMAN Week 12

1.4.9 PROJMAN Week 13

1.4.10 PROJMAN Final Evaluation

1.4.1.1 Submission of MCSPROJ Final Documents

1.4.1.2 Request Letter for Adviser/Consultant

1.4.2.1 Creation of Project Charter

1.4.2.2 Creation of Business Case

1.4.2.3 Creation of Stakeholders Management Strategy Plan

1.4.3.1 Creation of Scope Management Plan



1.4.3.2 Creation of Cost Management Plan

1.4.3.3 Creation of Time Management Plan

1.4.3.4 Creation of Work Breakdown Structure



1.4.3.5 Creation of Work Packages based on WBS.

1.4.4.1 Testing 1

1.4.5.1 Submission of PROJMAN Midterm Requirements

1.4.5.2 PROJMAN Midterm presentation (Sprint 10)

1.4.6.1 Creation of HR Management Plan

1.4.6.2 Creation of Quality Management Plan

1.4.6.3 Creation of Risk Management Plan

1.4.6.4 Creation of Communications Management Plan

1.4.6.5 Creation of Procurement Management Plan

1.4.7.1 Creation of Project Status Reports Distribution Plan

1.4.7.2 Creation of Change Request Documentation

1.4.7.3 Creation of Project Execution Monitoring Report

1.4.7.4 Creation of Implementation Plan

1.4.8.1 Creation of Change Management Plan

1.4.8.2 Creation of Project Status Reports

1.4.8.3 Creation of Transition-Out Plan

1.4.8.4 Creation of Project Turn-Over Plan

1.4.8.5 Creation of Post Project Review Plan

1.4.9.1 Creation of Consolidated Project Plan

1.4.10.1 Submission of PROJMAN Final Requirements

1.4.10.2 PROJMAN Final presentation (Sprint 11)

1.5 Closeout

1.5.1 System and documentation handover

1.5.2 Gain Formal Acceptance

1.5.3 Project close out meeting.

1.5.1.1 System and documentation handover

1.5.1.2 Gain Formal Acceptance

1.5.1.3 Project close out meeting. '

10.7 Glossary of Terms

11. HR MANAGEMENT PLAN

11.1 Introduction

The Human Resource Plan establishes a comprehensive strategy for managing and organizing the project team. It ensures that the person assigned to each position is appropriately qualified at the right time. By using the Human Resource Plan, the roles of the project manager and project team can effectively handle and oversee the project's progress. This plan helps the team members gain knowledge and understanding on their roles and responsibilities in the project. Also, as pushes for open communication within the team members, which opens to more information exchange and problem solving. Overall, the Human Resource Plan is essential in guiding the management and the project team. The implementation it enables shows an effective project management by giving clarity in each role and provides a detailed road map for managing the people, which helps toward the success of the project outcome.

11.2 Roles and Responsibilities

Project Manager
  • The Project Manager is responsible for managing the project's scope and ensuring that it remains within the defined boundaries. This includes identifying and managing any changes to the scope, communicating scope changes to the team and stakeholders, and ensuring that the project's deliverables align with the scope. The Project Manager is also responsible for ensuring that the project is completed on time and meets the specified quality standards. 
Product Owner
  • The Product Owner is responsible for defining and prioritizing the project requirements and ensuring that the final product meets the needs of the Project Sponsor. They work closely with the Project Manager and Scrum Team to ensure that the project deliverables align with the scope. 
Scrum Master
  • The Scrum Master is responsible for facilitating the agile development process and ensuring that the team is following the Scrum framework. They work closely with the Project Manager and Product Owner to ensure that the project is progressing according to the defined scope. The Scrum Master is also responsible for identifying and managing any scope-related risks or issues. 
Scrum Team
  • The Scrum Team is responsible for developing the project deliverables and working together with the rest of the team to ensure the success of the project. This includes understanding and adhering to the project's scope, identifying any scope-related risks or issues, and communicating these to the Project Manager and Scrum Master.
Documentation Manager 
  • The Documentation Manager is responsible for managing the project documentation and ensuring it is complete and accurate. They work closely with the Project Manager and team to ensure that all project documentation aligns with the scope. 
Project Sponsor
  • The Project Sponsor is responsible for providing input on the project's scope, including requirements and expectations. Also, responsible for accepting the project deliverables defined by the project's scope. It is important for the Project Manager to communicate regularly with Project Sponsor to ensure that the project remains aligned with their needs and expectations. 

11.3 Project Organizational Charts

Project organizational chart of the Barangay South Signal Village Web Application provides a visual presentation of the project team, Team Developmentality, and the relationship with their client. The Product Sponsor is at the top of the organizational chart which provides resources and support for the project and is responsible for major decisions. Directly under the Project Sponsor is the Project Manager who oversees the project from planning through to closing phase. Under the Project Manager are the Product Owner who is responsible for maximizing the value of the product and managing the product backlog, Scrum Master who is facilitate the agile methodology among the team, removing any obstacles and ensuring the team adheres to its agreed processes, and the documentation manager who in charge of all documentation, ensuring all required information is recorded, organized, and maintained properly. The Scrum Members are attached directly to the Scrum Master who are responsible in developing the product and delivering the value.

11.4 Staffing Management

The Barangay South Signal Village Web App Team’s Staffing Management Plan will be extensively examined and monitored since it is crucial to the project's successful deployment. It consists of the techniques and procedures the team will use to secure, manage, and release employees over the course of the project.
  • The project sponsor will secure the required personnel for the project. This will guarantee that the roles will be filled with the necessary skills and responsibilities. Internal resources will make up most of the workforce responsible for managing the web application's use and maintenance.
  • Training will be provided by the team to each of the designated staff that will handle the web application. This will guarantee that the web application will be utilized to its fullest extent and lower any risk that could arise from a lack of training.
  • Performance reviews will be used and monitored often. This is done to evaluate each team member's contribution to the project. The performance reviews will act as a report to ensure that the team is fulfilling the requirements and goals of the project.
The project owner will continually review the project's requirements, scope, and objectives to see if any new information needs to be included in the staffing management plan. It is important to review the project’s scope since it will determine if other items will be included in the staffing management plan such as government regulations. Government regulations may be a consideration since the project is for a barangay. These regulations primarily involve data privacy and security and the requirements and specifications for a government owned web-application.

12. Quality Management Plan

12.1 Introduction

This Quality Management plan considers specific requirements and standards for the Barangay South Signal Village Web App project, covering various aspects of quality such as functionality, performance, security, usability, compatibility, and compliance. The plan promotes a collaborative and iterative approach inspired by Agile methodologies like Scrum. By incorporating continuous feedback and improvement cycles, the team proactively addresses issues, mitigates risks, and maintains desired quality levels throughout the project. Involving stakeholders in defining quality standards is crucial as it shapes the final product. Aligning quality objectives with stakeholder needs creates a web application that exceeds user expectations, increasing satisfaction and adoption. The Quality Management Plan consists of five components: Quality Management Approach, Quality Requirements / Standards, Quality Assurance, Quality Control, and Quality Control measurements. By following the principles outlined in the plan, the project team aims to deliver a strong, secure, and user-friendly web application that meets high-quality standards. Monitoring and measuring the effectiveness of quality management processes throughout the project life cycle allows necessary adjustments for success.

12.2 Quality Management Approach

Quality management is an ongoing process, and it's important to regularly review and improve the approach based on feedback and changing requirements. Here are the several key principles and approaches that the team followed to ensure a high level of quality.
  1. Requirement Analysis: The team must begin defining and documenting the web application requirements. This will include the functional and non-functional requirements. The team needs to ensure that the requirements are testable, measurable, and aligned to the user expectations.
  2. Test Planning: Develop a test plan that outlines the testing strategy, scope, and test objectives. Determine the testing tools and techniques that will be used in the project.
  3. Test Execution: Execute the test cases according to the test plan that the team made. Record and track all the test results, and issues encountered during the testing.
  4. Performance Testing: Conduct performance testing to evaluate the performance of the web application to know its responsiveness, scalability, and stability under expected and peak loads to optimize the application.
  5. Security Testing: The team needs to perform security testing to identify vulnerabilities and ensure the web application is protected and secured against potential threats. Review all the code to identify security vulnerabilities and implement best security practices.
  6. Usability Testing: The team needs to evaluate the usability and user experience of the web application by doing a real user in the testing process. Gather all the feedback from the clients and insights to identify areas for improvement in terms of user interface, navigation, and overall user satisfaction.
  7. Compatibility Testing: The web application needs to function correctly across different browsers, devices, and operating systems. The team needs to test the application on different combinations of browsers and versions to ensure a consistent performance and user experience.
  8. Continuous Monitoring: Always monitor the performance, availability, and usage of the web application in production. Resolve all issues proactively, ensure a optimal performance, and user satisfaction.

12.3 Quality Requirements/Standards

Regular review and updates of requirements and adherence to standards are necessary to maintain the desired quality throughout the web application's development and maintenance phases. Quality requirements and standards for web applications are crucial for ensuring that the application meets the desired level of quality and performance.
  1. Functional Requirements: This defines the expected behavior and functionality of the web application. This will specify what the application should do like user authentication, form submission, data retrieval, and other specific features relevant to the application domain.
  2. Performance Requirements: This will focus on the responsiveness, speed, and efficiency of the web application. This will include the metrics such as response time, page load time, and server processing time. Performance requirements will help ensure that the web application will perform well under normal and peak load conditions.
  3. Security Requirements: This is essential for the team to protect the web application and its users from potential vulnerabilities and threats they will encounter. It includes measures such as secure authentication and authorization mechanisms, and data encryption for protection.
  4. Compatibility Requirements: This ensures that the web application will function correctly across different browsers, devices, and operating systems. These requirements cover the aspects of cross-browser compatibility, mobile responsiveness, and the adherence to web standards.
  5. Usability Requirements: This requirement will focus on enhancing the user experience and ease of use of the web application. This will cover the navigation, clear user interface design, accessibility for users with disabilities, and responsiveness to user actions, and lastly the compatibility across different browsers and devices.
  6. Scalability Requirements: The team needs to address the ability of the web application to handle user loads and data volumes.
  7. Compliance Requirements: This involves adhering to legal, regulatory, and industry-specific standards. Since the web application will be handling sensitive information and data, the team needs to comply with GDPR (General Data Protection Regulation) guidelines.
  8. Documentation Standards: Comprehensive and consistent documentation is important for the web application. It will establish standards for documenting requirements, user manuals, release notes, design specifications, and other relevant documentation. It will help ensure transparency, collaboration, and ease of maintenance.

12.4 Quality Assurance

Quality Assurance (QA) for the South Signal Village Barangay Web App project will be rooted in Agile methodologies, promoting quality through iterative development, constant collaboration, and improvement. The following steps is followed to make sure the quality is in the standard:
  • Defining Quality Standards: In cooperation with stakeholders, we will describe and document the quality standards for the project within the Quality Management Plan. The plan is communicated to all stakeholders.
  • Continuous Improvement: The project team will leverage feedback from quality audits and quality metrics to enhance the product and quality process. Collaboration with stakeholders will be necessary to pinpoint improvement opportunities and to implement required changes.
  • Compliance with Industry Standards: The project team will ensure that the Barangay Web Application conforms to applicable industry standards, including data privacy regulations, accessibility standards, and security standards.
Quality assurance metrics will be monitored closely, tracked, and reported on a regular basis to guarantee that the project yields a high-quality outcome. Violations of these standards will prompt immediate review and revision. Regular reports from the application software will be utilized to gather data on these parameters. The goal is to ensure that the South Signal Village Barangay Web App adheres to the highest quality standards.

12.5 Quality Control

The quality control process is an integral part of the development and maintenance of the Barangay South Signal Village Web App. It ensures that all aspects of the application meet the defined quality standards and requirements. The following quality control measures will be implemented:

12.6 Quality Control Measurements

Level of Effort:

Level of Effort (LOE) is how much work is required to complete a task.

WBS Code:

A unique identifier assigned to each element in a Work Breakdown Structure for the purpose of designating the elements’ hierarchical location within the WBS

Work Package:

A Work Package is a deliverable or work component at the lowest level of its WBS branch.

WBS Component:

A component of a WBS which is located at any level. It can be a Work Package or a WBS Element as there's no restriction on what a WBS Component is.

WBS Element:

A WBS Element is a single WBS component, and its associated attributes are located anywhere within a WBS. A WBS Element can contain work, or it can contain other WBS Elements or Work Packages.

Clone this wiki locally