The notion of a "post mortem" is familiar to most software developers and project managers: at the end of an application development project, a report is written to document the good, the bad, and the ugly experiences, so that future projects can learn and improve. In theory, it's a useful concept; in practice, it's largely ignored.
Advisor
Mini Post Mortems
By Ed Yourdon
Posted June 16, 1998 | Leadership | Amplify | Amplify | Amplify | Amplify
About The Author
Ed Yourdon was cofounder, with Karen Coburn, of Cutter Consortium. Ed served as Fellow of the Cutter Business Technology Council, and Founding Editor and Editor Emeritus of the Cutter IT Journal. He chaired Cutter's Summit for many years. Mr. Yourdon is widely known as the lead developer of the structured analysis/design methods of the 1970s. He was a codeveloper of the Yourdon/Whitehead method of object-oriented (OO) analysis/design and the… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.