3 ms·
Not sure I agree about fixed price point. When I'm spending 90% of the time developing software, especially if that's a stand-alone or well specified isolated
by Const-me 7y ago
Not sure I agree about fixed price point.
When I'm spending 90% of the time developing software, especially if that's a stand-alone or well specified isolated components - I can quote after some initial research, and I agree it's a good way to go.
For other clients I'm doing a job of technical lead. In that case, too much time is spent defining requirements, reviewing other people's work, writing project documentation, etc. These things are borderline impossible to estimate in advance. For these projects, I prefer hourly contracts.
- chiefalchemist 7y agoScrum is more or less a time & materials approach. Agreed. If it's small and finite - similar to an oil change - then a fixed price is doable. On the other, if the resuest is "the engine sounds odd and acceleration is off" then it could be anything. Anyone who is the latter but expects a fixed price must be avoided. They'll cost you more than you'll make.