# Program Consolidation

## ECOLINK
https://gitlab.com/izakS/carbonfootprint_egalitarian
### Project Overview

Currently, only **39%** of the waste collected in the Federal District is recycled, a rate far below its potential. To address this, the **Ecolink** project aims to raise awareness about proper waste separation and hygiene through **educational videos** on the **Ecolink app** and **Instagram**.

The initiative involves collaboration with **waste pickers**, who will share practical knowledge, and the implementation of a **gamified program** that rewards recyclable donations with **university credits**. The project will also introduce **EcoPoints**, smart collection containers ensuring efficient waste collection and sorting—driving **environmental benefits** and **fostering social engagement**.

**Key Benefits:**
- Raises awareness through **educational content** co-created by **waste pickers** and **University of Brasília (UnB) students**.
- Improves the **quality of collected recyclables**, reducing contamination and increasing value.
- Generates increased **income for cooperatives**, strengthening the **circular economy**.
- Provides an **accessible platform** for efficient waste collection participation.
- Encourages **UnB students** to engage in sustainability through **credit incentives**.

**Goals:**
- Educate residents on **proper waste separation and hygiene**.
- Within one year, collect **50,000 units of recyclables** (bottles & metal cans) through EcoPoints.
- Maintain a **qualification rate of over 50%** for recyclable materials.

---

## Scope and Non-Scope

### **Project Scope**
- **App Development (Aalborg University)**
- Locate **EcoPoints** (Delivery Points)
- Integration with **SIGAA System**
- Admin area for **cooperative employees and users**
- Software for **content registration & storage by waste pickers**
- Material **allocation system** (bottles & cans)

- **Content Creation (UnB)**
- Create & manage **Instagram page**
- Organize **events** in cooperatives
- Record & publish **educational content** with waste pickers
- Develop a **content management process**

- **Container Discovery (UnB)**
- Research **smart waste collection companies**
- Document **pros & cons of machines**
- Develop proprietary **hardware for EcoPoints**
- Map **waste recycling chain & container processes**

### **Non-Scope**
- Hiring external influencers for promotions
- Fixing **bugs in the content management application**
- Construction of **hardware solutions for containers**
- **Security management** of the containers

---

## Deliverables

### **App Development (Aalborg University)**

| Deliverable | Description | Acceptance Criteria |
|-------------|-------------|----------------------|
| **Content Section** | Front-end section for educational & explanatory recycling content. | Content is well-organized, searchable, and user-friendly. |
| **CMS Tools** | Content Management System (CMS) for students & waste pickers. | CMS supports video, image, and text uploads with real-time updates. |
| **Role-Based System** | Differentiates users, waste pickers, students & admins. | Cooperatives have full CRUD permissions; students can track contributions. |
| **Student Area in App** | Dedicated section for student participation. | Students can register, log in, and track contribution frequency. |
| **Locate Delivery Points** | Feature to find **EcoPoints** within the app. | Map accurately displays all EcoPoints. |

### **Content Creation (UnB)**

| Deliverable | Description | Acceptance Criteria |
|-------------|-------------|----------------------|
| **Instagram Page** | Official project Instagram page. | Bio, profile picture, and app link included. |
| **Post Content to Raise Awareness** | Regular educational posts. | At least 1 post per week with engaging multimedia. |
| **Manage Instagram Marketing** | Ad campaigns & engagement tracking. | Minimum 2 campaigns per month. |
| **Content Creation Process Map** | Process from **ideation to publication**. | Includes **stages such as ideation, approval, and publishing**. |
| **Content Recording Guide** | Guide for recording & editing content. | Includes **templates, step-by-step instructions, and key messages**. |
| **Content Calendar** | Organized scheduling of posts. | Contains **publication dates, content types, and team responsibilities**. |

### **Container Discovery (UnB)**

| Deliverable | Description | Acceptance Criteria |
|-------------|-------------|----------------------|
| **Research Companies Using Smart Waste Collection Machines** | Identify companies using intelligent recycling technology. | Minimum **5 companies** identified. |
| **Document Pros & Cons of Machines** | Analyze strengths & weaknesses of each system. | Covers **collection, sorting, and recycling processes**. |
| **Research Hardware Development for EcoPoints** | Investigate the feasibility of proprietary hardware. | Minimum **3 viable solutions** identified. |
| **Map Recycling Chain** | Document key stages of the recycling process. | Covers **waste generation to final processing**. |
| **Map Container Workflow** | Analyze how containers are used from filling to collection. | Includes **user interaction & logistics**. |

---

## Consolidated Schedule

# Sprint Schedule and Weekly Checkpoint Meetings

---

## 🇩🇰 Dinamarca

### Sprint Schedule

| Sprint | Goals | Start Date | End Date |
|----------|-----------------------------------------------------------------------|----------------|----------------|
| SPRINT 0 | **Stakeholder Identification**: Identify key stakeholders and define their roles. <br> **Initial Requirements Gathering**: Conduct interviews and workshops to gather high-level requirements. | February 2, 2025 | February 15, 2025 |
| SPRINT 1 | **Requirement Elicitation**: Use techniques like brainstorming, surveys, and user stories to gather detailed requirements. <br> **Prioritization**: Prioritize requirements based on stakeholder input and project goals. | February 16, 2025 | March 1, 2025 |
| SPRINT 2 | **Requirement Validation**: Validate requirements with stakeholders through reviews and prototypes (if needed). <br> **Conflict Resolution**: Resolve any conflicting requirements and ensure alignment. | March 2, 2025 | March 15, 2025 |
| SPRINT 3 | **Requirement Documentation**: Finalize the requirements document, including functional and non-functional requirements. <br> **Sign-Off**: Obtain stakeholder sign-off on the finalized requirements. | March 16, 2025 | March 29, 2025 |
| SPRINT 4 | **Alignment with Brasil**: Review Brasil's progress and align on shared goals and deliverables. | March 30, 2025 | April 12, 2025 |
| SPRINT 5 | **Feature Development**: Begin implementing core features based on finalized requirements. | April 13, 2025 | April 26, 2025 |
| SPRINT 6 | **Integration**: Integrate with Brasil's backend (if applicable) and test functionality. | April 27, 2025 | May 10, 2025 |
| SPRINT 7 | **Testing & Bug Fixing**: Conduct thorough testing and fix any bugs or issues. | May 11, 2025 | May 24, 2025 |
| SPRINT 8 | **Finalization**: Prepare for launch, finalize documentation, and conduct a final review. | May 25, 2025 | June 7, 2025 |

---

## 🇧🇷 Brasil

### Sprint Schedule

| Sprint | Goals | Start Date | End Date |
|----------|-----------------------------------------------------------------------|----------------|----------------|
| SPRINT 0 | **Kickoff & Planning**: Define squads, assign roles, and set high-level goals. | March 24, 2025 | April 6, 2025 |
| SPRINT 1 | **App Squad**: Review the provided design and plan frontend development. <br> **Content Squad**: Research content models and define objectives. <br> **Viability Squad**: Outline the structure of the viability document. | April 7, 2025 | April 20, 2025 |
| SPRINT 2 | **App Squad**: Begin frontend development based on the provided design. <br> **Content Squad**: Create a content creation framework and draft templates. <br> **Viability Squad**: Conduct market research and gather data for the viability document. | April 21, 2025 | May 4, 2025 |
| SPRINT 3 | **App Squad**: Integrate frontend with the existing backend and test basic functionality. <br> **Content Squad**: Test the content model with sample content and refine templates. <br> **Viability Squad**: Analyze competitors and document findings. | May 5, 2025 | May 18, 2025 |
| SPRINT 4 | **App Squad**: Implement key features and conduct internal testing. <br> **Content Squad**: Finalize the content model and create a user guide. <br> **Viability Squad**: Draft the viability document with initial conclusions. | May 19, 2025 | June 1, 2025 |
| SPRINT 5 | **App Squad**: Fix bugs, optimize performance, and prepare for beta testing. <br> **Content Squad**: Train the team on the content model and gather feedback. <br> **Viability Squad**: Validate findings with stakeholders and refine the document. | June 2, 2025 | June 15, 2025 |
| SPRINT 6 | **App Squad**: Conduct beta testing, gather user feedback, and make improvements. <br> **Content Squad**: Roll out the content model and monitor its adoption. <br> **Viability Squad**: Finalize the viability document and prepare for presentation. | June 16, 2025 | June 29, 2025 |
| SPRINT 7 | **App Squad**: Finalize the app for launch and prepare documentation. <br> **Content Squad**: Evaluate the content model's success and plan for scaling. <br> **Viability Squad**: Present the viability document to stakeholders. | June 30, 2025 | July 5, 2025 |

---

## Weekly Checkpoint Meetings

### Meeting Time
- **BRT (Brasil)**: 10:00 AM
- **CET/CEST (Dinamarca)**: 2:00 PM

### Schedule

| Week | Date | Time (BRT) | Time (CET/CEST) | Notes |
|------------|----------------|------------|-----------------|---------------------------|
| Week 1 | March 24, 2025 | 10:00 AM | 2:00 PM | Kickoff after Brasil starts |
| Week 2 | March 31, 2025 | 10:00 AM | 2:00 PM | |
| Week 3 | April 7, 2025 | 10:00 AM | 2:00 PM | |
| Week 4 | April 14, 2025 | 10:00 AM | 2:00 PM | |
| Week 5 | April 21, 2025 | 10:00 AM | 2:00 PM | |
| Week 6 | April 28, 2025 | 10:00 AM | 2:00 PM | |
| Week 7 | May 5, 2025 | 10:00 AM | 2:00 PM | |
| Week 8 | May 12, 2025 | 10:00 AM | 2:00 PM | |
| Week 9 | May 19, 2025 | 10:00 AM | 2:00 PM | |
| Week 10 | May 26, 2025 | 10:00 AM | 2:00 PM | |
| Week 11 | June 2, 2025 | 10:00 AM | 2:00 PM | |
| Week 12 | June 9, 2025 | 10:00 AM | 2:00 PM | |
| Week 13 | June 16, 2025 | 10:00 AM | 2:00 PM | |
| Week 14 | June 23, 2025 | 10:00 AM | 2:00 PM | |
| Week 15 | June 30, 2025 | 10:00 AM | 2:00 PM | Final meeting |

---

## Risks and Mitigations

| Risk | Description | Mitigation |
|------|------------|------------|
| **Mixed materials added without separation** | Users may dispose of materials incorrectly, contaminating recyclables. | **Educational campaigns, clear instructions, and EcoPoint monitoring.** |
| **Security vulnerabilities in the container** | Containers may be subject to theft or vandalism. | **Install security cameras, access control, and conduct regular inspections.** |
| **Unattractive content** | Content may fail to engage users. | **Create dynamic multimedia content with input from waste pickers.** |
| **Different academic calendars** | Misaligned semesters may affect student participation. | **Coordinate university schedules and introduce flexible credit systems.** |

---

### **Final Notes**
- **Use the Deliverable Groups section of the PM Canvas** to define key components throughout the project.
- **Use the Team section of the PM Canvas** to outline roles and responsibilities clearly.

---

This structured markdown format makes your document more readable and navigable on a wiki platform. Let me know if you need any modifications! 🚀

## Project Organization

| **Role** | **Responsibilities** |
| ------------- | ----------------------------------------- |
| Backend | Develop and maintain backend systems |
| Frontend | Design and develop the frontend interface |
| Database | Structure and manage the database |
| Product Owner | Validate deliverables, schedule meetings |

## Technologies

| **Backend** | **Frontend** | **Database** | **Documentation** | **Communication** |
|:-----------:|:--------------:|:------------:|:-----------------:|-------------------------|
| NodeJS | React | MongoDB | Markdown Wiki | WhatsApp, Teams, Discord|