31 Jan 2020
3 MINS READ
In this fourth blog of the series, we will have an informative discussion on how we can achieve capacity planning for sprints.
Our decades of agile practice experience have shown us that most of the agile projects lose out on their committed goals as they are under-committing or over-committing to work in sprints. This leads to scope variance and takes up a good chunk of time in retrospectives of understanding the causes leading to such situations.
The key to avoid such pitfalls and plan better is capacity planning. Teams tend to overlook this critical aspect, which further derails the entire model of all agile frameworks. The diagrammatic representation, Figure 1 shown below depicts different aspects of capacity planning.
Capacity Planning helps teams understand how many story points they are likely to accomplish within a sprint. This planning considers the company’s time off, team members’ personal time off and commitments that could impact the time available for productive project work. Better planning leads to better anticipation of challenges with regards to resource availability and time constraints. It further helps optimize resource’ bandwidth, thereby improving commitment and reliability.
Team velocity is based on actual story points completed in a closed sprint while team’s capacity is based on team’s estimated or projected future availability for the next sprint. From a planning perspective, velocity can be used to determine the number of product backlog items development team could bring into next sprint while maintaining a consistent burndown rate. Capacity helps in understanding the development team’s availability for upcoming sprints and the number of backlog items that the team can really bring in, based on the available capacity.
Though both velocity and capacity have their respective importance in planning, the success of a team is based upon the value it delivers.
A simple yet effective capacity planning can be done by breaking down the tasks into easy steps:
Step 1
Consider the sprint duration, total development team members, workdays in the sprint and business hours per day at client location to know the total hours (A) per team member in the sprint.
Step 2
Interpret the percentage availability per day, per development team member or percentage allocation of a development team member to the project and then calculate the individual hours available in the sprint. This will help calculate the team total (B) as follows:
B = Σ (A * Percent availability) 1 to n where n = total development team members
This calculation will also cover influences based on productivity and any unplanned unavailability in the sprint.
Step3
Calculate planned activity hours (C) that would be otherwise unavailable due to planned activities like public holidays, personal leaves and time invested in Agile ceremonies e.g. scrum or XP and planned meetings during the sprint.
Step 4
Consider the amount of ‘To Be Done’ work in hours (D) that would be taken in from to-be-completed/past sprint to the next planned sprint.
Step 5
Thus, the net capacity in hours would be E = B – (C + D)
Step 6
Capacity in story points (F) would be as under:
F = (E / hours required to complete 1 ideal story point) where hours for 1 ideal story point can be found by brain storming within scrum or other Agile framework team e.g. XP or based on past sprint data.
Use of appropriate tool for capacity planning helps to do the capacity planning faster. Sample tool for capacity planning.
Image Placeholder for the image from the excel
This capacity plan is to be used by agile projects during iteration planning to plan for the number of story points based on the team availability
Image of the tool for capacity planning without the dates and information. Explanation in the image should indicate that as per the data or dates specified the planned estimates are calculated and presented as a plan.
In a sprint, Stretch Objectives should be encouraged, as there is a high probability of achieving these to the extent where available capacity is not drastically over-exceeded. Else, it would just result in scope variance and unfinished work to be completed in the next sprint. It should be noted that 2% to 5% above capacity is an ideal scenario for Stretch Objectives.
To summarize, capacity planning for sprints is the process of determining the amount of work a team can deliver in a sprint and towards completion of product backlog items. Capacity is the maximum amount of work a team can deliver in a given sprint.
Proper capacity planning helps to avoid over or under commitments and brings in a consistency in delivering optimally efficient delivery. As rightly depicted in the Figure 2 above, the prime objective of capacity planning is to maintain the proper balance between team capacity and story points committed in the sprint.
About the Author
Suhas Hanumantrao Mali, Sr. Consultant – PMP, CSM, CSPO, SAFe Agilist, ITIL V4 Foundation, MS Azure Fundamentals – has over 20 years of IT experience out of which majority of experience is in Project Management, Pre Sales Solution Architect and Agile Coaching. Author has coached 1000+ Consultants in Hexaware and at Client locations, experienced in leading Enterprise Agile Transformations and Technology Migrations, experienced in coaching Business Teams, Product Owners, Scrum Masters and Development teams in Lean and Agile Frameworks.
Application Transformation Mgmt.
14 Jul 2021
02 Jul 2021
24 Jun 2021
22 Jun 2021
14 Jun 2021
13 May 2021
11 May 2021
28 Apr 2021
17 Dec 2020
14 Dec 2020
11 Dec 2020
27 Nov 2020
13 Nov 2020
12 Nov 2020
09 Nov 2020
06 Nov 2020
22 Oct 2020
13 Oct 2020
06 Oct 2020
17 Sep 2020
15 Sep 2020
26 Aug 2020
11 Aug 2020
07 Aug 2020
31 Jul 2020
22 Jun 2020
19 Jun 2020
11 Jun 2020
20 Apr 2020
03 Sep 2019
31 Aug 2019
03 Jul 2019
26 Apr 2019
28 Mar 2019
13 Aug 2018
19 Jun 2018
Application Transformation Mgmt., Healthcare, Insurance
18 Jun 2018
28 Nov 2017
14 Sep 2016
03 Sep 2016
25 Aug 2016
11 Jul 2016
BI & Analytics
19 Mar 2009
26 Nov 2010
Digital Assurance
02 Jan 2012
17 Feb 2012
Infrastructure Mgmt. Services
02 Mar 2012
03 Jan 2013
04 Feb 2013
06 Feb 2013
Digital Assurance, Enterprise Solutions
14 Feb 2013
18 Feb 2013
21 Feb 2013
27 Feb 2013
Others
01 Mar 2013
04 Mar 2013
Enterprise Solutions
05 Mar 2013
18 Mar 2013
Digital Assurance, Enterprise Solutions, Others
22 Mar 2013
12 Apr 2013
26 Apr 2013
29 Apr 2013
13 May 2013
11 Jun 2013
17 Jun 2013
25 Jun 2013
19 Aug 2013
26 Aug 2013
27 Aug 2013
03 Sep 2013
10 Sep 2013
19 Sep 2013
24 Sep 2013
26 Sep 2013
30 Sep 2013
01 Oct 2013
03 Oct 2013
01 Nov 2013
19 Nov 2013
Enterprise Solutions, Manufacturing and Consumer
28 Nov 2013
03 Dec 2013
20 Dec 2013
03 Jan 2014
22 Jan 2014
27 Jan 2014
31 Jan 2014
12 Feb 2014
13 Feb 2014
20 Mar 2014
24 Mar 2014
17 Apr 2014
11 Jun 2014
Manufacturing and Consumer
26 Jun 2014
30 Jun 2014
10 Jul 2014
15 Jul 2014
16 Jul 2014
18 Jul 2014
28 Oct 2014
13 Jul 2015
06 Aug 2015
26 Aug 2015
28 Sep 2015
07 Oct 2015
26 Oct 2015
07 Mar 2016
22 Mar 2016
13 May 2016
23 May 2016
15 Nov 2016
22 Nov 2016
25 Nov 2016
Business Process Services
25 Apr 2017
Banking and Financial Services
18 May 2017
30 May 2017
23 Jun 2017
27 Jun 2017
18 Jul 2017
26 Oct 2017
Healthcare, Insurance
11 Dec 2017
25 Jan 2018
21 Feb 2018
14 Mar 2018
( Mandatory field * )
The information you provide will be used in accordance with our terms ofPrivacy Policy
Please Check on "I Agree" to register for the blog.