|
Release 2 Recalibration |
According to the PSP forms submitted for stage 2, A Fetter team member can produce roughly 9 LOC / hour. With 5 active coders on the team and a maximum of 8 hours allocated per week for coding, Team Fetter can produce
(5 active coders) * (9 LOC / hour) * (8 hour / week) = 360 LOC / week
According to the integration plan, 164 LOC are planned to be completed for Week 8 (Feb 26 - Mar 4). As of Feb 26, the integration plan does not currently include the new modules that need to be coded to implement our approved change proposals. But after reviewing the impact of the approved proposals, it has been learned that relatively little new code will be added. What I consider to be a very safe estimate of the number of new LOC to be added as a result of the change proposals is 150 LOC (which also takes into account the team's trend of having the actual LOC produced per week be larger than that planned), so a total of 310 new LOC are planned to be added by the end of the project.
As of Feb 26, there are 8 days left until Mar 6, the day all features are planned to be completely coded. Coding at the maximum of 8 hours / week, Team Fetter can produce a total of
(360 LOC / week) * (8 days / 7 days / 1 week) = 411 LOC, which is well above the number planned to be needed by the end of the project. Rescheduling the end of coding from for Mar 1 to Mar 6 would require a Fetter team member to put in about
(8 coding hours / week) * (310 LOC / 411 LOC) = 6 hours of coding per week,
which should hopefully leave enough time in the week to fix assigned defects found by the tester.