How do you estimate the time needed to implement a user story? If it’s something you had done before you know how long it’ll take. But what about if it’s completely new to you? How much time do you reserve for ‘surprises’?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How do you estimate the time needed to implement a user story? If it’s something you had done before you know how long it’ll take. But what about if it’s completely new to you? How much time do you reserve for ‘surprises’?
A great technique for this is to break the story down to somewhat smaller tasks, and estimate them compared to each other (instead of absolutely). So you can say:
We’re better at estimating relative complexity than absolute complexity. Then you actually perform one of the tasks, and figure out how much ‘real time’ it takes you to implement 1 unit – now you can calculate all the tasks. You keep updating your estimates according to how you progress.
This technique is from Agile Estimating and Planning by Mike Cohn, which is a great book on the subject.