28 ms·
Will Wright had a quote on this … if you don’t have any constraints you are just playing. That said, however, The problem I run into during practice is depende
by pylua 4y ago
Will Wright had a quote on this … if you don’t have any constraints you are just playing.
That said, however, The problem I run into during practice is dependencies— people want estimates to integrate into systems you have never heard of or used before. Not only that, there is no in place architecture or design before estimation. Imagine a construction company estimating a house without knowing how big it is or without having blueprints.
Often times software development is designing and architecting the system — not just implementing it. And that is the expensive part.
- mewpmewp2 4y agoThen you communicate! Say that the estimation can depend on the complexity of the system. I would think worst case is when the system has these A, B problems, then it would take N time. Otherwise best case it could take M time. If we want more accurate idea, we can spend O time on it to figure out what it could be.
- pylua 4y agoI would say this is being negligent if it is generalized. Often times architecting a system involves meetings with multiple parties — stake holders , legal counsels, and months or years of planning ahead to give a proper estimate for a large system. Time and materials is the right way to do this. However I can see this working in a very small scenario.