Jira Image of the Day: Are You Done yet?

[#1]

An issue in Cloud

An issue in Server and Data Center

Concept Relates To

Application Type	Jira Work Management, Jira Software, Jira Service Management, Jira Core
Deployment Type	Jira Cloud, Jira Server, Jira Data Center

What is shown?

A Jira issue with child issues, an estimate, and time logged

Visit: <your-site-name>.atlassian.net (Cloud)
Visit: <your-jira-url.com> (Server and Data Center)

What can we learn?

Is someone constantly asking, “Are you done yet?” Try teaching them about the progress bars in Jira. If you’re logging time, they can answer that question without bugging you!

In Cloud

In Cloud, if an issue has child issues, a progress bar and the total percent complete is displayed. The original estimate and time tracking information is shown in the right sidebar. The right progress bar shows I’ve exceeded the original estimate by 3 days and 6 hours. (Oops!) Any user who can view the issue can also view the time tracked.

In Server and Data Center

In Server and Data Center, individual progress bars are shown to the right of any child issues. Time tracking information is shown in the right sidebar. The progress bars show 40 minutes of work remain. (Almost done!)

Why Log Work?

After the work is done, compare the actual time spent to the estimate, to understand effort and improve estimation next time.

Estimates and time tracking are very powerful metrics. They’re NOT about how good of a worker you are or how fast you are, compared to your colleagues.

Use this information to communicate progress and improve efficiency in the future.

---

Back to intro and image list

An issue in Cloud

[Łukasz Modzelewski _Lumo_]

It's great when teams use the correct statuses for the job and keep track of time, but it's hard to achieve.

Especially when team members are changing context, it can get messy. I have worked with teams changing statuses during daily meetings, or adding estimates after the time was logged—so those things can be corrupted ;)

Discipline is needed, or workflows supporting the 'right' process behaviors, but again, I've worked with teams that were negative towards any changes in terms of tracking estimates...

So it's very important to teach people about the benefits of those changes ^^
The more we estimate, the better we estimate.