Project sprint reports are designed to be able to evaluate the project actions, patterns, best and worst practices in various planned sprints.
We know the value of analyzing each sprint to understand the way to reach the most efficient practices in planning and execution of the sprint plan.
Sprints are only usable with the Jira integration and retrieved automatically for the corresponding projects in Jira.
Since the projects in Valven Atlas can contain various Jira projects, a Valven Atlas project can also contain more than one sprint. Therefore, the project and sprint filters are placed at the top of the sprint page.
On the sprint page, Valven Atlas offers various analyses on planning and current status to provide insights on the actions taken so far and the requirements to meet the sprint expectations as well as valuable insights to guide the users.
Sprint Features and Overview
Each sprint should have a start and an end date as well as developers that will be taking part in the sprint.
After a related project and sprint are selected, Valven Atlas also adds the completion rate to provide the current status even in the first look. If there is any issue with the planning, the possible problem is highlighted in the Completion Rate area.
With the Overview table, Valven Atlas offers a summary to show the whole sprint scope and the issues that have been finalized. This summary consists of three main components to highlight the progress;
- Items section corresponds to the related issues
- Effort is derived from the story points in the sprint
- Time is based on the estimation for the committed section and registered work log in the issues for the completed section
One of the most critical parts of the Sprint page is the direct insights where Valven Atlas suggests how the process can be improved and highlights the possible issues in this sprint to meet the time requirements for the sprint success. The Insights section guides teams to keep track of the current status and identify the missing points to successfully deliver product features.
The Burndown Chart demonstrates the current status based on the story points or issues -if story points are not being utilized- and a historical overview of the sprint to understand when the team was behind the schedule and what kind of effort in a specific time period enabled the teams to perform well with the sprint objectives.
The goal should not be to follow the guideline indicator exactly but to keep track of the process and realize the likelihood of completing the sprint in the planned time period.
Based on the guideline and the actual progress, teams can easily take actions to match the value in the guideline and manage their time and requirements successfully.
Cumulative Flow Diagram
This report demonstrates the progress and current status based on the story points or issues -if story points are not being utilized- and their types. The Cumulative Flow Diagram also provides historical analysis to highlight the progress throughout the spring and identify the gaps in terms of story points or issues.
This report also helps teams manage the issues successfully in case any deduction is required to fit the time constraints in the sprint while showing the process and missing points along the way.
Valven Atlas gives a sprint breakdown at the issue level by visually showing the issues with their;
- JIRA ID
- JIRA Name
- Type (epic, feature)
- Status (in progress, done, etc)
- Estimated (in terms of story points)
- Work Log (current effort)
One of the key points of having such a breakdown is understanding the active issues in detail because it will enable team leaders to make immediate data-driven decisions for well-planned sprints. Additionally, it is easy to identify if there is any problem with the way the issues are defined for the sprint or if there is any missing work log data to measure the effort and plan for the future sprint in the right way.