Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Can Capacity Tracker help us track capacity using lables ?

Selva Praveen Elango
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 30, 2023

We have a sprint where both development and maintenance work is done. We want to maintain a 70% development work and 30% of maintenance work for each developer in the scrum team. We have the tickets marked with lables for dev and maintance. Can the capacity tracker help with this in managing the developers work to assign 70% of dev work and 30% of maintenance work ?

1 answer

Hi there Selva,

Can't advice with regard to Capacity Tracker, unfortunately, but I'm quite interested in the subject itself, since automatically distributing work within the team of experts is our bread and butter at Skills for Jira. Mind answering a few questions for me to better understand how you see weighed distribution?

Since you mentioned Scrum, I assume that your tasks are and selected at the start of a sprint and are estimated in story points. Feel free to correct me if I'm wrong.

1. By "70% of dev work" do you imply "roughly 70% worth of story points should be dev work"? Or is it rather 70% of the tasks?

2. Do you expect assignments to also happen at the start of a sprint? Or you'd rather have people fetch the next assignment as the sprint progresses? Based on priorities and qualification, so that more important tasks are done first and you don't have to re-assign when people go on leave.

3. If it's the latter, is it important to maintain the 70/30 ratio as close as possible within a sprint? Or it's important in the long run. I.e. does "in 70% of cases user should get a Dev task" work or it should be more specific, "within a sprint, as close to 70% story points as possible should go to Dev tasks"?

4. Should task priority be respected, i.e. "if task has higher priority, assign it, otherwise, use the 70/30 rule"? 

5. Does the team get different kind of work as well? Maybe occasionally? Research-and-Development or training maybe? If yes, would this reduce the 70/30 percentages for Dev/Maint or just be added on top of that?

I have more but have to stop here to make it manageable :)

Looking forward to your thoughts.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events