🚀 Project Plan

---

General Project Information

Information	Detail
Project Name	Digital Talent Platform
Supervisor	Rafael Ricardo Jacomossi
Product Owner	Gabriela Rodrigues Matias
Scrum Master	Gabriela Rodrigues Matias
Development Team	Gabriela Rodrigues Matias
Start Date	02/03/2025
Expected End Date	11/15/2025

Start Date: 02/03/2025
Expected End Date: 11/15/2025

---

Agreements Between Student and Partner

To ensure efficient collaboration among those involved in the development of the Digital Talent Bank Platform - Next Generation of Lawyers, the following agreements have been established:

• Meeting Frequency:

  • Biweekly Alignments: Internal checkpoints to track project progress and validate functionalities.

• Meeting Location:

  • Meetings will mostly be held remotely (Google Meet, Microsoft Teams) to ensure flexibility.
  • When necessary, in-person meetings may occur at Inteli or during strategic legal events.

• Communication with Partner’s Internal Areas:

  • Communication with partner law firms will be mediated by a project representative, facilitating the exchange of information and adjustments in demands.

• Tool Access Level:
  The team will have access to the following tools:

  • Hosting Platform (e.g., AWS, GCP, or another to be defined)
  • Code Repository (GitHub)
  • Project Management (e.g., Trello, Jira, ClickUp – to be defined)
  • Design and Prototyping (Figma for UX/UI)
  • Testing Environment for platform validation

• Other Agreements:

  • Continuous Validation: Stakeholders (law firms and students) will be involved in usability tests to ensure the platform meets market needs.
  • Confidentiality: User data and information provided by law firms will be treated confidentially, in compliance with security and privacy regulations.
  • Delivery Schedule: The project will follow a predefined schedule, ensuring that each phase is completed with proper validation before moving on to the next step.

---

Project Objectives

General Objective:
Develop a digital platform that connects young law students from low-income backgrounds with law firms, facilitating access to training, mentoring, and job opportunities while promoting inclusion and diversity in the legal sector.

Specific Objectives:

• Build an accessible and intuitive interface for students to register their profiles and skills.
• Create tools for law firms to search for talent using filters and personalized criteria.
• Establish a sustainable and ethical technology model that meets stakeholder needs.
• Continuously validate the project with internal and external stakeholders to align with market demands.

---

Project Scope - Product Backlog

Phase	Activities	Deadline
Phase 1: Planning	Proposal creation, Implementation Plan, Validations	Feb - Mar
Phase 2: Research & Design	Interviews, Personas, User Journeys, Visual Identity	Apr
Phase 3: Prototyping	Requirements, Architecture Planning, MVP Definition, Prototype	May
Phase 4: Validation	Usability Tests, Adjustments, Infrastructure Prioritization	Jun
Phase 5: Implementation	MVP Development, Training, Final Report, Presentation	Jul - Nov

---

Roadmap and Project Timeline

Macro and Micro Deliverables

1. Initial Planning and Research (Feb - Mar)

   • Project Proposal Creation: Structuring vision, mission, and justification.
   • Implementation Plan: Defining phases, timeline, resources, and deliverables.
   • KPIs and Metrics: Establishing clear indicators for monitoring success.
   • Proposal Validation: Presenting and adjusting the plan based on feedback from Inteli and NEXT.
   • Market Understanding: Mapping trends, competitors, and benchmarks.

2. Product Research and Design (Apr - May)

   • Stakeholder Interviews: Identifying pain points and needs of HRs and students.
   • Persona Creation: Developing representative profiles of the target audience.
   • User Journeys Mapping: Identifying ideal interactions on the platform.
   • User Stories/Epics: Documenting functionalities based on user journeys.
   • Visual Identity Structuring: Defining platform branding and design elements.

3. Requirements Definition and Prototyping (Jun - Aug)

   • Functional and Non-Functional Requirements: Formalizing technical specifications.
   • Architecture Planning: Structuring back-end, front-end, and database.
   • MVP - Definition: Identifying essential functionalities.
   • Start - Prototype: Creating navigable prototypes with basic functionalities.

4. Development and Validation (Sep)

   • Usability Testing: Validating prototypes with students and law firms.
   • Iteration and Prototype Adjustments: Refining based on received feedback.
   • Service Definition: Planning APIs and integrations (e.g., authentication, advanced search).
   • Infrastructure Prioritization and Budgeting: Ensuring necessary technical resources.

5. Implementation and Finalization (Oct - Nov)

   • MVP Development: Building and testing the platform’s initial version.
   • Training and Adoption Plan: Creating support materials for users.
   • Final Public Report: Documenting results and key learnings.
   • Final Presentation: Showcasing the project and its impact.

Monthly Distribution of Micro-deliverables

Month	Micro Deliverables
February	Project Proposal, Implementation Plan, KPIs, Validation (Inteli and NEXT)
March	Market Research, Resource Planning
April	HR & Student Interviews, Persona Creation, User Journeys, User Stories, Visual Identity
May	Functional/Non-functional Requirements, Architecture Planning, MVP Definition, Prototype Creation, Usability Tests, Prototype Adjustments
June	Iterations, Service and API Planning, Infrastructure Prioritization
July	Data Modeling and Database Creation, Backend Development, General Functionalities for Roles (students and companies)
August	Page Development, Component Implementation, Student Features Development
September	Company Features Development
October	Architecture and Prototype Refinement, Training Planning
November	MVP Development, Final Tests
December	Final Report, Final Presentation

---

Risk Management

a. Technical Risks

Risk/Challenge	Impact	Probability	Mitigation Plan
Hosting platform infrastructure failure	High	Medium	Use scalable cloud services (e.g., AWS, GCP, Azure) and implement redundancy.
Critical bugs at platform launch	High	High	Establish a QA team for continuous testing and run automated tests before each deployment.
User data leakage	Very High	Low	Implement encryption, multi-factor authentication (MFA), and regular security audits.
Slow platform performance with user growth	High	Medium	Optimize the database, use caching, and implement load balancing for scalability.

b. Operational Risks

Risk/Challenge	Impact	Probability	Mitigation Plan
Delay in requirements gathering with stakeholders	Medium	High	Schedule interviews in advance and prioritize asynchronous meetings when necessary.
Lack of HR engagement with the talent bank	Medium	Medium	Promote co-creation by encouraging platform use from the development phase.
Difficulty in system maintenance and updates	High	Medium	Create detailed documentation and structure a continuous support plan.

c. Strategic Risks

Risk/Challenge	Impact	Probability	Mitigation Plan
Competition from established platforms	High	Medium	Develop competitive differentiators, focusing on diversity, inclusion, and UX/UI.
Difficulty in scaling the solution	Medium	Medium	Plan architecture to be modular and scalable from the start.
Lack of ongoing engagement from team and stakeholders	High	Medium	Maintain constant communication, hold periodic meetings, and encourage active participation.

---

Conclusion and Action Plan

• Technical: Implement rigorous testing and ensure scalable infrastructure from the start.
• Operational: Create incentives for law firms and students to adopt the platform.
• Financial: Establish a controlled budget and seek additional funding.
• Strategic: Monitor competition and regulatory changes while maintaining stakeholder engagement.

---