Version 5.0 of the QSM's Function Point Gearing Factor table is live!

The Function Point Gearing Factor table provides average, median, minimum, and maximum gearing factors for recently completed function point projects. A gearing factor is the average number of basic work units in your chosen function unit. Originally, it was designed to be used as a common reference point for comparing different sizing metrics by mapping them to the smallest sizing unit common to all software projects. QSM recommends that organizations collect both code counts and final function point counts for completed software projects and use this data for estimates. Where there is no completed project data available for estimation, we provide customers with a starting point to help them choose an appropriate gearing factor for their chosen programming language.

For this version of the table, we looked at 2192 recently completed function point projects out of the 10,000+ in QSM's historical database. The sample included 126 different languages, 37 of which had enough data to be included in the table. Interestingly, this year we added three new languages: Brio, Cognos Impromptu Scripts, and Cross Systems Products (CSP).

One trend we noticed is that, in general, the range for gearing factors has decreased over time. Similarly, the average and median values have decreased, which we attribute to having more data to work with.

Read the full press release or visit the new table!

While doing research on projects counted in function points, the sample size was large enough (over 2000 projects) to allow me to compare the productivity of different project types.  The QSM database uses these project categories:

• New Development (> 75% new functionality)
• Major Enhancement (25% - 75% new functionality)
• Minor Enhancement (5% - 25% new functionality)
• Conversion (< 5% new functionality)
• Maintenance

I calculated the normalized PI’s for projects in each development classification compared to the QSM Business trend lines.  The advantage of this is that it takes into consideration the impact of size and shows how the productivity of each project “application type” differs from the QSM Business IT average.  The datasets included medium and high confidence IT projects completed since 2000.  When I obtained the results, I went back over my selection process and calculations to make sure I hadn’t made a mistake.  The numbers were that surprising.  But, no, I hadn’t fat fingered anything (neither physically nor mentally).  Average productivity for conversion projects  was more than a standard deviation below the QSM Business IT average.

When I think about software projects, my memory goes back to the large ones I worked on when I was a developer.  These projects lasted for many months and usually had teams that were divided into sub-teams that worked on specific areas of functionality.  They typically created major systems for the customer.  But was that the normal life of a software developer?  Not really.  Years were spent on production support handling change requests, while the many small projects we completed are now only vague memories.

Recently, for some research I am doing on function points, I worked with a database of over 2000 recently completed software projects. As a byproduct of that research, I was able to come up with a portrait of the “average normal” Business IT project that I would like to share.

• The normal project is not new development.  In fact, only 16% of recently completed IT projects in the database were new development.
• 75% were either major or minor enhancements.
• Median project duration from the beginning of analysis until implementation was 7 months.
• Median effort was 22 person months (or 3520 hours at 160 hours per person month)
• Average staff (team size) just over 3 FTE people.
• Average size – 160 unadjusted function points.

If you were unable to attend our recent webinar, Using Function Points and SLIM to Support a Complete Estimation Process, a replay is now available.

How can project managers use their Function Point history to improve the way they estimate their projects? Leveraging historical data to generate and sanity check macro-level estimates early in the project lifecycle can save thousands of dollars in planning time and prevent signing up to unrealistic project schedules and budgets. Now that we've learned the basics of estimating before requirements, Keith Ciocco demonstrates how to use industry data and Function Point history with the SLIM Suite of Tools for a more mature estimation process. 

As Vice President of QSM, Keith has more than 25 years of experience working in sales and customer service, with 17 of those years spent at QSM. Keith’s primary responsibilities include managing business development, existing client relations, customer retention and response. 

Watch the webinar replay!

On Thursday, June 28 at 1:00 PM EDT, QSM's Keith Ciocco will present Using Function Points and SLIM to Support a Complete Estimation Process.

How can project managers use their Function Point history to improve the way they estimate their projects? Leveraging historical data to generate and sanity check macro-level estimates early in the project lifecycle can save thousands of dollars in planning time and prevent signing up to unrealistic project schedules and budgets. Now that we've learned the basics of estimating before requirements, Keith Ciocco demonstrates how to use industry data and Function Point history with the SLIM Suite of Tools for a more mature estimation process. 

As Vice President of QSM, Keith has more than 25 years of experience working in sales and customer service, with 17 of those years spent at QSM. Keith’s primary responsibilities include managing business development, existing client relations, customer retention and response. 

Watch the replay of this webinar!

Our recent webinar, Estimating Before Requirements with Function Points and Other Metrics, was a huge success! If you were unable to attend, a replay and pdf version of the slides are now available. If you have any questions regarding this material or QSM's Function Point Analysis services, please do not hesitate to contact us.

It is well known that project estimating based on parametric models has reached a sophistication where realistic estimates, schedules and predictable outcomes are indeed possible given a set of software and systems requirements. However, increasingly with the fast pace of Agile and other development methods is the requirement for estimates much earlier in the life cycle. What happens when project estimating moves back a full phase – before requirements, and acquisition managers, contractors, auditors and financial analysts are forced to develop and analyze estimates based on unknown requirements? Presented by industry expert Carol Dekkers, this presentation examines how to identify and document assumptions, create a logical and traceable project map including locations of potential “landmines” (calculated risks) that accompany this preliminary estimating. Experienced estimating professionals and contract managers will find a basis for common ground in this presentation – as the advice presented will create the basis for dialog and discussion of early estimates.

Watch the full replay here!

On Thursday, June 7 at 1:00 PM EDT, QSM will host Estimating Before Requirements with Function Points and other Metrics, presented by industry expert Carol Dekkers.

It is well known that project estimating based on parametric models has reached a sophistication where realistic estimates, schedules and predictable outcomes are indeed possible given a set of software and systems requirements.  However, increasingly with the fast pace of Agile and other development methods is the requirement for estimates much earlier in the life cycle. What happens when project estimating moves back a full phase – before requirements, and acquisition managers, contractors, auditors and financial analysts are forced to develop and analyze estimates based on unknown requirements?  Presented by industry expert Carol Dekkers, this presentation examines how to identify and document assumptions, create a logical and traceable project map including locations of potential “landmines” (calculated risks) that accompany this preliminary estimating.  Experienced estimating professionals and contract managers will find a basis for common ground in this presentation – as the advice presented will create the basis for dialog and discussion of early estimates.

Please welcome Carol Dekkers who joins QSM as a part-time Consultant and Trainer. Carol will be a member of our consulting team and also assisting as needed with our research and training needs. Carol has been a longtime teaming partner of QSM and those of us who have worked with her know that she is an excellent speaker, writer, trainer and consultant.  

Carol is a recognized international expert in the software metrics and IT Project Management industries. A former President of the International Function Point Users Group (IFPUG), Carol has been project editor of the U.S. delegation to ISO software and systems engineering standards in function points and benchmarking (ISO/IEC JTC1 SC7) since 1994.