Software Project Management Plan

for

EcoQuest Trinidad
List of Tables

Table No. Description Page

Table 1.0 Milestone Task 6

Table 2.0 Definition, Acronyms, and Abbreviations 7
Table 3.0 Roles and Responsibilities 10
Table 4.0 Estimation of Effort 11
Table 5.0 Project Staffing Plan 13
Table 6.0 Work Activities 15
Table 7.0 Schedule Allocation 16
Table 8.0 Budget Allocation 17
Table 9.0 Risk Management Plan 20
Table 10.0 Methods, Tools, and Techniques 22
 Software Project Management Plan
EcoQuest Trinidad

1. Overview

1.1. Project Summary

1.1.1. Purpose, Scope and Objectives

The main purpose of EcoQuest Mobile is to promote environmental awareness and

community participation in eco-friendly activities within the Municipality of Trinidad, Bohol
through a gamified cross-platform mobile application. The system connects community
residents with their local government unit (LGU) by providing a digital platform where
citizens can participate in environmental challenges, report concerns, and contribute to
community improvements.

This project is developed to encourage residents to participate in sustainable actions such

as tree planting, waste reduction, clean-up drives, and other community environmental
programs. The traditional way of encouraging environmental participation relies heavily on
manual announcements, physical meetings, and paper-based monitoring, which often
results in low youth engagement, limited participation tracking, and slow response to
environmental concerns.

EcoQuest Mobile aims to provide the following features required by the target users:

Community Residents (Users)

• User Account Registration and Login: Implements secure user authentication using
token-based authentication (Laravel Sanctum), with email verification, forgot/reset
password, and encrypted token storage on the device.

• Profile Management: Allows users to maintain their personal profile including name,
alias, email, mobile, date of birth, gender, barangay/address, and avatar upload.

• Eco-Challenges (Quests): Enables users to browse a paginated list of quests with

search, view quest details, join quests, and submit completion proof consisting of a
text description and photo evidence captured via the device camera.

1
Software Project Management Plan
EcoQuest Trinidad

• Environmental Submissions: Enables users to submit Reports (waste, illegal dump-

ing, drainage, pollution, deforestation) and Suggestions (recycling programs, tree
planting, clean-up drives, plastic reduction, barangay ordinances). Submissions sup-
port photo attachments and offline voice-to-text input via Vosk in English and Fil-
ipino/Tagalog.

• EcoPoints Monitoring: Automatically calculates and updates user EcoPoints based

on completed quests. Displays current point balance, rank, and activity history within
the application.

• Leaderboard and Progress Tracking: Generates dynamic rankings of users based on

accumulated EcoPoints with community-wide leaderboard and pagination.

• Rewards Redemption: Allows users to exchange accumulated EcoPoints for avail-

able rewards. The system deducts points, logs transactions, and maintains redemp-
tion history.

• Social Sharing: Allows users to share achievements via Facebook, Instagram, X/

Twitter, or native device sharing using achievement cards generated with ViewShot.

• Support Ticket System: Enables users to create support tickets, view their ticket list,
and engage in threaded replies with administrators.

• Push Notifications: Receives real-time notifications via Firebase Cloud Messaging

with in-app notification banners and a notifications list screen.

• Activity History: Provides a chronological, paginated feed of user actions such as

quest_joined, quest_submitted, quest_approved, reward_redeemed, profile_up-
dated, and avatar_changed.

System Administrator

• Quest Management: Allows creation, activation, deactivation, and configuration of

eco-challenges including title, description, location, points, dates, category, and diffi-
culty.

• Submission Review: Enables administrators to review user quest completions and

environmental submissions, approving or rejecting them with reviewer notes.

2
 Software Project Management Plan
EcoQuest Trinidad

• Reward Management: Enables administrators to manage reward records including

creation, modification, deletion, point cost configuration, and inventory tracking.

• User Monitoring: Allows administrators to view user activity logs, participation

records, and submission history for moderation and misuse detection.

• Points and Progress Tracking: Provides administrative access to user point balances
and challenge completion data, with the ability to adjust points when necessary for
validation.

• Role-Based Access: Supports User, Admin, and Assistant Admin roles with differenti-
ated permissions.

However, the system is limited to the following:

• No integration of payment gateways for reward redemption.

• The proposed project is intended initially for Trinidad, Bohol only.

• Offline speech-to-text is limited to English and Filipino/Tagalog Vosk language mod-

els.

The goals of EcoQuest Mobile are to:

• Encourage sustainable environmental behavior through gamification and EcoPoints-

based rewards.

• Provide an accessible mobile platform for rural users with varying literacy levels
through voice-to-text input.

• Establish a direct communication channel between citizens and the LGU for environ-
mental concerns.

• Provide offline access through local caching and offline speech recognition.

• Deliver a functional and deployable mobile application within the capstone project
duration.

3
 Software Project Management Plan
EcoQuest Trinidad

1.1.2. Assumptions and Constraints

EcoQuest Mobile is designed as a client-server system. Therefore, the system will be built
using the following technologies:

• Mobile Application (Front-end): React Native 0.84.1 (CLI, not Expo) with React
19.2.3 and TypeScript.
• Navigation: React Navigation (Native Stack).
• HTTP Client: Axios for REST API communication.
• Back-end Framework: Laravel (PHP) — MVC Architecture.
• API Communication: RESTful API using JSON format over HTTPS.
• Authentication Mechanism: Laravel Sanctum (Bearer-token authentication) with Re-
act Native Encrypted Storage.
• Database Server: MySQL (via Laravel migrations).
• Push Notifications: Firebase Cloud Messaging (FCM) with Notifee for Android notifi-
cation channels.
• Offline Speech-to-Text: React Native Vosk with English and Filipino models.
• Development Tunneling: Ngrok for on-device backend testing.
The project is expected to be completed within 6 weeks (February 23, 2026 to April 3,
2026) and will undergo system testing and user acceptance evaluation thereafter.

Assumptions:

• Users have access to Android smartphones.

• Internet connectivity is available periodically for API synchronization, while core off-
line features (caching, speech-to-text) remain usable without connectivity.
• The development team has foundational knowledge of React Native, TypeScript,
PHP, and the Laravel framework.
• MySQL database server is available for development and deployment.
• Admin accounts will be pre-configured and authorized for system management func-
tions.

4
 Software Project Management Plan
EcoQuest Trinidad

Constraints:

• Limited development time due to academic schedule (six-week window).

• No allocated budget for paid hosting or premium services; the project relies on free-
tier tools.
• Voice-to-text functionality depends on device microphone quality and available stor-
age for Vosk models.

1.1.3. Project Deliverables

All of the items listed in this subsection are the deliverables that are to be provided
prior to completion of the project.

 Software Program (EcoQuest Mobile Application — Android APK build).

 Backend REST API (Laravel) deployed with MySQL database.
 Software Documentation (Software Engineering Documents).
 Software Requirements Specification (SRS).
 Software Design Document (SDD).
 Software Project Management Plan (SPMP).

1.1.4. Schedule and Budget Summary

This is the schedule summary of the project. On the other hand, minimal budget is
required during the conduct of the study. This project will utilize free-tier development tools
and hosting services. Estimated miscellaneous expenses (internet usage, documentation
printing) may cost approximately ₱1,000.

Date Completion
Milestone Task
Started Date

Project Proposal & Requirements Gathering Week 1 Week 1

System Design (Architecture, DB, UI/UX) Week 1 Week 2

Development Phase I (Authentication, Dashboard, Week 2 Week 3

5
Software Project Management Plan
EcoQuest Trinidad

Date Completion
Milestone Task
Started Date

Theme)

Software Test I Week 3 Week 3

Development Phase II (Quests, Submissions, Week 3 Week 4

Rewards)

Software Test II Week 4 Week 4

Development Phase III (Leaderboard, FCM, Support, Week 5 Week 5

Activity)

Final Testing and Deployment Week 6 Week 6

Table 1.0 Milestone Task

6
Software Project Management Plan
EcoQuest Trinidad

1.2. Evolution of Plan

All changes to the project management plan must be agreed upon by the project
manager before they are implemented. All changes shall be documented to ensure that
the project management plan remains accurate and up to date throughout the
development lifecycle.

1.3. Definition, Acronyms, and Abbreviations

Terms Definition

Eco-Points Virtual points earned by users for completing eco-chal-

lenges.
Quest An eco-friendly challenge that users complete to earn
EcoPoints.
FCM Firebase Cloud Messaging — push notification service by
Google.
Notifee Library for handling Android notification channels and lo-
cal display.
Vosk Open-source offline speech recognition toolkit.
API Application Programming Interface
REST Representational State Transfer — architectural style for
APIs.
Ngrok Tunneling service used for exposing local backends to
mobile devices.
STT Speech-to-Text.

Table 2.0 Definition, Acronyms, and Abbreviations

7
 Software Project Management Plan
EcoQuest Trinidad

1.4. References

[1] IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans, Institute
of Electrical and Electronics Engineers, 1998.

[2] IEEE Std 830-1998, IEEE Recommended Practice for Software Requirements
Specifications, Institute of Electrical and Electronics Engineers, 1998.

[3] Schwaber, K. & Sutherland, J. (2020). The Scrum Guide.

[4] React Native Documentation. Available: [Link]

[5] Laravel Documentation. Available: [Link]

[6] Laravel Sanctum Documentation. Available: [Link]

[7] Firebase Cloud Messaging Documentation. Available:

[Link]

[8] Vosk Offline Speech Recognition Toolkit. Available: [Link]

[9] MySQL Documentation. Available: [Link]

[10] REST Architectural Style. Fielding, R. T. (2000). Architectural Styles and the Design of
Network-based Software Architectures.

[11] Republic Act No. 9003 — Ecological Solid Waste Management Act of the Philippines.

8
 Software Project Management Plan
EcoQuest Trinidad

2. Project Organization

2.1. External Structure

The EcoQuest Mobile project is developed by a student capstone team under the
academic supervision of a faculty adviser who acts as the Product Owner proxy. Externally,
the team coordinates with the following stakeholders and third-party services:

• Faculty Adviser — Provides academic supervision, validates project direction, and

approves deliverables.
• End Users (Community Residents) — Participate in usability testing and provide
feedback for refinement.
• Google Firebase — Third-party cloud platform providing push notification infrastruc-
ture via FCM.
• Vosk Project — Open-source provider of offline speech recognition language mod-
els.
• Ngrok — Development tunneling service used to expose the local Laravel backend
to on-device testing.
• GitHub — Source-code hosting and version control platform.

2.2. Internal Structure

The project team is a flat, self-organizing cross-functional unit of five (5) student
developers. Every member contributes to design, implementation, and testing activities.
Role accountabilities are distributed to ensure coverage of all project concerns, but
responsibilities overlap to facilitate peer learning and risk mitigation. The Project Manager
also serves as the Scrum Master and is the primary point of contact with the faculty adviser
and external stakeholders. The internal communication channels are daily stand-up
meetings, a shared group chat for asynchronous updates, and weekly sprint ceremonies.

9
Software Project Management Plan
EcoQuest Trinidad

2.3. Roles and Responsibilities

Role Team Member Primary Responsibility

Project Manager / Scrum Charl Hans Adrian Acuesta Overall planning, sprint
Master facilitation, risk
management, stakeholder
communication, and SPMP
maintenance.

Lead Mobile Developer Charl Hans Adrian Acuesta React Native architecture,
navigation structure, core
mobile features, and
device-side integrations.

Backend Developer Charl Hans Adrian Acuesta Laravel REST API,

database schema and
migrations, authentication
with Sanctum, and server-
side business logic.

UI/UX Designer & Charl Hans Adrian Acuesta Design system, theming
Frontend Dev (dark/light), screen layouts,
and user experience
refinement.

QA / Integration Engineer Eugene Wahing Unit/integration testing,

Ashley Joy Besan FCM integration, offline-
Michael Dave Payot support validation, and
Jefferson Salem deployment support.

Table 3.0 Roles and Responsibilities

10
 Software Project Management Plan
EcoQuest Trinidad

3. Managerial Process Plans

3.1. Start-up Plan

3.1.1. Estimation Plan

Effort estimation was performed at the work-package level using expert judgment
and analogy with past academic projects of similar scope. The team used story-point
estimation during sprint planning to refine backlog items. The total estimated effort for the
project is approximately 840 person-hours, distributed across six weeks for a team of five
members averaging 28 hours per week per member.

Work Package Estimated Hours Percentage

Project Initiation & Planning 60 7%

System Design 90 11%

Backend Development 210 25%

Mobile Application Development 280 33%

Integration & Testing 110 13%

Documentation 70 8%

Deployment & Turnover 20 3%

TOTAL 840 100%

Table 4.0 Estimation of Effort

11
 Software Project Management Plan
EcoQuest Trinidad

3.1.2. Staffing Plan

The project employs a stable team of five (5) members for the full duration of the
engagement. No additional hires are planned. All members begin work on February 23,
2026 and continue through April 3, 2026. Skill requirements include proficiency in React
Native/TypeScript, Laravel/PHP, MySQL, Git workflows, and basic understanding of
Firebase Cloud Messaging. Gaps in knowledge are addressed through pair programming
and peer knowledge transfer sessions scheduled at the start of each sprint.

3.1.3. Resource Acquisition Plan

The following resources are required and their acquisition strategy is summarized below:

• Developer laptops — provided by individual team members (no procurement

needed).

• Android test devices — sourced from team members' personal phones (minimum
three devices running Android 10 or newer).

• GitHub private repository — created on project kick-off using a free educational

account.
• Firebase project — created under a free Spark plan; credentials shared via secure
team vault.

• Figma workspace — created under a free plan for UI/UX mockups.

• Ngrok account — free tier for development tunneling.

• Laravel hosting (development) — local XAMPP/Laragon environments on each

member's machine.

3.1.4. Project Staffing Plan

Member Role Hours/Week Duration

Charl Hans Adrian PM / Scrum Master 25 Feb 23 – Apr 3

Acuesta

Charl Hans Adrian Lead Mobile Dev 30 Feb 23 – Apr 3

12
 Software Project Management Plan
EcoQuest Trinidad

Member Role Hours/Week Duration

Acuesta

Charl Hans Adrian Backend Dev 30 Feb 23 – Apr 3

Acuesta

Charl Hans Adrian UI/UX & Frontend 28 Feb 23 – Apr 3

Acuesta

Eugene Wahing QA / Integration 10 Feb 23 – Apr 3

Michael Dave Payot
Jefferson Salem
Ashley Joy Besan

Table 5.0 Project Staffing Plan

3.2. Work Plan

3.2.1. Work Activities

The project work is decomposed into the following major activities organized by work
package:

ID Work Activity Description

WP1 Project Initiation & Kick-off, requirements gathering, SPMP and

Planning SRS preparation, backlog creation.

WP2 System Design System architecture, MySQL database schema,

REST API specification, UI/UX mockups, and
design system.

WP3.1 Backend — Auth & Users Register, login, email verification, forgot/reset
password, profile management, Sanctum

13
Software Project Management Plan
EcoQuest Trinidad

ID Work Activity Description

tokens, FCM token registration.

WP3.2 Backend — Quests & Challenges table, user_challenges workflow,

Submissions submissions (REPORT/SUGGESTION), review
workflow, media uploads.

WP3.3 Backend — Rewards & Rewards, redemptions, points_logs,

Leaderboard leaderboard ranking endpoint, activity logs.

WP3.4 Backend — Support & Support tickets, threaded replies, notifications,

Notifications shares logging, addresses/barangay data.

WP4.1 Mobile — Navigation & Root and main navigation stacks, splash,
Theme dark/light theme, AsyncStorage persistence.

WP4.2 Mobile — Auth Screens Login, register, email verification, forgot/reset

password, encrypted token storage, session
expiry handling.

WP4.3 Mobile — Dashboard & Home dashboard with EcoPoints/rank, quest

Quests browsing/search, quest detail, join, and
completion submission.

WP4.4 Mobile — Submissions & Reports/suggestions with photo attachment,

STT offline Vosk voice-to-text (English/Filipino),
network check.

WP4.5 Mobile — Rewards, Reward list, redemption, leaderboard

Leaderboard, Sharing pagination, ViewShot achievement cards, social
sharing.

WP4.6 Mobile — Support, Support tickets (list/create/detail), notifications

Notifications, Activity list, activity history feed.

WP4.7 Mobile — Offline & Profile Offline caching (dashboard, quests,

14
Software Project Management Plan
EcoQuest Trinidad

ID Work Activity Description

leaderboard), profile management with avatar

upload.

WP5 Integration & Testing End-to-end integration, unit tests (Jest,

PHPUnit), integration tests

WP6 Documentation SRS, SDD, API reference, README and

developer notes.

WP7 Deployment & Turnover Final APK build, backend deployment, training
session, source and documentation handover.

Table 6.0 Work Activities

3.2.2. Schedule Allocation

The six-week project schedule is organized into three (3) two-week Scrum sprints
bracketed by a planning week and a deployment week.

Sprint Dates Sprint Goal

Planning Feb 23 – Mar 01 Finalize SPMP, SRS, architecture, database

schema, API spec, and UI/UX mockups.

Sprint 1 Mar 02 – Mar 13 Establish authentication, dashboard, theme

system, and FCM token registration. Deliver
working login, registration, email verification, and
EcoPoints dashboard.

Sprint 2 Mar 16 – Mar 27 Implement core engagement features: quest

browsing/joining/completion, environmental
submissions with offline STT, and rewards
redemption.

15
Software Project Management Plan
EcoQuest Trinidad

Sprint Dates Sprint Goal

Sprint 3 Mar 23 – Apr 01 Complete leaderboard, push notifications, support

ticket system, activity history, social sharing, and
perform UAT/polish.

Deployment Apr 02 – Apr 03 Final build, documentation finalization, and

project turnover.

Table 7.0 Schedule Allocation

3.2.3. Resource Allocation

Human and material resources are allocated to work packages as follows:

• WP1 (Initiation) — Project Manager leads, supported by all team members.

• WP2 (Design) — Backend Dev owns DB design, UI/UX Designer owns mockups,
Mobile Dev contributes to API contracts.

• WP3 (Backend) — Backend Dev as primary owner, QA Engineer contributes to inte-

gration tests.

• WP4 (Mobile) — Lead Mobile Dev and UI/UX Designer as primary owners, PM sup-
ports.

• WP5 (Testing) — QA Engineer leads, all developers support.

• WP6 (Documentation) — Project Manager owns overall documentation; each mem-

ber contributes to their area.

• WP7 (Deployment) — PM and QA lead, Mobile Dev and Backend Dev support.

16
 Software Project Management Plan
EcoQuest Trinidad

3.2.4. Budget Allocation

All tools and services used are free-tier or already available to the team.

Item Estimated Cost Source

(₱)

Internet connectivity (development) 500 Team members

Mobile data for on-device testing 300 Team members

Documentation printing (final) 400 Team members

Miscellaneous (USB, cables, backup) 300 Team members

TOTAL ESTIMATED BUDGET 1,500 —

Table 8.0 Budget Allocation

3.3. Control Plan

3.3.1. Requirements Control Plan

All requirements are documented in the SRS and tracked in the product backlog. Any
change request must be submitted to the Project Manager, evaluated against impact on
schedule and effort, and approved by the faculty adviser before being added to the
backlog. Traceability from requirements to backlog items, test cases, and delivered features
is maintained using a requirements traceability matrix.

3.3.2. Schedule Control Plan

Progress against schedule is monitored daily through stand-up meetings and weekly
through sprint burndown charts maintained in the team's project management tool. Any
slippage greater than ten percent in a sprint triggers a corrective action discussion in the
next daily stand-up. Tasks at risk of missing the sprint boundary are either de-scoped, re-

17
 Software Project Management Plan
EcoQuest Trinidad

assigned, or escalated to the Project Manager.

3.3.3. Budget Control Plan

Because the project operates on a minimal budget (₱1,500 total), expenditure tracking is
straightforward. The Project Manager maintains a simple expense log. All expenses require
approval from the Project Manager before reimbursement. The team avoids paid services
and uses only free-tier infrastructure.

3.3.4. Quality Control Plan

Quality is maintained through the following mechanisms:

• Definition of Done for every backlog item: code merged to develop branch, peer re-
viewed, unit tests passing, documentation updated, and acceptance criteria verified.

• Automated linting with ESLint + Prettier (mobile) and Laravel Pint (backend).

• Unit testing with Jest (mobile) and PHPUnit (backend).

• Sprint Review demonstrations to validate features against stakeholder expectations.

3.3.5. Reporting Plan

The Project Manager submits a weekly status report to the faculty adviser summarizing
progress, blockers, risks, and upcoming milestones. Sprint Review outcomes are
documented and shared with all stakeholders. Daily stand-up notes are recorded in the
team chat for asynchronous reference. A final project closeout report is prepared at the end
of the engagement.

3.3.6. Metrics Collection Plan

The following project metrics are collected and reviewed:

• Sprint velocity (story points or tasks completed per sprint).

• Burndown rate (tasks remaining vs. time remaining).

18
 Software Project Management Plan
EcoQuest Trinidad

• Defect count per sprint (bugs found during sprint review and testing).

• Code coverage percentage from unit tests.

• Build success rate from the CI pipeline.

• Open risk count and severity distribution.

3.3.7. Risk Management Plan

Risks are identified at project initiation and reviewed at every sprint planning session.
Probability and impact of each risk are rated on a three-point scale (Low/Medium/High),
and the overall risk level is derived from their combination. The following table presents the
initial risk register.

ID Risk Prob. Impact Level Mitigation Strategy

R1 Scope creep from High High High Enforce change control

new feature via PM; defer non-critical
requests items to post-project
backlog.

R2 Team member Medium High High Cross-train members;

illness or document all work;
unavailability shared repository access.

R3 Integration issues Medium High High Define API contracts

between mobile early; use Postman
and Laravel API collections; per-sprint
integration tests.

R4 FCM push Medium Medium Medium Test on multiple devices;

notifications monitor FCM reports;
unreliable delivery implement fallback

19
Software Project Management Plan
EcoQuest Trinidad

ID Risk Prob. Impact Level Mitigation Strategy

polling.

R5 Vosk STT model Medium Medium Medium Use small Vosk models;
size bloats the APK lazy-download on first
use; compress assets.

R6 iOS build delays High Medium High Prioritize Android; secure

(limited macOS macOS early; consider
access) cloud iOS build.

R7 Inaccurate Low High Medium Server-side validation;

EcoPoints unit tests on points logic.
computations

R8 Security Medium High High Follow Sanctum best

vulnerabilities in practices; encrypted
auth flow storage; code reviews;
security checklist.

R9 Low user adoption Medium Medium Medium Engage barangay officials

during pilot early; conduct onboarding
workshops; incentivize
participation.

R10 Loss of source due Low High Medium Daily commits to remote
to hardware failure Git; local backups.

Table 9.0 Risk Management Plan

3.3.8. Project Closeout Plan

Upon completion of all deliverables, the Project Manager will conduct a formal project

20
 Software Project Management Plan
EcoQuest Trinidad

closeout. This includes: (1) turnover of source code, documentation, and deployment
artifacts; (2) archiving of project assets in the team repository; (3) conducting a final team
retrospective to capture lessons learned; and (4) submission of the final closeout report to
the faculty adviser.

21
 Software Project Management Plan
EcoQuest Trinidad

4. Technical Process Plans

4.1. Process Model

The EcoQuest Mobile project adopts an Agile software development methodology using the
Scrum framework. Agile was selected because the project requirements are expected to
evolve as user feedback is obtained, and the short six-week timeline demands iterative
delivery of working features rather than a single big-bang release.

The project is divided into three (3) two-week sprints bracketed by a planning week and a
deployment week. Each sprint follows the standard Scrum ceremonies: Sprint Planning at
the start, Daily Stand-ups (15 minutes) throughout, Sprint Review to demonstrate a
potentially shippable increment, and a Sprint Retrospective to identify process
improvements. Backlog refinement is scheduled mid-sprint to clarify and estimate
upcoming items.

4.2. Methods, Tools, and Technique

The system is built using a client-server architecture. The mobile application communicates
with the Laravel REST backend over HTTPS using Axios. Authentication uses Bearer
tokens from Laravel Sanctum, stored in React Native Encrypted Storage. Session expiry
(HTTP 401 responses) triggers automatic logout and a navigation reset.

Technology / Tool Purpose

React Native 0.84.1 (CLI) Cross-platform mobile framework for Android & iOS.

React 19.2.3 + UI library with static typing.

TypeScript

React Navigation (Native Screen navigation and routing.

Stack)

Axios HTTP client for REST API calls.

22
Software Project Management Plan
EcoQuest Trinidad

Technology / Tool Purpose

Firebase Cloud Push notification delivery.

Messaging

Notifee Android notification channels and local display.

React Native Encrypted Secure storage of authentication tokens.

Storage

AsyncStorage Theme preferences and offline caching.

React Native Image Crop Photo capture and upload.

Picker

React Native Vosk Offline speech-to-text (English and Filipino).

React Native Share + Social sharing of achievement cards.

ViewShot

NetInfo Network connectivity detection.

DateTimePicker Date of birth input.

Laravel (PHP) REST API, routing, ORM, and middleware.

Laravel Sanctum Bearer-token API authentication.

MySQL Relational database for persistent storage.

Ngrok Development tunneling for on-device testing.

Git / GitHub Version control and code hosting.

Jest / PHPUnit Unit testing (mobile / backend).

Figma UI/UX mockups and design system.

Table 10.0 Methods, Tools, and Techniques

23
 Software Project Management Plan
EcoQuest Trinidad

4.3. Infrastructure Plan

The infrastructure required to support development, testing, and deployment is described

below:

• Development environment: each member runs a local Laravel (XAMPP/Laragon) +

MySQL stack on their laptop, paired with the React Native CLI toolchain for mobile
development.

• Version control: a private GitHub repository hosts all source code and documenta-
tion with branch protection on main and develop.

• Development tunneling: Ngrok exposes the local Laravel backend to physical An-
droid devices during testing.

• Push notifications: a Firebase project (Spark plan) provides FCM credentials and a
management console.

• Communication: team group chat for asynchronous updates; video conferencing for
sprint ceremonies.

4.4. Product Acceptance Plan

The product is considered accepted when it satisfies the following criteria: (1) all high-
priority functional requirements in the SRS are implemented and verified; (2) unit and
integration tests pass with no critical defects open; (3) the Android APK installs and runs on
a clean device with all core flows (login, quest completion, submission with STT,
leaderboard, rewards redemption) functioning end-to-end; (4) all documentation
deliverables are reviewed and approved by the faculty adviser. Acceptance is formally
recorded in the project closeout report.

24
 Software Project Management Plan
EcoQuest Trinidad

5. Supporting Process Plans

5.1. Verification and Validation Plan

Verification ensures the product is built correctly, and validation ensures the right product is
built.

Verification activities:

• Code reviews on all pull requests before merging.

• Unit tests with Jest (mobile) and PHPUnit (backend) run on every commit.

• Static analysis via ESLint + Prettier (mobile) and Laravel Pint (backend).

• Integration tests between mobile app and Laravel API performed at the end of each
sprint.

Validation activities:

• Sprint Review demonstrations to the faculty adviser acting as Product Owner.

• Formal User Acceptance Testing session with barangay representatives in Week 6.

• Usability feedback collection from community residents during pilot testing.

5.2. Documentation Plan

The following documentation artifacts are produced and maintained throughout the project:

• Software Requirements Specification (SRS) — functional and non-functional require-

ments, use cases.

• Software Project Management Plan (SPMP) — this document, updated as a living

artifact.

• Software Design Document (SDD) — architecture, database schema, API spec,

UI/UX mockups.

25
 Software Project Management Plan
EcoQuest Trinidad

5.3. Quality Assurance Plan

Quality assurance is the responsibility of every team member, with the QA / Integration
Engineer leading the QA function. The QA Plan includes: (1) a Definition of Done applied to
every backlog item; (2) mandatory peer reviews on all pull requests; (3) unit and integration
test coverage targets; (4) defect tracking in GitHub Issues with severity classification; (5)
bug triage at the start of each daily stand-up; and (6) a final QA pass before deployment
that exercises every critical user flow on a clean Android device. The QA Engineer also
maintains a checklist of security considerations including encrypted token storage, HTTPS
enforcement, input validation, and authorization checks on all protected endpoints.

5.4. Problem Resolution Plan

Problems encountered during the project — including technical defects, blocked tasks,
interpersonal conflicts, and external dependencies — are handled through a tiered
escalation process:

• Tier 1 — Individual: the assigned team member attempts to resolve the problem in-
dependently, consulting documentation and peers.

• Tier 2 — Team: if unresolved within one working day, the issue is raised in the daily
stand-up and addressed collaboratively.

• Tier 3 — Project Manager: persistent blockers are escalated to the PM, who may re-
prioritize the sprint backlog, re-assign tasks, or request external assistance.

• Tier 4 — Faculty Adviser: issues that threaten project scope, schedule, or deliverable
quality are escalated to the faculty adviser for guidance and arbitration.

All problems and their resolutions are logged in the project issue tracker (GitHub Issues) to
build an institutional memory for the team and support retrospective analysis.

26