Cocomo Calculator Finding Staffing From Effort

Staffing & Development Time Calculator

Basic COCOMO parameters for TDEV calculation.

Project Type	Constant ‘c’	Exponent ‘d’
Organic	2.5	0.38
Semi-detached	2.5	0.35
Embedded	2.5	0.32

What is a COCOMO Calculator for Finding Staffing from Effort?

A COCOMO calculator finding staffing from effort is a tool based on the Constructive Cost Model (COCOMO) that helps project managers and software developers estimate the average number of staff members required for a project and the likely development time, given a pre-calculated effort value in person-months (PM). It uses the effort estimate, which is often derived from the size of the software (e.g., Kilo Lines of Code – KLOC) and other cost drivers, to predict the schedule and average team size needed to complete the project.

This specific calculator focuses on the relationship between effort, development time (TDEV), and average staffing levels within the Basic COCOMO framework. It assumes you already have an effort estimate and want to determine the optimal schedule and the average team size you’ll need over that period.

Who Should Use It?

• Software Project Managers
• Development Team Leads
• Software Cost Estimators
• Students learning software engineering

Common Misconceptions

A common misconception is that you can drastically reduce the schedule by adding more people. The COCOMO model, particularly the TDEV formula, shows that the relationship is not linear; adding more people beyond a certain point yields diminishing returns on schedule reduction and can even become counterproductive (as described by Brooks’s Law).

COCOMO Staffing from Effort Formula and Mathematical Explanation

The core of this COCOMO calculator finding staffing from effort relies on two main formulas from the Basic COCOMO model, once effort (E) is known:

1. Development Time (TDEV): TDEV = c * (E)^d
2. Average Staffing (S): S = E / TDEV

Here’s a step-by-step explanation:

1. Effort (E): This is the input to our calculator, measured in Person-Months (PM). It represents the total amount of labor required to complete the project. It’s typically calculated earlier using E = a * (KLOC)^b * EAF (Effort Adjustment Factor), but for this calculator, we assume E is given.
2. Development Time (TDEV): The formula TDEV = c * (E)^d calculates the estimated time in calendar months from the start of design to the end of integration and test. The coefficients ‘c’ and ‘d’ depend on the project mode (Organic, Semi-detached, or Embedded), reflecting the project’s complexity and the development environment.
3. Average Staffing (S): Once Effort (E) and Development Time (TDEV) are known, the average number of full-time equivalent staff members (S) required throughout the development phase (excluding maintenance) is simply the total effort divided by the development time: S = E / TDEV.

Variables Table

Variables used in the COCOMO staffing from effort calculation.

Variable	Meaning	Unit	Typical Range/Values
E	Effort	Person-Months (PM)	1 to 1000s (depends on project size)
TDEV	Development Time	Months	Calculated based on E, c, d
S	Average Staffing	Persons	Calculated based on E, TDEV
c	TDEV Coefficient	Constant	2.5 (for Basic COCOMO)
d	TDEV Exponent	Constant	0.38 (Organic), 0.35 (Semi-detached), 0.32 (Embedded)

Practical Examples (Real-World Use Cases)

Example 1: Small Organic Project

A small, relatively straightforward project with an experienced team is estimated to require 50 Person-Months of effort. The project is classified as Organic.

• Effort (E) = 50 PM
• Project Type = Organic (c=2.5, d=0.38)
• TDEV = 2.5 * (50)^0.38 ≈ 2.5 * 4.498 ≈ 11.25 Months
• Average Staffing = 50 / 11.25 ≈ 4.44 Persons

This suggests an average team size of about 4-5 people over roughly 11 months.

Example 2: Large Embedded Project

A complex, large-scale embedded systems project has an estimated effort of 800 Person-Months. The project is classified as Embedded due to tight constraints and novel hardware/software interaction.

• Effort (E) = 800 PM
• Project Type = Embedded (c=2.5, d=0.32)
• TDEV = 2.5 * (800)^0.32 ≈ 2.5 * 7.568 ≈ 18.92 Months
• Average Staffing = 800 / 18.92 ≈ 42.28 Persons

This indicates a much larger average team of around 42 people working for about 19 months.

How to Use This COCOMO Calculator Finding Staffing from Effort

1. Enter Effort (E): Input the total estimated effort for your project in Person-Months into the “Effort (E)” field. This value usually comes from a previous COCOMO effort calculation based on project size and cost drivers.
2. Select Project Type: Choose the project type (Organic, Semi-detached, or Embedded) that best matches your project’s characteristics from the dropdown menu. This will determine the ‘c’ and ‘d’ parameters used for the TDEV calculation.
3. View Results: The calculator will automatically update and display:
   • Average Staffing (Persons): The primary result, showing the average number of people needed.
   • Development Time (TDEV): The estimated duration of the project in months.
   • The Effort and Project Type you entered, along with the ‘c’ and ‘d’ parameters used.
4. Analyze Chart: The bar chart visually represents the calculated TDEV and Average Staffing.
5. Reset: Use the “Reset” button to clear inputs and results to their default values.
6. Copy Results: Use the “Copy Results” button to copy the key outputs to your clipboard.

The results from this COCOMO calculator finding staffing from effort provide a baseline for project planning, helping you understand the trade-offs between schedule and team size for a given effort level.

Key Factors That Affect COCOMO Staffing Results

While this calculator uses Effort as the primary input, the factors that originally influenced the Effort estimate, and the model parameters, are crucial:

1. Accuracy of Effort Estimate: The staffing and TDEV results are directly derived from the input Effort. If the Effort estimate is inaccurate, the staffing and schedule will be too. Initial software effort estimation is critical.
2. Project Type Selection (c and d parameters): Choosing the correct project type (Organic, Semi-detached, Embedded) significantly impacts the TDEV and thus staffing. Misclassifying the project alters the c and d values used.
3. Project Size (KLOC): Although not a direct input here, the project size (often measured in Kilo Lines of Code) is usually the primary driver for the initial Effort calculation.
4. Cost Drivers (Effort Adjustment Factor – EAF): In a full COCOMO calculation, cost drivers (like personnel capability, product complexity, required reliability) modify the nominal effort. These indirectly affect the Effort value you input here.
5. Development Team Experience and Capability: Highly experienced teams might complete work faster than reflected in the standard Organic model, while less experienced teams might take longer, influencing the real-world fit of the model. Learn more about COCOMO II model basics.
6. Tool Support and Development Environment: A modern, supportive environment can reduce the actual effort needed compared to a limited environment, impacting the input effort.
7. Schedule Constraints: While COCOMO provides an optimal TDEV, external schedule pressures might force a deviation, which often comes at the cost of increased effort or risk, as detailed in project planning strategies.

Frequently Asked Questions (FAQ)

Q1: What is a “Person-Month”?

A1: A Person-Month (PM) is the amount of work one person can do in one month. It’s a standard unit for measuring software development effort.

Q2: Can I reduce the development time by adding more people?

A2: To some extent, yes, but not proportionally. The TDEV formula (with an exponent less than 1) shows diminishing returns. Adding too many people can even slow down the project due to increased communication overhead (Brooks’s Law).

Q3: How accurate is this COCOMO calculator finding staffing from effort?

A3: The accuracy depends heavily on the accuracy of the input effort estimate and how well the chosen project type fits your actual project. COCOMO provides estimates, and real-world projects can vary. It’s best used as a guide for initial planning.

Q4: What if my effort estimate is very rough?

A4: If your effort estimate is uncertain, consider running the calculator with a range of effort values (e.g., best-case, most-likely, worst-case) to see a range of possible staffing and schedule outcomes.

Q5: Does this calculator account for part-time staff?

A5: The “Average Staffing” result represents full-time equivalent persons. If you have part-time staff, you would need more individuals to make up the full-time equivalents.

Q6: Is this calculator based on Basic COCOMO or COCOMO II?

A6: This calculator uses the TDEV and Staffing formulas from Basic COCOMO, assuming effort is already known. It uses the parameters ‘c’ and ‘d’ from Basic COCOMO for the three modes.

Q7: What does “Organic”, “Semi-detached”, and “Embedded” mean?

A7: These are project modes in Basic COCOMO:

• Organic: Relatively small, simple projects, experienced team, familiar environment.
• Semi-detached: Intermediate size and complexity, mixed team experience, some unfamiliarity.
• Embedded: Complex projects, tight constraints (hardware, real-time), often innovative.

Our guide on COCOMO II model basics expands on these.

Q8: How do I get the initial Effort value?

A8: The Effort value is usually estimated based on project size (like KLOC), adjusted by various cost drivers using the full COCOMO effort equation, often with tools like our software effort estimation calculator or other methods.

Related Tools and Internal Resources