-
Notifications
You must be signed in to change notification settings - Fork 0
Sprint 3
Jhony Santos edited this page Nov 4, 2025
·
2 revisions
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: | 17 Story Points |
| Sprint Goal: | Rank 9 and Rank 10 User Stories (total of 12 Story Points) |
| Sprint Forecast (extras, not committed for delivery): | Rank 11 (total of 5 points) |
| Rank | Goal / Forecast | User Story | Expected Impact | Related Requirements | Estimate | Sprint |
|---|---|---|---|---|---|---|
| 1 | Goal | As a user, I want the system to generate written reports based on AI-provided insights, so that I can easily understand patterns, trends, and peaks in tickets and share this information clearly with my team or managers. | This functionality will automate report generation, ensuring consistency and reducing manual effort. It will make it easier to identify recurring issues and process bottlenecks, improve communication of findings with stakeholders, and increase efficiency in monitoring performance and driving continuous improvement. | FR6 | 8 | 3 |
| 2 | Goal | As a system administrator, I want only authorized users to access ticket insights and manage related data, so that sensitive information is protected and each user sees only data compatible with their authorization level. | This feature will strengthen data security and ensure compliance with internal policies. It will minimize the risk of unauthorized access or data leaks, provide clear control over user permissions, and increase trust and accountability across the system. | FR5 | 4 | 3 |
| 3 | Forecast | As a user, I want to visualize the tickets linked to dashboards so that I can understand which tickets are impacting the process. | This feature will improve visibility of process performance and issues, allowing users to quickly identify tickets that cause delays or inefficiencies. | FR01, FR4 | 5 | 3 |
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: