Project Roadmap
Overview
This roadmap aligns with Ecolink’s 14‑day cadence, culminating in final delivery on June 17, 2025. Each phase focuses on specific goals and deliverables to incrementally build, test, and deliver the platform.
| Phase | Timeline | Goals | Deliverables |
|---|---|---|---|
| Phase 0 | March 24, 2025 – April 6, 2025 | - Define frontend & backend responsibilities - Set up communication tools - Map existing infrastructure - Identify technical dependencies |
- Team alignment document - Initial technical mapping |
| Phase 1 | April 7, 2025 – April 20, 2025 | - Gather requirements for EcoPoints & CMS - Analyze existing APIs & dependencies - Build backlog |
- Requirements document - Technical dependencies report |
| Phase 2 | April 21, 2025 – May 4, 2025 | - Finalize detailed requirements & acceptance criteria - Prioritize backlog - Prototype API & static map |
- Prioritized backlog - Initial EcoPoints prototype |
| Phase 3 | May 5, 2025 – May 18, 2025 | - Complete EcoPoints module (filters, location, tests) - Start CMS with CRUD & user roles |
- Functional EcoPoints module - CMS prototype (CRUD & roles) |
| Phase 4 | May 19, 2025 – June 1, 2025 | - Finalize CMS features (editing, validation) - General testing & polish - Draft technical & user documentation |
- Fully functional CMS - Initial documentation |
| Phase 5 | June 2, 2025 – June 17, 2025 | - Final testing & bug fixes - Stakeholder validation - UX adjustments & official delivery |
- Final validated system - Final documentation - Delivery |
Phase Descriptions
🛠️ Phase 0 — Initialization & Alignment
Timeline: March 24 → April 6, 2025
Purpose: Align team responsibilities and prepare the technical foundation.
Key Activities:
- Define frontend and backend roles
- Set up communication tools
- Review and map existing infrastructure
- Identify initial technical dependencies
📋 Phase 1 — Requirements Gathering & Backlog Building
Timeline: April 7 → April 20, 2025
Purpose: Understand the product’s functional needs and shape the project backlog.
Key Activities:
- Interview stakeholders (students, collectors, UnB teams)
- Define functional requirements for EcoPoints and CMS
- Analyze API integrations and external systems
- Structure and prioritize user stories in the backlog
🧪 Phase 2 — Specification & Prototyping
Timeline: April 21 → May 4, 2025
Purpose: Refine top-priority items and validate with early prototypes.
Key Activities:
- Finalize detailed requirements and acceptance criteria
- Prioritize stories and dependencies
- Create API stubs and static map for EcoPoint discovery
- Build clickable mockups or wireframes for main flows
⚙️ Phase 3 — Core Module Development
Timeline: May 5 → May 18, 2025
Purpose: Implement the EcoPoints module and CMS foundations.
Key Activities:
- Implement EcoPoints filters, geolocation, and tests
- Scaffold CMS with CRUD functionality and user roles
- Begin writing unit and integration tests
- Present working features to stakeholders for feedback
🧼 Phase 4 — Feature Completion & Polishing
Timeline: May 19 → June 1, 2025
Purpose: Finalize CMS and enhance overall usability and documentation.
Key Activities:
- Implement advanced CMS features (validation, media upload)
- Perform end-to-end testing across modules
- Polish UI based on testing and feedback
- Draft user and technical documentation
🚀 Phase 5 — Final Testing, Validation & Delivery
Timeline: June 2 → June 17, 2025
Purpose: Validate the system with users and stakeholders and deliver the final product.
Key Activities:
- Execute QA (performance, security, accessibility)
- Conduct final stakeholder reviews and validations
- Apply final UX/UI refinements
- Finalize documentation and deliver the project
Revision History
| Date | Version | Changes | Authors |
|---|---|---|---|
| 2025‑04‑06 | 0.2 | Updated document with Ecolink scope/timeline | Mateus Vieira |
| 2024‑03‑28 | 0.1 | Document creation | Cainã Freitas, Lucas Antunes |