Function Point Productivity Calculator
Measure how many hours each delivered function point actually took.
What this calculator does
Functional size is counted under IFPUG practice and divided into recorded effort. The person-month convention is the user's own; no standard working month is assumed.
Inputs and what they mean
- Function points delivered
- — Unadjusted function points counted for the delivered software..
- Effort spent
- — Person-hours actually recorded against the work..
- Hours in one person-month
- — The hours your organisation counts as one person-month. No standard value is assumed..
How to use it
- Enter your own figures — the calculator never fills in a rate, price or benchmark for you.
- Press Calculate to see the result.
- Read the formula, variables, assumptions and source below the result before you rely on it.
Formula
Hours per function point = Effort hours ÷ Function points; Function points per person-month = Function points ÷ (Effort hours ÷ Hours per person-month)
Worked example
480 function points delivered in 6,240 hours
Your own recorded effort and your own person-month convention; no industry delivery rate is supplied.
Reading the result
The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.
Limitations and assumptions
Results depend entirely on the figures you enter and are rounded for display. They are for general information and education, not professional advice.
Reference: International Function Point Users Group — Function Point Counting Practices
Last reviewed:
Common questions
Formula, source and verification
Delivery rate is recorded effort divided by counted functional size, expressed per function point and per person-month.
The question it answers: How many hours did each function point actually take us?
The formula
Hours per function point = Effort hours ÷ Function points; Function points per person-month = Function points ÷ (Effort hours ÷ Hours per person-month)
- FP — Function points delivered
- (FP). Unadjusted function points counted for the delivered software.
- H — Effort hours
- (h). Person-hours actually recorded against the work.
- h_m — Hours in one person-month
- (h). The hours the organisation counts as one person-month.
Units: Function points; hours; hours per function point.
What kind of calculation this is
Deterministic formula. The same inputs always give the same answer. The maths is fixed and does not depend on judgement.
Method
Functional size is counted under IFPUG practice and divided into recorded effort. The person-month convention is the user's own; no standard working month is assumed.
Assumptions built into the result
- Mathematical: The effort recorded covers exactly the work that produced the counted function points.
Figures this calculator will never guess for you
- No industry delivery rate, productivity figure, defect rate or cost per line is inserted.
- No optional component is filled in on the user's behalf.
Limitations
- Measures past delivery; it is not itself a forecast.
- Comparable only across projects counted the same way.
Source and version
- Standard or reference
- Function point analysis — delivery rate measures — International Function Point Users Group (IFPUG, Function Point Counting Practices Manual — functional size is counted independently of technology, and delivery rate is effort per unit of functional size.)
- Published source
- International Function Point Users Group — CPM 4.3.1 family
- Formula version
- Version 1
- Verification
- Reviewed against the cited source on
- How much weight the source carries
- Standards or government
- Applies to
- Currency
- The result is a ratio or index, so it does not depend on currency.
Related tools
Work out the hourly rate to charge a client so that target margin is met after overhead and non-billable time.
Find the true hourly cost of an employee once benefits, payroll cost and overhead are included.
Size a software application from its data and transaction functions before estimating effort or cost.
Estimate development effort, schedule and average team size for a software project of a known size.
Express cloud spend as a cost per customer, per transaction or per other business unit.
Set the rate used to apply manufacturing overhead to jobs for the coming period.