Changing Resources, Time and/or Features
We have all been on projects where management decides to change resources, time and/or features of an ongoing project. The old chestnut used to be these are the 3 things you have control over, pick 1.
Thinking about this I looked at what would need to happen if we changed one variable:
- If you reduced Resources then you would need more Time or less Features
- If you reduced Time then you would need more Resources or less Features
- If you increased Features then you would need more Time or more Resources
But thinking about this, changes in Resources usually make no difference in the short term. Adding another developer does very little until the developer comes up to speed. Depending on their expertise this can take a while. So, what if we treated Resources as a constant?
We end up with a relationship like: Resources = Features over Time (R = F/T). Sounds really pretty nice. Kind of makes sense. Can be looked at as a productivity measures, quality measure, etc… as well. Again you don’t expect the productivity of your team or their quality level to change much in the short term. Walking through the cases above we get relationships to still work.
I think this is a nice clear mathematical argument even the most demanding manager can understand. Oh, you want to increase Features this late in the project. That means we need more Time – see here… Yes, we can increase our productivity, but not in the short term (phase) of this project.
