Sprint 1
This page summarizes the key information for the current Sprint, including team capacity, sprint goals, forecasted work, and the detailed sprint backlog. Use this as a reference to track progress and priorities throughout the Sprint.
| Estimated Team Capacity per Sprint: | 29 Story Points |
| Sprint Goal: | Rank 1, Rank 2 and Rank 3 User Stories (total of 21 Story Points) |
| Sprint Forecast (extras, not committed for delivery): | Rank 4 User Story (8 Story Points) |
| Rank | Goal | User Story | Expected Impact | Related Requirements | Estimate | Sprint |
|---|---|---|---|---|---|---|
| 1 | Goal | As a user, I want to receive quantitative insights from the historical database on ticket quantities by company, product, status, and category, so that I can make better strategic decisions without relying on complex dashboards. | Improved decision-making for support management through actionable insights, reducing reliance on complex dashboards and increasing strategic efficiency. | FR4 | 8 | 1 |
| 2 | Goal | As an administrator, I want personal data to be processed and stored only as long as necessary, and completely deleted when no longer required or upon request, so that the system complies with LGPD and user privacy is guaranteed. | Ensures compliance with LGPD by anonymizing data, reducing legal risks and building trust with stakeholders. | FR2 | 7 | 1 |
| 3 | Goal | As an administrator, I want to delete user data upon a deletion request, ensuring protection of personal information and compliance with LGPD. | Protect personal data, ensure LGPD compliance, and maintain trust while allowing anonymized data analysis. | FR03 | 6 | 1 |
| 4 | Forecast | As a user, I want to search tickets by keywords so that I can quickly locate old tickets, identify patterns, track ticket history, and resolve issues more efficiently. | Faster access to historical tickets, reducing time spent searching for solutions and increasing user productivity. | FR1 | 8 | 1 |
Define the criteria that must be met to consider a task ready to be worked on.
- ✅ Title and description of the history are comprehensible.
- ✅ The expected impact is described and validated with the PO.
- ✅ The user story is short enough to fit in a sprint.
- ✅ Effort estimation completed.
- ✅ Title and description of the tasks are comprehensible.
- ✅ Design and mockups are available - (Front-end).
- ✅ Detailed business rules (text or diagram).
- ✅ Data model available (Back-end).
- ✅ Test strategy defined (Back-end).
- ✅ Effort estimation completed.
