Logging project failures

I've been to project washup meetings. Failures catalogued, noted, sighed over. What to do with the results? We were quite confident that the new project manager wouldn't read them, would never believe he/she would make the same mistakes etc, so the faith in the output of the review was minimal.

Mark paints the same ideas with a different brush. The inspiration was a site logging climbing accidents, the logic being clear. You aren't daft enough to do this.... are you? Applying the same logic to a design methodology (SCRUM in this case) seems a logical step. Making it a wiki even better. Add your own horror stories. Nice one Mark. Bill calls it a blackbook. Adept naming? The Kaizen way is the neat adjunct here. Perhaps that's the bottom line. Why review mistakes if you aren't going to learn from them?