Hi, community.
I have the following request:1. Need to measure time spent VS time estimated on sprint basis by individual.2. The complexity #1 is that sometimes tasks migrate from one sprint to another, that is why the original estimate not always works for my needs.3. The complexity #2 is that sometimes tasks are being added to the sprint after start (4. I use Capacity tracker https://pdffiller.atlassian.net/jira/marketplace/discover/app/capacity-tracker-plugin for sprint estimation and Team Reports for time logging. Have troubles only with correct and not manual estimation for the sprint. It is important because our team has KPI Estimation accuracy.
Try using Reports by Jira: https://www.atlassian.com/software/jira/features/reportsIf that doesn't work, you may have to create a Dashboard in Jira, or use Confluence to store a lot of Advanced Search Jira filters. If this is the case, please include what fields/values you have access to on your tickets, with screenshots, etc.
Reports in Jira do not work because I need statistics by assignee, and these reports do not cover it.
Hi @ganna_kyselevych
I am curious about your question...
You ask about "VS time", which I am guessing means "value stream time" or some interpretation of lead time or cycle time.
And you note using sprints, and so there is probably a team using Scrum. What problem are you trying to solve by measuring that number for individuals rather than for the team's work as a whole?
Kind regards,Bill
Please include what fields/values you can access on your tickets, with screenshots, etc.
Basically, I can add whatever is needed, coz I have rights of administrator.
This time could be called as "Estimation accuracy" as well.
It means that every team member estimates their tasks for the sprint, then logs real time and the best option when estimation and logged time match or almost match.
What we solve by calculating it by individual: keep every team member accountable for their time, track under- or overutilization of resources. It is one of our individual KPIs. We do calculate team KPIs as well, but we do need individuals'. Let's say, the specific of our team.
Wouldn't the leader of the people on the team and the entire team already know this information from paying attention and asking questions during 1-1 conversations and the daily scrum (stand-up), respectively?
For example, a forecast is provided, and after repeated daily scrums no concerns are raised and progress seems stalled. The team and leader should engage to learn why and what they can do to help, perhaps swarming on the challenge to resolve it.
Hi, @ganna_kyselevych While the tools you're currently using offer some helpful features, handling task migration and additions within sprints for your KPI estimation accuracy can indeed be tricky.
Jira's native reporting and Capacity Tracker might fall short when it comes to tracking time spent versus estimated time specifically within the context of a sprint, particularly when tasks move between sprints or are added after the sprint has started.
However, the Time & Cost Tracker for Jira add-on offers features that can streamline this process and provide the accurate sprint-based time tracking you need. Here's how it can help:
Accurate Time Tracking, Even With Task Migration: Time & Cost Tracker seamlessly integrates with Jira's time tracking, so any time logged on a task is captured, even if that task moves to a different sprint. This means you get a true picture of the time spent on tasks within the sprint they were actually worked on, not just their original sprint.
Handles Mid-Sprint Task Additions: Any tasks added to a sprint after it starts are also included in the Time & Cost Tracker reports for that sprint, ensuring your time tracking remains accurate and reflects the actual work done during that period.
Sprint-Specific Reports: The add-on allows you to generate Time Reports filtered by sprint, giving you a clear breakdown of time spent versus estimated time.
How to set it up:
By leveraging Time & Cost Tracker's capabilities, you can obtain accurate sprint-level time tracking data, even with task migration and mid-sprint additions. This will help you confidently assess your team's estimation accuracy and identify areas for improvement.
Feel free to reach out if you have any more questions or need further assistance!
It looks like you're new here. Sign in or register to get started.
