Resource Allocation while Iteration/Sprint Planning

[Maulik Shah]

* We want to see resource allocation in term of %, Over-allocated or under-allocated in specific Iteration while doing sprint planning.

* Sprint Planner or manager will plan resource (Developer/QA) based on resource and hours, we will add task in Sprint and allocate to resource. Want to see view that which resource is allocated fully or %

*Also during review we want to see that Iteration is not getting complete because of which resource, (Which resource is not completed their own task timely).


Can you please guide me how to achieve same in JIRA Agile?

Regards,
Maulik Shah

[Oleh Vasyliv]

Hi Maulik,

As Peter said, this is not available in a pure JIRA. ActivityTimeline add-on supports resource allocation and planning based on task estimate, people's capacity and shows a red indicator if someone did not finish a task on time or got overloaded with other tasks. The amount of scheduled work is displayed on a timeline interface and workload indicator per each person. Add-on is available at:

https://marketplace.atlassian.com/plugins/com.activitytimeline.plugin

https://activitytimeline.com

[Peter Van de Voorde]

Hi Maulik,

This is not possible with out of the box Jira Agile.

You can take a look at the following plugins and see if they might help you out :

https://marketplace.atlassian.com/plugins/FEYWA

https://marketplace.atlassian.com/plugins/is.origo.jira.tempo-plugin

Best regards,

Peter

PS: as a Scrum Coach I have to say this : don't start playing the blame game, if a sprint failed it's the entire team that's at fault not just one person, the team did not follow up correctly.

[scott.fawcett]

So without this functionality how does "the team", scrum master, project lead, etc. know when they should suggest somebody get help?  An easy display that updates in real-time to compare resource availability vs. workload is immensely valuable in understanding when the team needs to review the total work and reassign (self-organizing). In my experience, in real-life, rarely does anybody think they can't complete their assigned tasks when behind...and then they don't.  I'd much rather have an objective heads up based on data as opposed to somebody not raising a red flag in scrum because they think something magical is going to happen to get them back on track.

If you have experience with the blame game it's because you didn't have data to make changes during the sprint.  This data is used to make real-time adjustments during the sprint to ensure success as opposed to waiting until the end to see how didn't complete their tasks.