Are you tired of logging hours?

[ElenaK_NemetschekBG]

Are there any effective alternatives to time tracking?

We are a small team of product developers & consultants. We used to log time for our work but we generally saw the inefficiency of it. We noticed there was too much of an overhead. A decision was made to stop logging hours and the team was thrilled. The consultants still log hours corresponding to the work with different clients but the product team does not.

Instead of logging hours, the product team started using story points and the velocity in a given sprint. But without the logged time, we lose track of how many hours the scrum team spends on each project. For example, how much time was spent on support versus how much time was spent on product features.

How do you track the work spent per project? Do you know another way to track how much work was spent on a project without logging hours?

We have an idea how to automatically track the distribution of resources, so stay tuned for an update!

[Gracjan Wesołowski _HeroCoders_]

Hi, @ElenaK_NemetschekBG 

have you considered third-party time-tracking apps?

I can recommend you our Clockwork Automated Time Tracking & Timesheets Free app, which has an automatic time-tracking feature. 

When automated timers are enabled, Clockwork will record the time that an assignee has an issue in an active status, and use this with the working hours to calculate the time worked. Automatic timers ensure that all work is logged, without users having to take any actions.

It might fit well in your case. If you have any questions, let me know.

Cheers!

Gracjan

[Anna Zoucha]

You could have the product and engineering teams estimate in ours rather than story points. That's what our team does! Two birds, one stone. 

[ElenaK_NemetschekBG]

Thanks for the tip Anna! How do you measure if the estimation matches reality? Do you have a point in time when you analyze the information? 

[Valeriia_Havrylenko_SaaSJet]

Hi @ElenaK_NemetschekBG   👋

I guess you can try Time in Status for Jira Cloud  to track how much work was spent on a project without logging hours. If developers keep the board updated, then it will be possible. Add-on developed by my team.

The primary purpose is to help teams gather valuable data about the lifecycle of your issues in Jira. Add-on allows you to measure and visualize the time spent in each status, such as "Open," "In Progress," "In Review," and "Closed," and provide 7 types of reports to help you identify areas for improvement. But also with our add-on and reports you easily can have information for example "how much time was spent on support versus how much time was spent on product features".

One of the helpful report for you can be The Assignee time report. Report shows the total time a particular assignee has been working on the issue. That’s why it’s especially useful for identifying who is responsible for the workflow delays.  It shows which assignee has been solving the task longer than it might be necessary. 
How it works:


Also we are working on new feature "Time in status sprint report" witch will allowed you to track Team velocity, workload, completion rate, commited, completed, scope change. We are going to release it soon!   
Add-on has a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌
Valeriia

[RVS_Support]

Hi @ElenaK_NemetschekBG 

The easiest way would be track time the time the issue spent with a particular assignee or time in a status, like "In Development", "In Review" etc. We have built an app for the same use case.

Time in Status Reports 

The add-on provides the time in status for the complete lifecycle of the issues. In the example report below you can see the tie with Assignee for each of the status. The app has 20+ reports which help meet variety of use cases and is cost effective too.

Do try it out.