Ability for TFS sprint capacity and days off for a project to be inherited by teams
For businesses where a single scrum team works on multiple projects/products per sprint, sprint planning is painful in TFS 2015.
One approach is to have a single TFS project and teams representing each product. This simplifies backlog management. However, capacity planning is still time consuming.
I would recommend capacity planning for a team has a checkbox to "Inherit capacity and days off from parent project". This would allows only having to set capacity and days off at the TFS project level without having to duplicate it at the sub-team level.
Currently TFS is not designed for single scrum teams with multiple products in a sprint, and this would go some way to make TFS more usable for small businesses.
Martin Underwood commented
I agree with Raju, this is the biggest gap in TFS. Not even looking at it from a Project Management aspect but from a development manager. One person (resource) has a limited amount of hours they can work each day, why in the world TFS allows you to allocate a person unlimited number of hours per day seems like a bug to me. It doesn't matter what projects/sprints they are working on, the restriction is common sense in my opinion.
Shalem Raju commented
In VSTS, How to constraint/restrict a team member's working capacity in case working in multiple projects.
Assume a team member A works with multiple projects/applications(P1,P2,P3). While doing Capacity planning, i'm able to allocate him with 8hrs per day in each project(P1,P2,P3). Is there any availability to freeze/constraint a team member's capacity to 8hrs in all projects combined(capacity should be restricted to 8hrs in combined). This would be of great help.
Don VanVooren commented
This would provide great visibility to our Management team as they would have access to team projects at a higher level
David Bottiau commented
Another possible solution would be to create a project/product sprint around a team sprint. I mean, The "My team" group has a collection of sprints and each sprint can be linked to the projects/products the group intend to work on.
Would like to track planned capacity / sprint to actual. Planned includes allocation for scheduled absences, but if someone calls in sick, there is no way to capture that as an unplanned impact to capacity.
Maybe keep it on the project itself, since availability can be different to multiple projects. Adding it to your user profile would make that harder to manage.
Would like to be able to add a comment as well so others can see why someone is not available. For example, on holiday or doing some other project elsewere.
Kevin Auch commented
We often work with part-time, and it will be great to be able to choose fix day of presence by week.
Would be awesome :)
Okko Oulasvirta commented
Add global capacity planning functionality for multiple teams and projects so that people in resource planning may use vsts as resource planning tool
What I would like to see:
- Enter working days/days off once for all employees and have each project look in that global calendar so I don't need to enter it for each project
- Instead of capacity per day, allow me to enter a capacity per day of the week
It would be great if this functionality would allow easier capacity integration with MS project. Currently I need to update peoples availability in TFS and MS project, based upon an excel calendar being completed by the team. If we could have a one-stop-shop, allowing all team members to update this, it would give me at least one hour per sprint less waste :-)
Barry Postma commented
Agree with @Fokko and @Harald-René.
Would like to add that apart from people working on specific days during different weeks (even inter-sprint) people working only for 4 hours on one day would be nice to register in the sprint.
In an SMB like ours scrumming developers are usually also assigned to other - non TFS - tasks for 2-4 hours a day. The current way of calculating hours backwards over the available days without specifying leave is too laborious.
James Hanley commented
To me, this seems like an integration point to Exchange or PeopleSoft or whatever system used for tracking office hours, vacation, or PTO - not a core function of TFS and not a a redundant feature to the above systems that then needs to be either synchronized or updated in multiple locations by the end user.
I'd like to be able to put a comment next to days off - people always seems to forget if is it because of vacation, holidays, other work, etc.
Pavel Shkleinik commented
While TFS developers thinking if there is a need for timesheet in TFS (and they do it during last 9 years) you can use some TFS plugin (like TX Chrono http://www.teamexpand.com/product/tx-chrono). It provides you with ability report/approve time, adjust personal timetable, holidays for different locations, nice reports and bench of other useful tools.
Joe Aubin commented
I would also like to have a global calendar as opposed to one per sprint and then let the system determine what holidays and personnel non-work days are applicable to a given sprint. It is a pain to have to go to multiple projects and enter things as obvious as Christmas while making sure that I select the "correct" sprint.
Harald-René Flasch commented
In order that TFS is able to calculate team member capacities it is necessary to define usual workdays for each team member.
It is possible to configure capacity per day and off-days for each team member for a sprint but I can't find a way/location to configure workdays.
Team Member A: works, Mo, Tue, Wed, Thu
Team Member B: works from Tue, Wed, Thu, Fr
I don't want to do this manually and again and again for each sprint.
Also don't see a "calender" containing public holidays ...
Yer Yang commented
Would be great to be able to query team members and see what projects they are assigned to and their capacity allocation per project as well as the sprint begin/end dates. This will help project managers when trying to pull resources.
I would add to have ability to manage holidays for different countries for groups of members on the same team instead of managing using multiple teams.
These approaches takes too much overhead
Ivan Vorona commented
Valid point, I totally agree. Plus would be very helpful to see resource allocation diagram which shows what resource is going to do in following few weeks based on his assigments and priorities.