5 ms·
This reminds me of an obvious-yet-not-that-obvious trick when it comes to quoting for new features using an unknown technology: Be honest, ask to sacrifice a c
by mootothemax 14y ago
This reminds me of an obvious-yet-not-that-obvious trick when it comes to quoting for new features using an unknown technology:
Be honest, ask to sacrifice a couple of hours to throw at a proof-of-concept, and then you should have a better idea of how long the full feature will take to implement.
- praptak 14y agoIn my experience this applies to every feature. Doing a small chunk tends to improve estimates - somehow they tend to go up rather than down, go figure :-) This creates a sort of an impedance mismatch if you do your work in sprints - it's good to do the initial chunk in one sprint and the actual body of work in the next one. Unfortunately this means that features' implementation latency goes up.
- mootothemax 14y agoIn my experience this applies to every feature. Heh, I think it depends on the feature ;) Past the first few projects, you should have a pretty good feel for how long standard CRUD, user auth, email fun and other such things should take. Basically, the more experience you have, the fewer times you should need to sacrifice time for proof-of-concepts - but there'll always be a need for them :)
- praptak 14y agoWell yes, I meant "every feature" for some values of "every", obviously :-) For some features the gain is not noticeable enough to justify doing the initial spike.