Re: Best Practices to Manage Complexity in Hardward/Software Design?
Erik de Castro Lopo wrote:
(snip)
> I was involved in one of those hellish development projects that
> resembles a slow moving train wreck.
> The project was supposed to take 9 months but ended up taking over
> 2.5 years. Near the end, I offered to write a paper on what went
> wrong and how to avoid similar problems in future projects. I made
> it clear that I was not looking to blame anyone but I wanted the
> company and the development team to learn from the mistakes made.
Read "Mythical man-month", which pretty much has the same description,
though on a different scale.
It is written by the head of the OS/360 project. The examples relate
to software projects, but it should be more generally applicable.
-- glen
|