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 ?
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.
1. yes 70 % of the story points be dev work and 30% of the maintenance work
2.yes expect assignemts to happen in the sprint planning itself. in that way we will have the distribution of work as 70/30
3.
4.yes the priority is respected. we prioritise the work within the 70: 30 ratio
5. we do get different work. those will be based on the priority. In that case 70: 30 ratio will be disturbed and we try to complete task based on the priority
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.