Project Duration

Project duration is the measure of the elapsed months that a project is completed in.
As with most aspects of the software development process, software duration has many influencing factors.

Functional Size and Duration Relationships

You can estimate project duration using your estimation of software size, your software development life cycle phase profile, (including overlap between phases and activities), staff availability and other factors.
For a "ball park" or indicative estimate of duration, several "rules of thumb" equations, or quick estimating techniques are available. Two are shown below.

Functional Size and Duration

Analysis of data from the ISBSG repository has produced a detailed set of equations that you can use to achieve indicative estimates of project duration. Here are three examples of duration estimates using the ISBSG equations:

For a project of 500 Function Points using the language only equation table:

Duration = FPSize
where Duration is in Calendar Months.
eg., for a project of 500 Function Points,
Duration = 7.93 calendar months.

Finding similar results drawn from two sets of data collected in entirely different ways, lends support to the notion that, in general, there is a predictable relationship between the functional size of a Program(s) and the duration of the project to produce the program(s).

Work Effort and Duration Relationship

An analysis of 662 projects in the ISBSG repository that reported their project duration, the following equation was produced:

You can create an Excel formula to use this equation: =SUM(0.38*(effort^0.37))

The above "rule of thumb" equations are useful as a first indication of possible project duration. Of course, other factors such as the availability of resources and the business environment, must always be kept in mind. These additional factors should be used to apply judgement before drawing conclusions from the values calculated using any of the equations above.

Team Size and Duration Relationship

Project Managers are often faced with the task of providing information about the likely size, cost and duration of a proposed project to assist with a business decision about the project's feasibility. As part of this task they often seek answers to the following questions:

• Is it practical, or possible, to deliver software of the estimated project size within the target time frame?
• What effect will the project team size have on productivity?
• If I have an available team size of 'n' people, what is the likely elapsed time for the project?

The ISBSG Special Analysis Report 'Team Size Impact on Project Delivery Rate" looks at the impact that both team size and software size have on productivity. The report provides data in tables and charts, and examples that you can use to produce more accurate estimates by taking into account the impact of team size and software size when you are estimating.   This report is available to purchase, or is available free when you become an ISBSG Web Subscriber.