A guide to estimations.

1) don’t give an immediate answer. The first “timeframe” you give will be held against you and will result in overtime and working weekends.

2) think of a relevant piece of work and the time that took.

2.1) if it’s something you haven’t done before, add some adequate research time.

3) allow half a day of testing for every day of development.

4) add a day as buffer - this is good for on the fly bug fixes

5) calculate time

6) now give an educated estimate.

7) this should take you 5 seconds to get through mentally.

8) if scope creep occurs: goto:1

  • 2
    I find it takes me at least twice as long as I reckon it will, whilst a good friend of mine reckons it will take three times as long..
  • 3
    Book clean coder -> chapter estimation;
  • 2
    If you finish it quickly then that is new expectation
  • 1
    (minimal estimate + 4* estimate + maximal estimate)/6 = your estimate

    1/(maximal estimate - minimal estimate) = uncertainty

    dont be a fool, do it like the pros ;-)
  • 2
    @gnulinuxer4fun you have 2 values that need to be ascertained (min, max) before we can use that formula.
  • 1
    @C0D4 Go with values where you can say "If i manage to achieve that, Im a wizard"
Add Comment