As a project manager and supervising a team of 15 people, I have to take responsibility over a series of different issues in communication, resources, and risks. The daily challenges on my path are various. On one hand, the clients – constantly changing their priorities, defining new goals or demanding unplanned changes. On the other, the team availability. There are the holidays, training, sickness, part-timers, etc.to consider. To keep the project time and cost under control, the visibility around man-days, team organization and disposal around sprint goals is key. So, how to calculate sprint capacity in man-days for agile team management?
Let’s say, each sprint is 2 weeks. So it’s not as easy as (number of team members * number of days in sprint) or for example, (15*10) = 150 man-days. A project manager thus needs a tool that helps to keep an overview of team availability and man-days capacity for each sprint and to ensure everything runs smoothly. Over the past years, I struggled with finding the right solution for an accurate project plan and estimation.
My initial thought was to use JIRA Tempo Planner. We were already using it in different project stages and it helped to manage sprints, backlogs, and releases successfully. However, using JIRA for team management would mean another plugin in your local JIRA installation and if you are going to use this to calculate only the sprint capacity, the cost cannot be justified. JIRA was over and done. I decided to give a go with plain old Excel. With little automated features, this meant the need to create my own calendar, insert details of the people, their availability and create my own grouping via pivot tables, etc. A lot of manual work and a limit of views you can have on it, which can be a major disadvantage for agile team management.
And then I remembered – The MS Project tool is still on my computer! Being considered a typical waterfall product, MS project is not often used in agile environments. But I was ready to show its potential, as I will demonstrate in this article. Simply because MS Project must be viewed as a database and so it’s agnostic of the methodology that you use. The calendar, grouping possibilities, etc. are already there. I just needed to configure the project and enter the data!
In the Gantt chart you can create a new view that groups the team members by their group
Now you build a view here also to group and see capacity:
I have 24 development days in the first week and 17.6 in the second week of this sprint.
If your sprint starts in the beginning or in the middle of the month you can set the count of weeks to 2
Then the days are summarized by 2 weeks - your sprint length
This gives me the power of MS Project and its different views and the calculation at the same time. Even with regular team sizes, I believe that this can be of great value to correctly predict the capacity for the next sprints.
Isaac Van Der Straeten is Project Manager at Amplexor, based in Belgium. With over 20 years of experience leading projects across industries, at Amplexor he’s the driving force behind client website and software implementations. Isaac is certified as Project Management Professional (PMP) and Scrum Product Owner (CSPO).