Sprint 2
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: | 28 Story Points |
| Sprint Goal: | Rank 1, Rank 2 and Rank 3 User Stories (total of 20 Story Points) |
| Sprint Forecast (extras, not committed for delivery): | Rank 4 User Story (8 Story Points) |
| Rank | Goal / Forecast | 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 department, SLAPlan and priorities so that I can make better strategic decisions without relying on dashboards. | Users will gain fast access to actionable insights, improving decision-making efficiency and reducing dependence on manual dashboard analysis. | FR4 | 6 | 2 |
| 2 | Goal | As a user, I want the system to use artificial intelligence to analyze the history of tickets for each product, so that patterns, trends, and peaks in complaint or incident volumes are automatically identified. | Early detection of trends and anomalies allows proactive management, reduces response times, and improves resource allocation. | FR6 | 9 | 2 |
| 3 | Goal | As a user, I want to filter the dashboards by periods and flags such as company, product, period and categories, so that I can quickly analyze specific scenarios, identify patterns, and make better data-driven decisions. | Filtering capability enhances analytical precision, accelerates scenario analysis, and enables targeted strategic actions. | FR4 | 5 | 2 |
| 4 | Forecast | As a user, I want to apply predefined filters in the ticket search, such company, product, status, priority, category, and subcategory, so that I can reduce search time, focus only on the most relevant cases, and avoid manually configuring filters every time I perform an analysis. | Predefined filters reduce time spent on searches, increase productivity, and ensure consistent analysis across users. | FR4 | 8 | 2 |
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).
- ✅ Effort estimation completed.
Link: Clique aqui
