| Features, Schedule, Cost Well, schedule and cost at least have straightforward measurements. The issue then is features. Or is that it? The "pick two" model really is just the business view. Invariably you will also have: - adherence to process (ideally process would be an overall enhancement to productivity, but it usually becomes a net-negative) - maintenance costs (patching, libraries, language versions, database versions) - infrastructure churn and upkeep - random org shit: meetings, more meetings, training, certifications, HR, ticket walls, etc - documentation. Is that important? - ... are the requirements known? settled? at least ballparked? As I see here, invariably measuring developer productivity is of course blaming the victim: WHY AREN'T YOU MORE PRODUCTIVE, and of course shrugging away the nigh-unlimited ways an org can hamstring or frustrate a developer. |