Accounting for: - time spent debugging/errors - unforeseen interrupting work - wanting to deliver quickly but not set up unrealistic expectations
Whatever you think x1.5/2
āIt will be done when itās doneā
Wow, the way things get done in G
^Isnt that always better than just 3xing and sit on your hands 1/2 of the time?
My rule of thumb is to guess then multiply x3. After that create a detailed list of stuff that fits the estimate.
1. Have well defined requirements 2. Have a comprehensive knowledge of existing product as to understand any āgotchasā/design rework 3. Have an understanding of what is involved in implementation 4. Understand the complexities of testing/validation If you donāt know all of the above itās best to plan for a small investigative task to document the above before giving any reliable estimation Then double your estimation.