Posted By Ian Mitchell on 15 Dec 2013 04:55 AM
> what about simple items that takes a long time
That's the problem with estimating by complexity. Mundane tasks may not be complex, but they can absorb much of a Sprint. Why not estimate by effort instead?
There are 2 reasons which I can think of right now:
1) effort is a relative word. For a senior developer it may take 8hrs while for another less experience developer it can take up to 16hrs or more. The moment we start using effort (time) the estimation process takes a much longer time because they want to get more exact.
2) when the client figure out effort is equal to time, deadlines will be created and before you know it, were doing Scrum in a waterfall environment. I want to keep a strict line between "how long will it take" and "how complex is this gonna be"