This is a one-stop resource for the entire project team to view high-level direction from Product Operations & Product Strategy.

Amp up Project Charter (Phase 2)

• Create a Mid-Fidelity Mockup: Design and develop a prototype covering UI/UX elements for community interaction features.
• Target User Group: US-based job seekers breaking into tech.

Out-of-Scope:

• AI Technologies & GitHub Integration: Excluded due to resource and budget constraints, as well as a lack of development work in Phase 2.
• Cost-bearing Design and Research Activities: Excluded due to no budget.
• Job Search Functions: Excluded due to resource constraints, business viability considerations and phase-specific focus on validating USP. | V.02 (01/12/24) | | | | Assumptions | 1. The product will positively impact users' mental well-being without causing harm or unintended consequences.

2. The project can leverage existing open-source tools, libraries, and frameworks to reduce development time and costs effectively. | | | These are high-level assumptions that must be true for the project to remain viable. | | Constraints | 1. No budget for marketing, hosting, and operational expenses due to the project's open-source nature and reliance on volunteers.

2. The availability and expertise of volunteer contributors may influence project progress and development speed.

3. Compliance with data protection and privacy regulations, given the project's data collection activities.

4. Stringent security constraints related to user data, necessitating robust encryption and data protection measures.

5. Active engagement with the community required within the open-source ecosystem, demanding additional effort in communication, collaboration, and documentation.

6. Adherence to open-source licensing agreements and legal constraints to maintain project openness and compliance with licensing terms. | V.01 (01/10/24) | | All constraints will be addressed in the Product Feasibility Study deliverable | | Deliverables | A. Requirements & Feasibility Assessment:

• Product Requirements Document (Incl. POC Definition)
• Product Feasibility Study
• Product Roadmap

B. Design & Mockup:

• Mid-fidelity Mockups
• User Journey Mapping
• User Testing Protocols

C. User Insights & Personas:

• User Research Findings
• User Testing Insights
• Persona Development

D. Strategic Considerations:

• Business Model Canvas
• OKRs - Risk Assessment (removed due to lack of time) | V.02 (1/12/24) | | | | Project Team | ‣ | N/A | | | | Steering Committee* | M2K: @Anonymous @Anonymous @Anonymous Support: @Anonymous | N/A | | *Decision-making body for high-level baselines | | Budget | As the project operates without a budget, all incurred costs must be covered exclusively by the product's own revenue-generating components. | N/A | | | | Communication Plan | ‣ | N/A | | | | Proof of Concept (PoC) | POC (WIP) | V.02 (1/12/24) | WIP | | | Product Directives | Product Directives | V.03 (1/12/24) | | | | Business Goals & Strategic OKRs | ‣ | N/A | | | | Product Vision | (WIP)Amp up’s POC will be a browser extension that delivers emotional wellbeing value to **UX career transitioners with 0-2 years of experience in their target careers during the job search process. Our tool will provide interactions that reinforce feelings of positive emotions, and allows users to hide interactions that tend to create negative self comparisons and/or emotional wellbeing.

**Needs updating based on product directives. Want to walk apprentices through this on Monday. | | WIP | - Need to establish consistent naming convention on: emotional wellbeing/mental wellbeing/mental wellness (by PO team on January 14, 2024) | | Project Roadmap | Project Roadmap | V.03 (1/12/24) | | |

Product Directives

POC (WIP)

Project Roadmap