Capacity Tracker

JIRA supports for dark color scheme - but the Capacity tracker does not seem to be affected by it, it look wiered and it not professional. But from a functionality standpoint - seems to be working fine.

Currently in Capacity Tracker it shows capacity by role when a person is assign to a task. but can we have a report by type of task even if the task is not assigned to anyone. For Ex: A story needs work from development team and also from testing team. So if I can add estimate for testing sub-task without assigning anyone, so that it gives me visibility as to how much work left on all the testing subtask. Because it is practically not possible to assign all the subtasks from the beginning of a sprint.

This app is great for sprint and release capacity monitoring across different teams - love how quickly overallocation can be identified. The granularity in individual team availability is extremely useful - from offering half-day outages to adjusting # of hours in a work day for them. (This helps particularly with lead/senior or manager team members who can't dedicate a full 8 hours to their work each day.) There are a few features I'd love to see in the future for this that would be helpful! Suggestions: - Add a " View in search" option when looking at individual's list of tasks in the Sprint. This helps to reprioritize tasks quickly straight from the tool on an individual that may become overallocated, rather than going to a different tab and spooling up a new search. - Add a "Location" tag or something similar to track different team member's locations so different "team holidays" can be applied to different teams in different locations. This is key for a world where we are becoming more and more remote from each other - it would be prudent to separate them easily to account for different national holidays, etc.

• 

  Inprowiser Engineering

  Hi,

  Thank you for your review, we are happy to see the Tracker improves your productivity.

  Would you be so kind as to send us your suggestions through our support portal so we can track them and potentially include them to our backlog?

  Thank you!

The Capacity Tracker is great for teams starting in their scrum practices and contributes towards quick wins within solving challenges of being overallocated. It's also useful for those who are examining their estimation practices and understanding what points means for a team. The hours aspect works best here. Story Points in Capacity Tracker doesn't seem to be useful. The Kanban implementation of this doesn't work as well, because it's constrained to the Release versions, which may or may not overlap work for a team member, or may not be geared to consistent timeboxes.

The capacity tool is a great tool which meets our needs. Switching from Version One to Jira we struggled to find a capacity tool which was able to fulfill our capacity tool which we used prior. With the help of Vijay from the Inprowiser Team, we were able to filter our board to make sure the tool was able to work according to our needs. Vijay was very knowledgeable on the information he provided and we were able to successfully implement the tool which we now use on an everyday basis!!! So thank you so much for all your help Vijay!!! :) Suggestion: One suggestion or feature advancement which we could really use is entire sprint capacity instead of daily capacity. We have a team which consists of devs working on multiple projects so we ask for their total capacity for the project which we are tracking capacity for. So when they give me 20 hours for 9 days, I would have to go divide 20/9 and place "2.2222" to give me the display exactly 20 hours for capacity. This would help us resolve one step which is vital during our planning meeting process.