3 ms·
When we run into stuff like that at work we budget a set number of hours to breaking the problem up into chunks, researching and prototyping the sticky parts, a
by knieveltech 11y ago
When we run into stuff like that at work we budget a set number of hours to breaking the problem up into chunks, researching and prototyping the sticky parts, and then using that information to put together a realistic estimate. We call it a "planning project".
- lifeisstillgood 11y agoThat's sensible - and is a way to lose bad clients (not itself a problem). I am not saying project mgmt does not work, I am saying the plan the task, do the task approach is not appropriate for software development, at a given level of granularity. If you ever watch Grand Designs, they start with a design, a plan, a schedule, and it all goes out the window ten minutes later. This is not that being on top of the process will not give you control, but that relying on estimates and plans as a means of control is worthless - and that's for something people have been doing for hundreds of years