Not all the agile projects use Story Points for estimating the backlog items, like stories or tasks. Some projects use time estimates (work hours or work days) while some others also track the time spent on every backlog item or sub-task on a daily basis. Tracking such project that uses time estimates in an agile manner, by using the agile specific tools like burndown or burnup charts, might be difficult because the big majority of the agile tools are based on Story Points calculation.
Here we describe how Great Gadgets app for Jira solves this problem for you and how to track a Jira project that uses time estimates in an effective way. Great Gadgets is an app (add-on) for Jira (Server, Data Center and Cloud) that offers a set of useful gadgets for tracking Jira projects; it includes the necessary burndown / burnup charts and velocity charts that you need for tracking sprints or entire releases by time estimates.
Two Time Tracking Strategies
First of all, let’s make it clear what the time tracking fields of the Jira issues are.
Original Estimate – represents the total time estimate of the Jira issue. It is usually set at the issue creation or right after, but can be adjusted later, during the project.
Time Spent – is the total work logged on the Jira issue. This field is actually the sum of the time spent of all the work log entries of the Jira issue. The value of this field increases each time someone logs the work on the Jira issue.
Remaining Time – represents the estimated remaining work of the Jira issue. When Original Estimate field is set for the first time, Jira sets automatically the Remaining Time to the same value as of Original Estimate. Then, when someone logs the Time Spent, the Remaining Time adjusts accordingly or it is manually overwritten by the person who adds the work log entry.
Great Gadgets offers two options / strategies for tracking the Jira projects that use time estimates. It depends on you which one to choose:
Once you decided what tracking method to use and you installed Great Gadgets in your Jira instance, follow the steps below to display the necessary charts on your Jira dashboard.
Sprint Burndown Burnup Chart by Time Estimates
This chart helps you determine the team’s progress during the sprint.
Release Burndown Burnup Chart by Time Estimates
This chart helps you determine the progress at the project level. You can also generate the chart cross-teams or cross-projects (see Cross-project release burndown chart in Jira with Great Gadgets app for more details).
Team Velocity Chart by Time Estimates
The team’s velocity is an essential metric that helps the Agile teams not to over-commit during sprint planning meeting, but also helps them to see how they perform from a sprint to another.
That’s it. If you have further questions, please don’t hesitate to contact firstname.lastname@example.org.
Danut M _StonikByte_
We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events