Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
New Challenges to the King of Project Sizing
In the arena of software development measurement, one of the single most critical components to good measurement is effectively determining the size of a given project. Knowing the size of a given development project allows the IT organization to measure how productive the project was based on the relationship between the project’s size and the number of hours worked, number of dollars spent, and so forth for that given project.
Measurement groups can use any number of approaches, which could include counting the lines of code delivered or the number of use cases delivered by the project. In measurement circles, though, the function point has been the unofficial king of project sizing methods for some time. Years after its introduction, though, this measurement bellwether is seeing new challenges to its reputation as the most relevant and effective method for project sizing.
Developed in 1979 by Allan Albrecht of IBM, the function point counting technique was created to quantify the functions delivered by a software project from the perspective of the software user. One of the key differentiators that had made Albrecht’s technique superior to others, like counting the lines of code developed (LOC), was that the method allowed sizing comparisons between different projects to be made that were independent of the platform or programming languages …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"The best way to become boring is to say everything." - Voltaire |