This has been an issue for some agile proponents who say that you can add staff to an agile project without penalty. In other words, you could not take a project that was estimated for 10 people for 12 months and run it with 20 people for 6 months. COCOMO explained why projects could only be compressed so much and that you could not trade staff months for staff level. These numbers were very tricky because they would change based on the size and staffing level of the project. They knew that if their team members could produce 500 SLOC per month across the life cycle, then they would be writing 1,000 SLOC during the coding phase. They felt they knew how many SLOC the members of their team would produce across the life of the project. At that time, project managers normally estimated based on SLOC.
#Cocomo model ii does it work? driver#
The thing that they all have in common is that source lines of code (SLOC) is the primary driver for the model. There were really two variations of Intermediate COCOMO. There was Basic, Intermediate and Detailed versions. In any case, COCOMO 81 was really a family of models. Others called it COCOMO 81, after the year that it was published. Obviously, some people referred to this first release as COCOMO I. When COCOMO II was released, there had to be a way to distinguish between the two of them. When it was developed, the first version of the Constructive Cost Model (COCOMO) was simply called COCOMO. The diagram specifies COCOMO i because it might be either COCOMO I, COCOMO II or COCOMO III. In this diagram, we have specified that COCOMO and CORADMO were the models that should be used.
#Cocomo model ii does it work? drivers#
In the original diagram, it was specified that the both traditional and agile cost drivers were applied.
This size is the primary driver to a mathematical model that will generate the project effort and schedule. As a brief review, the development environment is applied to the consumer product size, made up of both estimated function points and enriched SNAP points, to arrive at the producer product size. The diagram above looks like the bottom of the one in Overview of Semi-Classical Estimating.