![]() ![]() This helps you monitor whether the epic will release on time, so you can take action if work is falling behind. Tracks the projected number of sprints required to complete the epic. Similar to the Epic Report, but optimized for Scrum teams that work in sprints. This helps you manage your team's progress by tracking the remaining incomplete and unestimated work. Shows the progress towards completing an epic over time. This helps you identify potential bottlenecks that need to be investigated. This helps you identify whether data from the current process can be used to determine future performance. Shows the cycle time for your product, version, or sprint. Control Chart Control ChartĪpplies to: Projects, versions, or sprints This helps you determine if your team is overcommitting or if there is scope creep. Shows the work completed or pushed back to the backlog in each sprint. This helps your team manage its progress and respond accordingly. Tracks the total work remaining, and projects the likelihood of achieving the sprint goal. Reports for Scrum projects Burndown Chart ![]() This helps you determine your team's velocity, and estimate the work your team can realistically achieve in future sprints. Tracks the amount of work completed from sprint to sprint. ![]() Provides a visual representation of a sprint's scope, as well as its remaining work. Reports for team-managed software projects Burnup Chart Learn more about switching between boards in a company-managed project. Ensure you're viewing the correct board before generating a report. Jira Software runs reports on each board in the project. Company-managed projects support multiple boards. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |