The document outlines an agenda for capacity planning for a News Team. It discusses determining team capacity through calculating average engineer velocity, computing team capacity, and determining program scope. It describes measuring and analyzing capacity using steps like calculating story points completed. The document provides an example of how the News Team performed capacity planning for a specific release, including determining their workload, reducing it using techniques like breaking programs into phases, and conducting a Fist of Five vote to get team consensus. The benefits of capacity planning include optimizing resource use and improved forecasting.
DC MACHINE-Motoring and generation, Armature circuit equation
Walkthrough - Capacity Planning for PI Planning (1).pptx
1. Confidential and proprietary information. Do not distribute. ® 2021 Business Wire, Inc.
Capacity Planning for PI
Planning
The News Team (Josh Riddell + Alisa Smith)
2. Agenda
What is Capacity Planning? page 2
Benefits and Impact - Alisa page 3
News App 5.6 - Measure + Analyze – Alisa (1-3) page 4
Fist of Five Voting page 5
News App 5.6 Formulate – Alisa (1 + 4) page 6
Next Steps page 7
Thank You page 8
2
3. Benefits and Impact – p. 3
High Quality Work - By understanding the capacity scrum, no matter at what level, one can focus on the highest work priority
and make staff adjustments that would ultimately align with the strategic goals.
Improved forecasting and predictability - Not only to improve performance in their next sprint but to increase
delivery predictability overall.
Committing and delivering - Using data from previous sprints improves commitment confidence, knowing what your team
can deliver in a given period.
Get more done with the same amount of resources - create more value with resources
Better planning - 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.
Know the demand of resources –this is the process of forecasting shortages or excesses of resources in the short or
long term. It is carried out by analyzing the gaps between the Capacity of resources against the demand for resources.
3
4. News App 5.6 – Measure + Analyze p. 4
The overarching goal of agile capacity planning is to optimize capacity. As
previously mentioned, this includes effective resource use. Fairly distributed work.
Real time data and better planning.
Here are 6 simple steps to get there:
• 1.Calculate Average Engineer Velocity Per Sprint - - Add up the total individual story
points completed from each sprint, then divide by the number of sprints.
• 2.Compute Team Capacity - Dividing the total Story Points completed by the team by the number of Sprints.
• 3.Determine List of Programs - Preferably 1 month to 15 days before the start of the quarter, provide the
list of programs and their scope to your Engineering Team so they can ask questions and get to know what they are developing.in
advance.
Next is Josh with steps 4 – 6.
4
5. News App 5.6 Formulate – p. 6
Agile capacity planning involves working out the capacity of your scrum team for a particular sprint - then determining how much of
the product backlog you can expect to complete. There are several tools to use in team capacity, resource allocation, and
determining available resources. These include JIRA, Total Story Points, Capacity Planning Template, Fist of Five Voting,
Engineering T-Shirt Sizing and Velocity Chart.
Here are the steps to loop through to Formulate your Team's Capacity:
1.Review Short List of Programs – Team Capacity Versus Total Story
Points 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. Review as a
team the selected programs which match your team's capacity.
Next Josh will review a technique for getting feedback or gauging consensus on the short list of programs.
1.Else Trim Program List: - Methods for reducing quarterly workload story
points includes:
I.Remove Some Programs Outright - Eliminating a program from the quarter
based on prioritization and T-shirt size. It will be on priority for the
next quarter.
II.Break a Program into Phases, Try Step I Again - Looking at how to reduce
the scope of a program into completing some for that quarter and
completing some for the next quarter (thus reducing the T-shirt size) LOOK
AT WORD: PHASES
5
6. Agenda
What is Agile Capacity Planning? page 3
Goals of Agile Capacity Planning page 4
Challenges of Agile Capacity Planning page 5
News Team Agile Capacity Planning Process page 6
The Benefits of Agile Capacity Planning page 14
Agile Capacity Planning Appendix page 15
6
7. What Is Agile Capacity Planning?
Agile capacity planning involves
working out the capacity of your scrum
team for a particular quarter - then
determining how much of the product
backlog you can expect to complete.
It is sometimes known as capacity-
based quarter planning or commitment-
based quarter planning.
7
8. Goals of Agile Capacity Planning
The outcome of Agile capacity planning isn’t simply
to know how much capacity you have. It’s about
knowing how much you can realistically commit to
delivering within the timeframe. And that’s not just
about people x time.
It’s about keeping resources optimally engaged to
deliver their best work - so they can create
functionality that delights your customers and users.
8
9. Challenges + Impact of Agile Capacity Planning
9
Finance
• Revenue Recognition for 1.0 – Issue first noticed on Feb 13th 2023
• Revenue Recognition – Bulk testing not started
•Resources, Collaboration & Priorities
EBS SME / Support – Hiring done( Onboarding April 24th )
•Sales Commitment & Comfort level for Bulk
10. News Team Agile Capacity Planning
10
Agile Capacity Planning is as simple as 1-2-3.
1. Determine your team average sprint
velocity (looking via JIRA Velocity Chart).
2. Determine your team quarterly capacity
(via Story Points) including removing 20%
to account for unknowns.
3. Determine your quarterly workload story
points (taking into consideration the
following T-Shirt Sizes to Story Points |
News Team uses the mid point of Story
Points listed):
14. News Team Agile Capacity Planning
Once your team reaches 80% Consensus Confidence Level, your
workload can be committed to and your capacity planning is done.
14
15. News Team Agile Capacity Planning - Example
• For example, for 5.6 PI Planning, News Team knew our quarterly
capacity and measured our T-Shirt Sizes into Story Points. We
determined our team quarterly capacity vs our quarterly workload
story points as measured here (the template will automatically
recommend if you should increase demand or increase capacity):
15
16. News Team Agile Capacity Planning - Example
• We had 5 Members and when doing the Fist of Five Voting News
Team needed a 4.0 or higher final vote from the following
options:
16
19. Agile Capacity Planning Appendix
On Page 6, Velocity Chart Velocity Chart
On Page 7, Engineering T-Shirt Sizing Engineering T-Shirt Sizing
On Page 11, Capacity Planning Template
NT&ARM-Capacity-Planning-Template_Google-Sheet.xlsx
On Page 12, "Fist of Five Voting"
Cast your vote using fist of five tool at Agilebin.com
Fist of Five Manual Process
19
