How do I track people capacity, story points on stories and hours for tasks and capacity?

[Wayne Wilson]

Using company managed project. I would like to estimate stories using story points, and tasks using hours. As I am loading a sprint, I would like to see how many hours each person has assigned to them, but I would like to track velocity over time by story points. I'm in the process of changing from DevOps to Jira. I'm confident Jira can do everything that DevOps was doing for me, just working with a learning curve here.

Thanks!

[YY Brother · Accepted solution]

Hi @Wayne Wilson 

Welcome to our Community.

For Jira Software, I think we have those ways to track progress:

• Sprint Planning phase: 

 

• Daily Standup - Active sprints

• Scrum Reports:

Of course, if you see all sprints' progress based on both story points and timespent, you may try this App: https://marketplace.atlassian.com/apps/1233252/sprint-reviewer-pro?tab=pricing&hosting=cloud

Hope it helps. Thanks,

YY哥

[Wayne Wilson]

Thank you.

For my Workload by assignee window, I only see columns for Issues, Subtasks, and Story Points. I don't see the Remaining Time Estimate column.

[YY Brother]

My pleasure. I think you need to change the board configuration like this:

[Wayne Wilson]

Awesome!

Now I see the Remaining time estimate. For the process I've been describing, I feel like we'll put story points only on stories and time estimates on the tasks that satisfy the stories? If so, then I assume I will assign tasks and not stories? So in my Workload by assignee window, the stories would all be 'Unassigned' but the Unassigned row would have my total story points for the sprint. Then, each dev's name would have a row with the total number of hours currently assigned to them for the sprint?
Let me know if I'm tracking with you there. Thanks again!

[YY Brother]

Hi @Wayne Wilson 

In my practice, I'd like to split story into sub-tasks so that stories and their sub-tasks have strong parent-child link. However, this process is not mandatory and is only used when scrum teams think through splitting, they will know more about the implementation of the story.

We recommend split big story into smaller ones and then teams won't need to split the stories. Hope this interpretation will help your team.

Thanks,

YY哥

[Stephen_Lugton]

From what you've said I'm going to make the following assumptions:

• You're planning your work in Sprints
• The tasks are being used to deliver the stories

Make sure you have Original estimate visible on tasks and story points on stories.

Estimate both task (Original estimate field), and stories (Story Points); that'll give you your hours on tasks for capacity.

Put the refined stories and task into your sprint and off you go, only the stories will show up as part of your velocity.

---

However doing it this way defines story points as a set number of hours, and takes away the purpose of using story points.

If you are going to be using Story Points then just use Story Points and once you've got your velocity you'll know that in one Sprint your team can do this much work so all you have to do is assign that many story points to the Sprint and away you go no need to track hours assigned.

[Wayne Wilson]

Stephen,

I think I like most of what you said here. This makes sense for tracking velocity over time by story points. However, I don't want to load the sprint 'only' by story points because we assign work to devs during planning. A given Story may have several tasks, and those tasks may be assigned to various devs so I'd like to be able to see how many hours each dev has assigned to them as we go through planning. If I know that a dev has 60 hours of available capacity in this sprint, I want to assign 60 hours worth of tasks to that dev. Thanks so much for your communication, I feel like I'm close, but not quite where I need to be yet.

[Mark Segall]

Hi @Wayne Wilson - By default your scrum board will track against story points so nothing needs to change on that front.  For tasks, you'll want to leverage a unique screen that replaces the story point field with the Original Estimate field.  

To see how many issues each team member has assigned to them, you'd need to leverage a dashboard that you can review on another tab leveraging the Workload Pie Chart configured like this:

• Project or Saved Filter: You'll need a filter with JQL like this:

  • Project = YOURPROJECT AND sprint in futureSprints()

• Statistic Type: Assignee
• Time field to report on: Original Estimate
• Refresh Interval: Your choice

NOTE: A caveat to the filter above is that Jira does not natively provide a way to query for just the next sprint. So, you'll need to ensure Original Estimate field is not set on issues that are beyond the next sprint or you'll get false readings. 

[Wayne Wilson]

@Mark Segall

I don't see how to add that JQL. When I click to 'Change Filter or Project...' I don't see how to add custom JQL?

[Mark Segall]

You need to first create the filter:

1. Navigate to Filters >> View all issues
2. Enter the JQL and press enter to search
3. Verify the desired results are returned
4. Save the query as a filter
5. Update the filter permissions (Next to the filter name at the top of the screen, click on Filter details