Practical project management: restoring quality to DP projects and systems
Practical project management: restoring quality to DP projects and systems
Post implementation evaluation of computer-based information systems: current practices
Communications of the ACM
201 principles of software development
201 principles of software development
Communications of the ACM
Changing Your Endgame Strategy
IEEE Software
Management-Aided Software Engineering
IEEE Software
Software Process Improvement in Web Time
IEEE Software
The Nine Deadly sins of Project Planning
IEEE Software
Postmortem: Never Leave a Project without It
IEEE Software
Augmenting Experience Reports with Lightweight Postmortem Reviews
PROFES '01 Proceedings of the Third International Conference on Product Focused Software Process Improvement
Designing process-based software curriculum
CSEET '97 Proceedings of the 10th Conference on Software Engineering Education and Training
Gaining knowledge from post-mortem analyses to eliminate electronic commerce project abandonment
E-commerce and cultural values
A study to investigate the impact of requirements instability on software defects
ACM SIGSOFT Software Engineering Notes
Evidence-Based Software Engineering for Practitioners
IEEE Software
Information and Software Technology
Software maintenance seen as a knowledge management issue
Information and Software Technology
Towards governance schemes for distributed software development projects
Proceedings of the 1st international workshop on Software development governance
SIGITE '08 Proceedings of the 9th ACM SIGITE conference on Information technology education
Postmortem reviews: purpose and approaches in software engineering
Information and Software Technology
Application of traditional software testing methodologies to web accessibility
Proceedings of the 2010 International Cross Disciplinary Conference on Web Accessibility (W4A)
Journal of Systems and Software
An approach for virtual organisations' dissolution
COIN'09 Proceedings of the 5th international conference on Coordination, organizations, institutions, and norms in agent systems
Software project effort assessment
Journal of Software Maintenance and Evolution: Research and Practice
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Project management offices: A case of knowledge-based archetypes
International Journal of Information Management: The Journal for Information Professionals
Timeboxing: a process model for iterative software development
Journal of Systems and Software
Proceedings of the 12th International Conference on Knowledge Management and Knowledge Technologies
Building Resilience in Large High-Technology Projects: Front End Conditioning for Success
International Journal of Information Technology Project Management
Perceived causes of software project failures - An analysis of their relationships
Information and Software Technology
Hi-index | 0.00 |
Conventional wisdom in the software industry decrees that it's good practice to conduct a postmortem study at the end of each project. Some would even suggest that this is not just a useful undertaking, but one of the fundamental principles of successful software development. The rationale authors most often cite for postmortem analysis is that only by analyzing our shortcomings can we learn to do better.We must begin by cataloguing such failures and learning from their patterns. The success of the postmortem-or of any learning process-demands a context that makes organizational learning possible. Participants are empowered when they know that each issue raised during the postmortem process must be added to the risk database and evaluated methodically on each subsequent project.