GJJSP‐SIS PAGE 3 - apcjlquesada/APC_2023_2024_3rd_Term_PROJMAN GitHub Wiki

Table of Contents

5.11 IMPLEMENTATION MANAGEMENT PLAN

5.11.1 Executive Summary

The implementation plan focuses on deploying the GJJSP-SIS smoothly. Activities include setup, configuration, and system integration. The goal is to improve user experience by assessing the current system, gathering requirements, selecting suitable technologies, designing the architecture, and developing the system using best practices.

The project team, including a project manager, quality assurance tester, scrum master, document specialist, product designer, and developers, will work together to ensure a successful transition. Workforce transition will involve assessing skills, providing training, and possibly recruiting new talent. Property transition will include evaluating infrastructure, integrating systems, and conducting thorough testing. The schedule ensures efficient execution and timely completion. Overall, the plan aims to deliver a user-friendly platform while effectively managing workforce and infrastructure transitions.

5.11.2 Transition Approach

This section outlines the strategy and steps for implementing the GJJSP-SIS. It serves as a roadmap for migrating from the current system to the new one.

The transition plan for the GJJSP-SIS project includes several key steps to ensure a smooth change from the old system to the new one. First, the team will evaluate the current system to identify its strengths, weaknesses, and check if the infrastructure is ready. Then, they will gather detailed requirements from stakeholders, covering both functional and non-functional aspects.

Based on these requirements, the team will select appropriate technologies and frameworks, considering compatibility and scalability. They will then develop an architectural design that ensures functionality, scalability, security, and integration. The new system will be implemented according to this design, following best practices and coding standards.

Comprehensive testing will be conducted, including unit, integration, system, and user acceptance tests, to ensure everything works correctly. Training materials will be developed, training sessions conducted, and user manuals and technical guides created.

For deployment, the production environment will be prepared to ensure scalability, security, and performance, and then the system will be deployed. The team will coordinate with the GJJSP team to ensure a smooth transition from the old system to the new one and provide support as needed.

Finally, the transition process will be evaluated, feedback gathered, areas for improvement identified, and lessons learned documented.

5.11.3 Team Organization

This section provides an overview of the team members involved in the project, their roles, and responsibilities.

Table 5.21 Team Organization

Role Responsibilities
Project Manager Oversee the transition, lead the team, ensure task completion, coordinate with stakeholders.
Quality Assurance Tester Conduct testing activities, develop test plans, execute test cases, identify and report bugs.
Scrum Master Facilitate agile development, organize and lead meetings, remove obstacles, promote collaboration.
Document Specialist Create and maintain project documentation, including requirements, user manuals, and technical guides.
Product Designer Design and prototype the UI/UX, ensuring a visually appealing and user-friendly design.
Frontend Developer Develop client-side components, implement the UI/UX design, ensure responsive and interactive interfaces.
Backend Developer Develop server-side components, handle data processing, integrate with databases, implement business logic.

5.11.4 Workforce Transition

This section outlines the plan for managing workforce transition during the implementation of GJJSP-SIS.

  1. Assess the Current Workforce: Evaluate the existing workforce's skills, knowledge, and capabilities relevant to the new system.
  2. Identify Skill Requirements: Determine the skills needed for the new system, identify specific roles and responsibilities.
  3. Internal Workforce Training: Provide training programs and resources to upskill current employees.
  4. Recruitment and Hiring: Recruit new employees or contractors to fill skill gaps, develop job descriptions, conduct interviews.
  5. Knowledge Transfer: Facilitate knowledge transfer through mentoring, shadowing, or collaborative work.
  6. Team Integration: Encourage open communication, knowledge sharing, and cross-functional collaboration.
  7. Performance Evaluation: Establish mechanisms to assess progress, provide regular feedback, and recognize achievements.
  8. Employee Support: Provide support and resources, including training materials, documentation, and technical support.
  9. Change Management: Manage resistance to change, communicate benefits, and provide support to facilitate transition.
  10. Ongoing Training: Continue investing in professional development through workshops and certifications.

5.11.5 Workforce Execution During Transition

Key aspects of workforce execution during the transition include:

  • User Training: Provide training programs to equip employees with the necessary knowledge and skills.
  • System Launch: Ensure all systems are in place and functioning before launch, conduct final tests, and verify data migration.
  • Lessons Learned Documentation: Document insights gained, highlight areas of success and improvement for future projects.
  • Updating Files/Records: Update relevant files and records to reflect project completion.
  • Formal Acceptance: Obtain formal acceptance from stakeholders, ensuring all deliverables are met.
  • Archiving Files/Documents: Archive all project-related files and documents.
  • Project Closeout Meeting: Conduct a meeting to review overall performance, acknowledge successes, and address remaining issues.

5.11.6 Subcontracts

There are no existing contracts or subcontract agreements associated with the GJJSP-SIS project, so there is no need for transition or transfer of such contracts.

5.11.7 Property Transition

Steps for evaluating and utilizing incumbent-owned equipment:

  1. Infrastructure Assessment: Assess existing infrastructure, including servers, networking equipment, databases, and other hardware and software.
  2. Repurposing Existing Equipment: Determine if existing equipment can be used for the new system, considering scalability and performance.
  3. Equipment Replacement: Develop a plan for replacing inadequate equipment, specifying criteria for selecting new equipment.
  4. Integration and Configuration: Outline procedures for integrating existing and new equipment, ensuring seamless operation.
  5. Testing and Validation: Develop a plan to test and validate the compatibility and functionality of the infrastructure.
  6. Documentation and Knowledge Transfer: Document details of equipment and facilitate knowledge transfer among team members.

5.11.8 Knowledge Transfer 

 Documentation and training plan includes:
  • Documentation: Prepare comprehensive documentation covering system overview, architecture, technical specifications, and relevant materials.
  • Training: Provide personalized training and access to online resources for continuous learning.
  • Regular Check-ins: Schedule regular meetings with stakeholders to ensure successful knowledge transfer.

5.11.9 Schedule

This schedule outlines the key activities involved in the transition out phase, ensuring a smooth and successful transition from the current system to the new GJJSP-SIS platform.

Table 5.22 Transition Out Plan Schedule

Task Description Start Date End Date
Assess Current System Evaluate existing system, identify strengths, weaknesses, and limitations, and assess readiness. 04/18/2023 04/27/2023
Gather Requirements Engage stakeholders to gather detailed functional and non-functional requirements. 04/18/2023 04/21/2023
Select Technologies Choose appropriate technologies and frameworks for the new system. 04/21/2023 04/27/2023
Design Architecture Develop an architectural design considering functionality, scalability, security, and integration. 05/16/2023 05/23/2023
Develop System Implement the new system based on the architectural design using best practices. 05/19/2023 06/10/2023
Conduct Testing Perform unit, integration, system, and user acceptance testing. 05/19/2023 06/10/2023
Provide Training and Documentation Develop training materials, conduct training sessions, and create user manuals and guides. 06/13/2023 06/22/2023
Deploy System Prepare the production environment and deploy the system ensuring scalability and security. 06/13/2023 06/22/2023
Transition to Production Coordinate with the team for a smooth transition, provide necessary support. 06/13/2023 06/22/2023
Post-Transition Evaluation Evaluate the transition process, gather feedback, and document lessons learned. 06/13/2023 06/22/2023
Conduct Project Closeout Meeting Review overall performance, acknowledge successes, and address any remaining issues. 06/13/2024 06/13/2024

5.11.10 Handover and Acceptance

This section shows the final stage of the implementation process for the GJJSP-SIS. Final stage activities include:

  1. Documentation Handover: Compile and hand over all relevant project documentation.
  2. Training and Knowledge Transfer: Conduct training sessions and knowledge transfer activities.
  3. User Acceptance Testing: Stakeholders participate in testing to validate functionality and performance.
  4. Sign-off and Acceptance: Obtain formal sign-off and acceptance from stakeholders.
  5. Handover of Administrative Rights: Grant necessary administrative rights and access privileges.
  6. Post-Implementation Support: Provide support to address any issues during the initial period of system operation.

By following this plan, the GJJSP-SIS project aims to ensure a smooth transition, effective management of the workforce and infrastructure, and successful implementation of the new system.

SPONSOR ACCEPTANCE

Approved by the Project Sponsor

_June 11,2024__

Mrs. Maria Victoria Borres Date Project Sponsor

REFERENCES

      1. References
1. G. B. R. Artajos, M. P. L. Flores, J. R. C. Rosel, and L. D. M. Salazar, "Chubby Gourmet's E-commerce Web Application," Project Management Plan, HighTable, Asia Pacific College, [Accessed:].

2. Y. Danielsson and P. Skog, "A development of a tool to improve traceability between requirement and verification," Lund University, 2014. [Online]. Available: https://lup.lub.lu.se/student-papers/record/4499697/file/4499708.pdf(https://lup.lub.lu.se/student-papers/record/4499697/file/4499708.pdf). [Accessed:].

3. Project Management Institute, Practice Standard for Work Breakdown Structures. Newtown Square, PA: Project Management Institute, 2006.

4. “1,000+ Full Stack Developer Jobs, Employment 28 May, 2024| Indeed.com,” [Indeed.com](https://ph.indeed.com/q-full-stack-developer-jobs.html?vjk=c5cc2265d382c0f5&advn=5087089626359147) (accessed May 27, 2024).

5. “1,000+ Project Manager Tech Jobs, Employment 28 May, 2024| Indeed.com,” [Indeed.com](https://ph.indeed.com/jobs?q=project+manager+tech&l=&from=searchOnDesktopSerp&vjk=52d9e8b4feb3f2b2) (accessed May 27, 2024).

6. “3,000+ Document Specialist Jobs, Employment 28 May, 2024| Indeed.com,” [Indeed.com](https://ph.indeed.com/jobs?q=document+specialist&l=&from=searchOnDesktopSerp&vjk=b5aba0273820ed9d) (accessed May 28, 2024).

7. “Inspiron 15 Laptop,” [Dell](https://www.dell.com/en-the team/shop/dell-laptops/inspiron-15-laptop/spd/inspiron-15-3520-laptop) (accessed May 28, 2024).

8. “MX Palm Rest,” [Logitech.com](https://www.logitech.com/en-ph/products/mice/m330-silent-plus-mouse.html) (accessed May 28, 2024).

9. “H390 USB Computer Headset,” [Logitech.com](https://www.logitech.com/en-ph/products/headsets/h390-usb-headset.981-001287.html) (accessed May 28, 2024).

10. J. Kotter, “The 8 Steps for Leading Change,” [Kotter](https://www.kotterinc.com/methodology/8- steps/)

11. [React](https://react.dev)

12. [Material-UI](https://mui.com/)

13. [Laravel](https://laravel.com/)

14. [REST](https://restfulapi.net/)

15. [Docker](https://www.docker.com/)

16. [Nginx](https://www.nginx.com/)

17. [PhpMyAdmin](https://www.phpmyadmin.net/)

18. [MySQL](https://www.mysql.com/)

19. [Linode](https://www.linode.com/)

20. [AWS](https://aws.amazon.com/)

21. Work Breakdown Structure, “Work Breakdown Structure (WBS): The Ultimate Guide (with Examples),” [ProjectManager](https://www.projectmanager.com/guides/work-breakdown-structure) (accessed Jun. 12, 2024).

22. Association for Project Management. "What is scheduling in project management?" APM Body of Knowledge, 7th edition, [www.apm.org.uk](www.apm.org.uk). Accessed 13 June 2024.

APPENDICES

Appendix A: Cost Change Request Form

Change Number:
Project Name:
Prepared by:
Date:
Person(s) Requesting Change:
Detailed Description of Cost Change Requested:
Reason for Cost Change Requested:
Overall Effect on Project Cost
• Projected Cost Overrun of approximately:
• Estimated Cost Reduction of approximately:
Effect on Schedule:
• Planned Project Completion Date:
• New Project Completion Date:
Effect on Scope:
Additional Remarks:
Approval
Project Manager
Date
Approval
Project Sponsor
Date

Appendix B: Change Request Form

Change Description
Change Name:
Contact:
Description of Change:
Reason for Change:
Priority [Shade]: Medium
Impact on Deliverables:
Impact of Not Responding to Change:
Approval of Request:
Change Impact
Tasks/Scope Affected:
Cost Evaluation:
Risk Evaluation:
Quality Evaluation:
Additional Resources:
Duration:
Additional Effort:
Impact on Deadline:
Alternative and Recommendations:
Comments:

Appendix C: Request for Proposal (RFP)

RFP:
Proposal Due Date:
Company Name:
Project Overview:
Project Goals:
Scope of Work:
Current Roadblocks and Barriers to Success:
Evaluation Metrics and Criteria:
Submission Requirements:
Project Due Date:
Budget Amount:
Contact:
Email:
Phone number:

Appendix D: Work Package

Initiation

WBS: 1.1.1.2
Work Package: Create an Empathy Map
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: This work package analyzed potential risks, evaluated their impact and likelihood, and proposed ways for managing and mitigating them.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Empathy Map and As-is Scenario FigJam
WBS: 1.1.1.3
Work Package: Create an AS-IS Scenario
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: This work package analyzed potential risks, evaluated their impact and likelihood, and proposed ways for managing and mitigating them.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Empathy Map and As-is Scenario FigJam
WBS: 1.1.1.4
Work Package: Project Adviser Request Form Completion
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Project Adviser Request Form Completion is the process of filling out and submitting a form to request an adviser for a specific project. This form is commonly used in academic or organizational settings where projects need oversight and direction from qualified advisers.
Completion State: When See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Charter.docx
WBS: 1.1.1.1
Work Package: Problem Rundown
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: This work package involves the development of a detailed company profile that will serve as a key communication tool for GJJSP. It focuses on the Company profile for its branding, background, and mission.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Problem Rundown FigJam
WBS: 1.1.3
Work Package: First Meeting with Adviser
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: The first meeting with an adviser is an important step toward establishing a fruitful working relationship and obtaining guidance and support for a project or professional growth.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 10,000
Reference Docs:
WBS: 1.1.2
Work Package: Creation of Proposal Paper
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A proposal paper outlines a problem or opportunity, proposes a solution or project, and includes information such as objectives, methodology, budget, evaluation plan, timetable, and risk management.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Proposal Paper.docx
WBS: 1.1.4
Work Package: Connection to Client
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Connecting with a client entails developing a healthy and productive connection based on clear communication, understanding their needs and expectations, and providing value through products or services.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 10,000
Reference Docs:
WBS: 1.2.1
Work Package: UI Design System (Components)
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A UI design system, also known as a component library or design system, is a set of reusable components, patterns, rules, and materials that define the visual and interaction parts of a user interface.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Wireframe Figma
WBS: 1.2.2
Work Package: Preliminary Study
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A preliminary study is a first examination or analysis carried out before beginning a more complete research project, development endeavor, or decision-making process.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 5,000
Reference Docs:
WBS: 1.3.1.2
Work Package: Daily Scrum
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: The Daily Scrum, also known as the Daily Standup or Daily Stand-up Meeting, is a brief and concentrated daily meeting that follows Agile and Scrum Methodology.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 5,000
Reference Docs: -
WBS: 1.3.1.3
Work Package: Sprint Review
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Sprint Review is a critical event in Agile and Scrum techniques that takes place at the conclusion of each sprint or iteration.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the projects and their agendas.
Budget: PHP 5,000
Reference Docs: -
WBS: 1.3.4.1
Work Package: Daily Scrum
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Daily Scrum is a short, time-boxed meeting held each day in agile project management. Team members share updates on their progress, discuss any obstacles, and outline their plans for the day.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 5,000
Reference Docs: -
WBS: 1.3.2.1
Work Package: Update Product Backlog
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Updating the Product Backlog entails reviewing and amending the list of activities, features, and enhancements that must be performed for a project.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 5,000
Reference Docs: -
WBS: 1.3.2.2
Work Package: Daily Scrum
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Daily Scrum is a short, time-boxed meeting held each day in agile project management. Team members share updates on their progress, discuss any obstacles, and outline their plans for the day.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 5,000
Reference Docs: -
WBS: 1.3.2.3
Work Package: Wireframing
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Wireframing is generated early in the design phase to build the framework and organization of the interface before proceeding to visual design and development.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: -
Reference Docs: Wireframe Figma
WBS: 1.3.2.4
Work Package: Sprint Review
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Sprint Review occurs at the end of each sprint in agile project management. The goal is to present the completed work to stakeholders, solicit input, and explore future changes.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: 5,000
Reference Docs: -
WBS: 1.3.3.1
Work Package: Daily Scrum
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Daily Scrum is a short, time-boxed meeting held each day in agile project management. Team members share updates on their progress, discuss any obstacles, and outline their plans for the day.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: 5,000
Reference Docs: -
WBS: 1.3.3.2
Work Package: Sprint Review
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Sprint Review occurs at the end of each sprint in agile project management. The goal is to present the completed work to stakeholders, solicit input, and explore future changes.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: 5,000
Reference Docs: -
WBS: 1.3.4.1
Work Package: Daily Scrum
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Daily Scrum is a short, time-boxed meeting held each day in agile project management. Team members share updates on their progress, discuss any obstacles, and outline their plans for the day.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: 5,000
Reference Docs: -
WBS: 1.3.4.3
Work Package: Frontend Development
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Frontend development is the process of designing the user interface (UI) and user experience (UX) of a website, web application, or software program.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: 5,000
Reference Docs: -
WBS: 1.4.1
Work Package: Paper
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Papers are crucial for developing knowledge in a specific topic, adding to academic discourse, and providing evidence-based insights for decision-making and future study.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: -
WBS: 1.4.2
Work Package: Wireframe
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Wireframes are generated early in the design phase to build the framework and organization of the interface before proceeding to visual design and development.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: SPD
Reference Docs: Wireframe Figma
WBS: 1.4.3
Work Package: Prototype
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A prototype is an early version of the model of a product, system, or concept created to test and validate concepts, features, and designs before full-scale production or implementation.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Wireframe Figma
WBS: 1.4.4
Work Package: Team Meeting
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A team meeting is a scheduled gathering of team members to discuss key topics, provide updates, and work on projects together. The primary goals are to align on objectives, handle any concerns, and plan for future actions.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: -

Planning

WBS: 2.1.1
Work Package: Create Use Case Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Creating a Use Case Diagram to visually represent interactions between users (actors) and a system.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.2
Work Package: Create Entity Relationship Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: An Entity Relationship Diagram (ERD) depicts the data and relationships in a system.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.3
Work Package: Create Class Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Use Case Diagram depicts the interactions of users (actors) with a system, capturing functional requirements.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.4
Work Package: Create Event Table
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: An Event Table documents and organizes the system's major events, including triggers, sources, activities, and replies.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.5
Work Package: Create Data Flow Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Data Flow Diagram (DFD) depicts the flow of data throughout a system, including how it is processed and moved between different components.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.6
Work Package: Create Activity Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: An activity diagram depicts the flow of activities and actions inside a system or process.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.7
Work Package: Create Sequence Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: An activity diagram depicts the flow of activities and actions inside a system or process.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.1.8
Work Package: Create Deployment Diagram
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Deployment Diagram depicts a system's physical architecture and how software components are spread across hardware nodes.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Project Diagrams Lucidchart
WBS: 2.5.1
Work Package: Create Initial Wireframe
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: An initial wireframe consists of drawing or outlining the fundamental layout, structure, and functionality of a digital interface, such as a website or mobile app, in a simplified and visual manner.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 25,000
Reference Docs: Wireframe Figma
WBS: 2.6.2.1
Work Package: Daily Scrum
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Daily Scrum is a short, time-boxed meeting held each day in agile project management. Team members share updates on their progress, discuss any obstacles, and outline their plans for the day.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 10,000
Reference Docs: -
WBS: 2.6.2.2
Work Package: Sprint Review
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: A Sprint Review occurs at the end of each sprint in agile project management. The goal is to present the completed work to stakeholders, solicit input, and explore future changes.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 10,000
Reference Docs: -
WBS: 2.6.2.3
Work Package: Retrospective and Impediments
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Retrospective is a meeting held at the end of each sprint to discuss what went well, what did not, and how the team can do better. They also identify and address impediments, which are roadblocks to progress, to sustaining momentum and assure project success.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP 10,000
Reference Docs: -
WBS: 2.6.2.4
Work Package: Sprint 6 Planning
Package Owner: See Solutions
Owner Organization: GJJSP
Participants: Mc Joseph Agbanlog | Project Manager, Scrum Master, and Product Designer
Christian Medallada | Product Owner, Quality Assurance Tester, and Full Stack Developer
Jerlyn Pascua | Document Specialist
Daniel Yap | Document Specialist
Description: Sprint 6 planning is determining the goals, tasks, and deliverables for the upcoming sprint. The team goes over the backlog, selects high-priority items, estimates effort, and assigns tasks to establish clear objectives and alignment throughout the sprint's duration.
Completion State: See Solutions has accomplished the document with no revisions needed.
Assumptions:
  • All team members agree to stay and work in the same group until the full completion of the project.
  • The team will work to meet the agreed deadline with all the resources available to them.
  • Key Stakeholder will give her honest and critical feedback regarding the work package.
Risks:
  • Key Stakeholder may second guess and back out of the project.
  • Group can collapse or have other agendas in continuing the project.
Risk Mitigation:
  • The team will provide consistent updates to reassure the client that progress was made in the project's development.
  • The team will communicate with each other if they are quitting and have open collaboration on the project and their agendas.
Budget: PHP [Specify]
Reference Docs: -

APPENDIX D - DOCUMENT LINK: https://asiapacificcollege-my.sharepoint.com/:b:/g/personal/jppascua_student_apc_edu_ph/Eb_7fMxrDI1FqJoitFJk1acBSZ-OtxYkS9OEdhD2x2gSWw?e=7ys1Sm

⚠️ **GitHub.com Fallback** ⚠️