title: Scrum - When do you Estimate the Effort for Product Backlog Items?
body: <p>At which part of the Scrum process does your team make educated estimates as to the effort required to complete a given product backlog item?</p>
  
  <p>For example, say you have a product backlog item that says "The user will be able to supply their email address and receive an email with a link for resetting their password" scheduled for Sprint 1. </p>
  
  <p>Do you start the sprint with a very rough estimate and refine it? When does this "user story" turn into granular action items that a programmer can estimate in time? (ex: "Build web form with one text box and submit button" = 2 hours)</p>
  
  <p>Do you do the finer, more accurate, estimates before the sprint begins? At the beginning of the sprint? Or during the sprint whenever the designer/programmer finally bumps into the task?</p>