A defined process for project post mortem review

@article{Collier1996ADP,
  title={A defined process for project post mortem review},
  author={Bonnie Collier and Tom DeMarco and Peter Fearey},
  journal={IEEE Software},
  year={1996},
  volume={13},
  pages={65-72}
}
Most of us pay lip service to the need for software project post mortems, but the literature offers little guidance on how to conduct them. The authors propose a tentative, standard process for conducting post mortem reviews and describe activities, roles, and artifacts of the process. The success of the post mortem-or of any learning process-demands a context that makes organizational learning possible. Management must make an honest and sincere commitment to establish this context. This… 

Figures from this paper

A Review of Small and Large Post-Mortem Analysis Methods

It is concluded from the findings that PMA is worthwhile in small and medium-sized software development projects for which lightweight versions of PMA can be tailored.

Information systems project post-mortems: Insights from an attribution perspective

Information systems (IS) project failure is a costly and common problem. This is despite advances in development tools and technologies. In this article, we argue that one reason for this is the

Organizational Learning through Post-project Reviews in R&D

Post-project reviews are one opportunity to systematically improve performance in subsequent projects. However, a survey reveals that only one out of five RD process-related factors such as project

The post mortem paradox: a Delphi study of IT specialist perceptions

It is argued that the PME literature has underestimated the limits to learning in most IT organizations and paradoxical thinking is proposed to explore to help researchers frame continued inquiry into PME and to help managers overcome learning dysfunctions as they push for more widespread use of PMEs.

Experiences with conducting project postmortems: reports versus stories

This article will discuss how postmortems can be used to capture tacit experiences in projects, and compare two kinds of postmortem outcomes – traditional reports and stories.

Project Management Assurance

CIOs are increasingly held responsible for generating a positive return on IT project investment. As a result, there is great interest for devising ways to assure successful project outcomes. By

Establishing a project management office for a more effective and efficient implementation of projects in JKR

Effective and efficient implementation of projects is crucial in sustaining the trust of the government and public onto JKR as the main projects implementer. Despite having the advantages of

Project reviews: The vehicle for learning in organisations

Project reviews are an essential process of learning new things and capturing what has been learned in a project. This is done in order for future projects to benefit from this knowledge. A study
...

References

SHOWING 1-10 OF 22 REFERENCES

Post implementation evaluation of computer-based information systems: current practices

This study suggests that in practice, the primary reason for post implementation evaluations seems to be project closure and not project improvement.

201 Principles of Software Development

The principles contained in this volume are all valid, and they can all be used to improve software engineering, but it may be impossible to apply some combinations of them on any one project.

Managing New Product and Process Development: Text and Cases

Argues that a company's capability to conceive and design quality prototypes and bring a variety of products to market more quickly than its competitors is increasingly the focal point of

History and Failure

Engineering is a profession focused on the future, looking back mainly to calibrate progress; engineers are typical? ly drafting plans for the next generation of artifacts, seeking to achieve what

Management-aided software engineering

Two veteran software managers examine some of today's management best practices for signs of what might become generally accepted practice in the near future and envision how software management might mature over the next few decades to produce a new generation of best practices.

Product Development Consulting

  • Product Development Consulting
  • 1992

Him to ,VGa.sure m d Improve Ci~.stu/r/erSuti~nctzun: Attitude Scule.s, Quality . A h Inst

  • Him to ,VGa.sure m d Improve Ci~.stu/r/erSuti~nctzun: Attitude Scule.s, Quality . A h Inst
  • 1993

Post hnplementntion Evaluation of C:ornpixer-Rascd Information Sy\temi: Current Practices, " Cumm. AC.1.1, Fcb

  • Management Aided Software Enginccring IEEE SO$LZWT
  • 1904