Ben Bradley wrote:
>
> The big company I worked for at the time sent me to a week-long
> "Software Engineering Training Program" while in the middle of a
> longish project. I recall it being a mostly "positive learning
> experience" but the only thing I now (10 years later) remember from it
> was "Do a post-mortem on the project." When you get done with a
> project (whether it's shipping or it was trashed), you (meaning the
> whole team) look it over (perhaps not so much the design itself but
> rather how you did it), see what you did right and what went wrong,
> what you could have done better, etc. The point of this is that you
> might have better insight at the start of the next project, rather
> than at the end of it.
> Of course, at the end of the project I was working on, we did NOT
> do a post-mortem.

Very common.

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.

My offer was ignored and I left the company 4 months later to
go to a job with about 5% less pay.

Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo [email protected] (Yes it's valid)
+-----------------------------------------------------------+
"Linux is produced to be used, whereas the others are produced
to be sold" -- Bobby D. Bryant