The project aims to develop a project performance management and monitoring platform focused on providing visibility and dynamic insights into metrics and indicators. The platform will be integrated with Taiga and JIra, and will allow the visualization of data such as the number of cards created and completed, average execution time, distribution by employee, among other relevant indicators. With different access levels (Operator, Manager and Administrator), the system will ensure that each profile only views information relevant to their role. The solution aims to improve efficiency, transparency and data-driven decision-making in project management.
This document presents the main components and organization of the Track project repository:
- 🗂️ Project Repositories
- 📑 Documentation
- 👥 Contributors
- 💡 Solution
- 📋 Requirements
- 🧵 Product Backlog
- 🏃 Sprints
- 🛠️ Technologies
- 📝 Product Documentation
- 📖 User Manual
- 🧩 Design Patterns
- 📚 DevOps - Documentation Pattern
- 📌 DevOps - Requirements Tracking
- 🔁 DevOps - Continuous Integration (CI)
- 🚢 DevOps - Deploy
- 🗄️ DevOps - Database
- 🧪 DevOps - Unit Test
- 🧪 DevOps - Integration Testing
- 🎨 Wireframes
| FUNCTION | NAME | SOCIAL MEDIA | IDENTIFICATION |
|---|---|---|---|
| Product Owner | Ana Raquel |   |
 |
| Scrum Master | Lucas Henrique | |
 |
| Developer | Ali Mohamed | |
 |
| Developer | Alita Amancio | |
 |
| Developer | André Bernardes | |
 |
| Developer | Eduardo Farias | |
 |
| Developer | Willian Antoniazzi | |
 |
The solution was tailor-made for Youtan, a company specialized in the development of custom software and applications. Youtan employs agile methodologies and modern technologies to deliver digital solutions for Web, Desktop, and Mobile platforms. Currently, Youtan aims to enhance its project management using various tools. However, it faces challenges in visualizing key workflow indicators, which makes it difficult to monitor progress and make strategic decisions. The lack of a centralized dashboard displaying metrics such as average completion time, task volume over specific periods, and task distribution among team members reduces efficiency and transparency in project management. Another critical issue is the limitation of Taiga in offering differentiated access levels, which hinders the ability to present personalized information to operators, managers, and administrators.
TRACK is designed as a platform integrated with the databases of both Taiga and Jira, developed to consolidate and present key indicators in a clear and accessible way, tailored to different user profiles:
- Operator: can view metrics related to tasks under their responsibility.
- Manager: has access to team metrics, including tasks assigned to their team members.
- Administrator: can access all organizational indicators.
With interactive and visually intuitive dashboards, TRACK aims to streamline project monitoring, enabling data-driven management that is more efficient and transparent across all organizational levels.
| ID | Functional Requirement | Description |
|---|---|---|
| RF01 | Cards by tag | The system must display the number of cards per tag registered in the kanban. This information must be presented visually, in a vertical bar graph. |
| RF02 | Cards per employee | The system should display the number of cards assigned to each employee. This information should be presented visually, in a horizontal bar chart, making it easier to compare workload between team members. |
| RF03 | Cards by status (Kanban columns) | The system should display the number of cards by status, based on the Kanban board columns (In Progress, In Review, Completed, etc.). This information should be presented visually, in a donut chart, providing an overview of the distribution of tasks between the different stages of the workflow. |
| RF04 | Cards created by period | The system must display the number of cards created in a given period selectable by the user. This information must be presented in a highlighted numeric box format, clearly showing the total number of new cards created in the specified period. |
| RF05 | Cards completed by period | The system must display the number of cards completed in a given user-selectable period. This information must be presented in a highlighted numeric box format, clearly showing the total number of cards completed in the specified period. |
| RF06 | Average card execution time | The system should display the average time it takes for cards to be completed. This information should be presented in a table format, containing two columns: one with the name of the card and another with the time it took to complete, allowing a detailed analysis of the efficiency in executing the tasks. |
| RF07 | Reworks | The system should display the number of cards that have been reworked (cards that have returned from the Completed column to In Progress). This information should be presented in a table format, containing two columns: one with the card name and another with the number of times the card has been returned for rework, allowing for the identification of difficulty patterns in specific tasks. |
| RF08 | Access control by levels | The system must manage the display of indicators and metrics at different access levels (administrator, manager and operator), allowing customization of the display of information according to the profile of the logged-in user and their responsibilities within the team. |
| RF09 | Integration with other systems | The system must create an API for integration with other systems, such as Trello and Jira, allowing the import and export of data between platforms to centralize metrics from different task management tools. |
| ID | Non-Functional Requirements | Description |
|---|---|---|
| RNF01 | API Documentation | The API must have clear and detailed documentation, containing three main components: process documentation (detailing flows and interactions), product documentation (detailing endpoints, parameters, and responses), and DevOps documentation (detailing configuration, deployment, and maintenance). |
| RNF02 | Responsiveness | The system must be responsive and accessible on different devices (Desktop and Mobile), automatically adapting to the screen size of the device used, ensuring a consistent user experience across all platforms. |
| RNF03 | User Manual | The system must have a manual to guide users on how to use the system, including step-by-step tutorials for key features, usage tips and common troubleshooting. |
| RNF04 | Database Modeling | The system must create an efficient database model (DW - Data Warehouse) to store all project information, allowing quick queries and complex analysis of the data collected from the kanban. |
| Pacote | Requisitos cobertos |
|---|---|
| Dashboard | RF01, RF02, RF03 |
| Tempo | RF04, RF05, RF06, RF07 |
| Perfis | RF08 |
| Integrações | RF09 |
| Docs & UX | RNF01, RNF02, RNF03 |
| DW | RNF04 |
| Rank | Pacotes de Requisitos | User Story | Perfil | Prioridade | Sprint | Status |
|---|---|---|---|---|---|---|
| 1 | Dashboard, Perfis, Docs & UX | Como administrador, quero visualizar todos os projetos e seus respectivos indicadores e métricas, para acompanhar o desempenho de cada um. | Admin | 1 | 1 | ✅ Done |
| 2 | Dashboard, Docs & UX, DW | Como usuário, quero visualizar dashboards com as métricas dos cards (por etiqueta, colaborador e status), para acompanhar os resultados. | Usuário | 2 | 1 | ✅ Done |
| 3 | Dashboard, Perfis, Docs & UX | Como administrador, quero fazer login com minhas credenciais para acessar todos os indicadores da equipe e dos projetos. | Admin | 4 | 2 | ✅ Done |
| 4 | Dashboard, Perfis, Docs & UX | Como operador, quero fazer login com minhas credenciais para acessar apenas meus indicadores de desempenho. | Operador | 2 | 2 | ✅ Done |
| 5 | Dashboard, Perfis, Docs & UX | Como gerente, quero fazer login com minhas credenciais para acessar meus indicadores e os da equipe. | Gerente | 3 | 2 | ✅ Done |
| 6 | Tempo, Docs & UX, DW | Como usuário, quero visualizar dashboards com as métricas dos cards (criados por período, finalizados por período, tempo médio e retrabalho). | Usuário | 1 | 2 | ✅ Done |
| 7 | Dashboard, Tempo, Perfis, Docs & UX, DW | Como usuário, quero filtrar as métricas e indicadores nos dashboards para obter apenas informações relevantes para minha análise. | Usuário | 3 | 3 | ✅ Done |
| 8 | Integrações, Docs & UX, DW | Como usuário, quero que o sistema integre com outras plataformas (como Trello e Jira) para puxar métricas dos projetos. | Usuário | 1 | 3 | ✅ Done |
| SPRINTS | PERIODS | KEYWORD | DESCRIPTION |
|---|---|---|---|
| Kick-off | 27/02/2025 | - | Initial alignment of the team, presentation of the project theme (Track), and definition of roles and responsibilities. |
| Sprint 1 | 10/03/2025 to 30/03/2025 | initials dashboards and project screen | Deliver the first version of the project screen and initial dashboards with card metrics by tag, collaborator and status, enabling an overall view of projects and performance. |
| Sprint 2 | 07/04/2025 to 27/04/2025 | access management and dashboards | Implement a secure login for all roles (administrator, manager and operator), expand the panels with new indicators (cards created and completed by period, average time and rework) and ensure adequate access control to the views. |
| Sprint 3 | 05/05/2025 to 25/05/2025 | advanced filters and export CSV | Advanced filtering integration for dashboards, external platform integration (e.g. Jira), and export of filtered metrics in CSV format to support decision making. |
| Feira de Soluções | 17/06/2025 | final presentation | Presentation of the final version of the Track platform, highlighting main features such as dashboards, filters, access control, data export and integrations, aligned with users' needs. |
