930
Task estimation (lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
[-] bleistift2@sopuli.xyz 78 points 2 days ago

Teach this to your manager: At the beginning of a task, uncertainty is highest. Under no circumstances should you give an estimate in ‘man-hours’. Even days is too precise. The first estimate should be in months or years (of course depending on the size of the project). Then, as your insight into the project grows, you refine that to months, then weeks, later days. A vague estimate with a lower and a higher bound is way more useful to your manager than a ridiculously ‘precise’ but highly speculative number.

This lesson was brought to you by either “Code Complete 2” or “Rapid Development” by Steve McConnel, and by my former manager who wanted projects estimated in minutes.

[-] SlopppyEngineer@lemmy.world 13 points 2 days ago* (last edited 2 days ago)

I usually say what unit of measurement we're counting in: days, weeks or months. For more detail, more specs are needed.

[-] AngryCommieKender@lemmy.world 3 points 1 day ago

The project will be completed by Stardate -287289.4717465754

load more comments (7 replies)
this post was submitted on 16 Sep 2024
930 points (99.2% liked)

Programmer Humor

19180 readers
953 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS