Skip to main content
The Workplace

Return to Question

deleted 109 characters in body
Source Link
Curious
Curious
  • 169
  • 1
  • 6
  • 18

Spoke with a potential client about delivering a computer vision app (making calculations deduced from human body pose joints, in addition to UI navigation work and refinements). I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?

Spoke with a potential client about delivering a computer vision app (making calculations deduced from human body pose joints, in addition to UI navigation work and refinements). I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?

Spoke with a potential client about delivering a computer vision app. I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?

Tweeted twitter.com/StackWorkplace/status/1523860624610144256
Mod Moved Comments To Chat
Became Hot Network Question
deleted 9 characters in body
Source Link
Curious
Curious
  • 169
  • 1
  • 6
  • 18

After speakingSpoke with a potential client about delivering a computer vision app (making calculations deduced from human body pose joints, in addition to UI navigation work and refinements). I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?

After speaking with a potential client about delivering a computer vision app (making calculations deduced from human body pose joints, in addition to UI navigation work and refinements). I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?

Spoke with a potential client about delivering a computer vision app (making calculations deduced from human body pose joints, in addition to UI navigation work and refinements). I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?

Source Link
Curious
Curious
  • 169
  • 1
  • 6
  • 18

How might I avoid significantly overestimating the time required to deliver a potential client's software project?

After speaking with a potential client about delivering a computer vision app (making calculations deduced from human body pose joints, in addition to UI navigation work and refinements). I estimated this would take one month, erring on the side of a conservative estimate to account for any complexities that might unexpectedly bubble up. However, I didn't realize just how conservative it was compared to another iOS engineer's estimate of 60-80 hours when he told me. He also said that a number of his contacts agreed that 60-80 hours sounds right.

How might I avoid such a discrepancy of 2-3x in the future, and potentially navigate situations like this?