3 ms·
It doesn't make a difference if you ask the coder, the secretary or some manager as long as they are allowed to give a ballpark estimate. That's easy. The probl
by maxxxxx 10y ago
It doesn't make a difference if you ask the coder, the secretary or some manager as long as they are allowed to give a ballpark estimate. That's easy. The problem starts once somebody doesn't accept that ballpark number and wants more precise data. Then you start pouring over velocity data and define the project architecture to a level you can't reasonably know at this stage.
The solution usually is to make up some stuff but tell people about some nonsense methodology you used. It works but it's just lying. It would be much better if management methodologies would be able to accept uncertainty. Agile was one way to do this but it has evolved into a micromanagement tool.
- vinceguidry 10y ago> The problem starts once somebody doesn't accept that ballpark number and wants more precise data. That's crappy management. If my boss did that to me, it's time for a closed-door meeting where we have a come-to-Jesus on how software development is conducted. If I can't show them the light, I start sending out resumes because my working relationship with my boss is trashed and life is only going to get more painful over time.