One "rule" I've heard a few times for estimating software schedules is "take your estimate, double it, and then shift to the next unit of time". For example:

2 hours → 4 days

(I've also heard "multiply by pi" so "2 days → 6.29 weeks)

Does that rule have a name? It seems like the sort of thing that should, and that should be listed on

@codesections I took a course in systems engineering, and they called this simply a "margin". It would come in several forms.... extra time for a project, extra RAM required for an application, extra strength for a steel beam, and so on.

@codesections Surely Hofstadter's law always applies:

"It always takes longer than you expect, even when you take into account Hofstadter's Law."

@codesections I knew "multiply by 4", with some explanation as "multiply by 2 'cause you thought about the 'happy path'. Then multiply by 2 again 'cause you forgot some rule."

I just multiplied by 4 and called it "The Scotty Rule" ('cause Kirk asks if he always multiplies things by 4 and he answers "Otherwise, how would I be known as a miracle worked?").

@juliobiason I second #TheScottyRule or #ScottyScheduling, which perhaps goes hand in hand with #TheBoimlerEffect from the new #StarTrekLowerDecks animation series, which «encourages crew members to take shortcuts, not blindly follow the rules, and build in "[ #bufferTime ]" whenever they deem fit.»

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.