|
|
|
|
|
by FireBeyond
3154 days ago
|
|
> they rewrote "20 man years of software in 4 weeks". Which is absolutely incredible ... if accurate, if bug-free (for varying reasonable values of same). Otherwise the mythical man-month seems to creep in. That's a project that's complicated enough to require 240 developers (12 months x 20 years, fitted into 1 month), yet somehow was reliably chunked up, retrofitted into their supplier screw up, tested and deployed in 4 weeks?? I'm considering myself skeptical. |
|
Seriously though, you can probably redo a typical 20 Man Year project in 2, given how much of the development process is usually taken up by missed requirements and re-work, IF you have a bombproof specification and a well-drilled team of stars.
The part I’m not quite getting though is how a battery software issue impacted on wider productivity? Couldn’t they get them in-place and then patch the software after the fact?