Each line on the

graph represents a
different kind of
resource. As you add
projects, the number
of people you have Quick and Dirty
vs. the amount of
work they have to
do will change. By Capacity Tool
playing with the
settings on this
page, you can
answer the following
If any of your resources go above the capacity line,
questions: you'll be requiring them to work overtime during those periods.
How many
resources do I really
MOVE your projects need to get all of
these projects done?
Business
Analysts
back and forth What happens if one Developers

through time with the

of my projects is Testers
late by a week?
Capacity
slider buttons. What happens if I
lose someone mid-
project?

Play with it and see

You can also what happens!
change the project Capacity Table Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12
durations (in
Business Analysts 16.00 28.00 10.00 32.00 14.00 14.00 26.00 10.00 14.00 6.00 4.00 4.00
weeks), and the
Developers 0.00 0.00 28.00 24.00 24.00 34.00 34.00 6.00 56.00 34.00 6.00 6.00
number of each
type of resource Testers 2.00 2.00 2.00 18.00 10.00 16.00 22.00 32.00 40.00 14.00 24.00 24.00
needed on the Capacity 48 48 48 48 48 48 48 48 48 48 48 48
project.

Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12
Project Duration Resource Qty. Needed Phase x x x x x
Project 1 5 Business Analysts 2 Requirements x
Developers 2 Design x
Testers 1 Build x
Test x x
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12
Project Duration Resource Qty. Needed Phase x x x x x x
Project 2 6 Business Analysts 3 Requirements x
Developers 2 Design x x
Testers 1 Build x x
Test x x
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12
Project Duration Resource Qty. Needed Phase x x x x x x
Project 3 6 Business Analysts 2 Requirements x
Developers 3 Design x x
Testers 4 Build x x
Test x x
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12
Project Duration Resource Qty. Needed Phase x x x
Project 4 3 Business Analysts 1 Requirements
Developers 2 Design x
Testers 1 Build x
Test x
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12
Project Duration Resource Qty. Needed Phase x x x x x x
Project 5 6 Business Analysts 2 Requirements x
Developers 3 Design x x
Testers 3 Build x x
Test x x

Mockup for Capacity Modeling. Not actual customer data. Workbook freely available for use.
 Use this page to set the
assumptions for your
project capacity view.
These don't have to be
exact. Just enough for you
to get a gauge on how your

Assumptions: projects will likely interact

as they slide over top of
one another.
All projects follow a standard SDLC waterfall methodology.

The requirements phase mak 25% of the duration of a project and is composed of:

Business Analysts who ### of a business day, 8 hours per day

Testers who work 25% of a business day, 2 hours per day

The design phase makes up 15% of the duration of a project and is composed of:

Business Analysts who 25% of a business day, 2 hours per day

Developers who work 75% of a business day, 6 hours per day

The build phase makes up 20% of the duration of a project and is composed of:

Business Analysts who 25% of a business day, 2 hours per day

Developers who work ### of a business day, 8 hours per day

The test phase makes up 40% of the duration of a project and is composed of:

Business Analysts who 25% of a business day, 2 hours per day

Developers who work 25% of a business day, 2 hours per day
Testers who work ### of a business day, 8 hours per day

For a total of 100% of the project.

There are 2 Business Analysts each with a capaci8 hours per dafor a capacity
### hours.
2 Developers each with a capaci8 hours per dafor a capacity
### hours.
2 Testers each with a capaci8 hours per dafor a capacity
### hours.

Mockup for Capacity Modeling. Not actual customer data. Workbook freely available for use.