Experiences with conducting project postmortems: Reports versus stories

Software Process Improvement and Practice

Volumn 10, Issue 2, 2005, Pages 203-215

  Desouza, Kevin C ^a   Dingsøyr, Torgeir ^b   Awazu, Yukika ^a  

^a Institute for Engaged Business Research   (United States)

^b SINTEF   (Norway)

Author keywords

Knowledge management; Narratives; Postmortem review; Project; Project management; Projects; Software engineering; Stories

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; COMPUTER PROGRAMMING LANGUAGES; COST BENEFIT ANALYSIS; KNOWLEDGE ENGINEERING; LEARNING SYSTEMS; SOCIETIES AND INSTITUTIONS;

KNOWLEDGE MANAGEMENT; NARRATIVES; POSTMORTEM REVIEW; PROJECT; PROJECTS; STORIES;

PROJECT MANAGEMENT;

EID: 20744444388     PISSN: 10774866     EISSN: None     Source Type: Journal    
DOI: 10.1002/spip.224     Document Type: Conference Paper

References (39)

1. Abdel-Hamid TK, Madnick SE. 1990. The elusive silver lining: how we fail to learn from software development failures. Sloan Management Review 32(1): 39-48.
2. Awazu Y, Desouza KC, Evaristo JR. 2004. Stopping runaway information technology projects. Business Horizons 47(1): 73-80.
3. Basili VR, Caldiera G, Rombach HD. 1994. The experience factory. In Encyclopedia of Software Engineering, Vol. 1, Marciniak JJ (ed.). John Wiley: New York, 469-476.
4. Baskerville R. 1999. Investigating information systems with action research. Communications of The Association for Information Systems 2:1-32.
5. Baskerville R. 2001. Conducting action research: high risk and high reward in theory and practice. In Qualitative Research in Information Systems, Trauth E (ed.). Idea Group Publishing: Hershey, PA, 192-218.
6. Baskerville R, Pries-Heje J. 1999. Grounded action research: a method for understanding it in practice. Accounting, Management and Information Technology 9: 1-23.
7. Baskerville R, Wood-Harper AT. 1996. A critical perspective on action research as a method for information systems research. Journal of Information Technology 11(3): 235-246.
8. Birk A, Dingsøyr T, Stålhane T. 2002. Postmortem: never leave a project without it. IEEE Software 3(19): 43-45.
9. Boland JR, Tenkasi R. 1995. Perspective making and perspective taking in communities of knowing. Organization Science 6(4): 350-372.
10. Brydon-Miller M, Greenwood D, Maguire P. 2003. Why action research. Action Research 1(1): 9-28.
11. Collier B, DeMarco T, Fearey P. 1996. A defined process for project post mortem review. IEEE Software 4(13): 65-72.
12. Cusumano MA. 2004. The Business of Software. The Free Press: New York.
13. Cusumano MA, Selby RW. 1995. Microsoft Secrets - How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People. The Free Press: New York.
14. Daft RL, Lengel RH. 1986. Organizational information requirements, media richness and structural design. Management Science 32(5): 554-571.
15. Damm D, Schindler M. 2002. Security issues of A knowledge medium for distributed project work. International Journal of Project Management 20: 37-47.
16. Davenport TH, Thomas RJ, Desouza KC. 2003. Reusing intellectual assets. Industrial Management 45(3): 12-17.
17. Denning S. 2000. The Springboard: How Storytelling Ignites Action in Knowledge-Era Organizations. Butterworth Heinemann: Boston, MA.
18. Desouza KC. 2003. Barriers to effective use of knowledge management systems in software engineering. Communications of the ACM 46(1): 99-101.
19. Desouza KC, Evaristo JR. 2004. Managing knowledge in distributed projects. Communications of the ACM 47(4): 87-91.
20. Desouza KC, Raider JJ, Davenport TH. 2003. Intellectual asset re-use in software development. Research Note, Institute for Strategic Change: Accenture.
21. DingsøyrT, Moe NB, Nytrø O. 2001. Augmenting experience reports with lightweight postmortem reviews. In Third International Conference on Product Focused Software Process Improvement, Lecture Notes in Computer Science, Vol. 2188, Bomarius F, Komi-Sirviö S (eds.). Springer-Verlag: Kaiserslautern, Germany, 167-181.
22. Greenwood DJ, Levin M. 1998. Introduction to Action Research. Sage Publications: California.
23. Kaye B, Jacobson B. 1999. True tales and tall tales - the power of organizational storytelling. Training and Development 53(3): 44-52.
24. Keil M, Flatto J. 1999. Information systems project escalation: a reinterpretation based on options theory. Accounting, Management and Information Technologies 9(2): 115-139.
25. Keil M, Robey D. 2001. Blowing the whistle on troubled software projects. Communications of the ACM 44(4): 87-93.
26. Keil M, Mixon R, Saarinen T, Tuunainen V. 1995. Understanding runaway IT projects: results from an International Research Program Based on escalation theory, Journal of Management Information Systems 11(3): 67-97.
27. Keil M, Tan BCY, Wei KK, Saarinen T, Tuunainen V, Wassenaar A. 2000. A cross-cultural study on escalation of commitment behavior in software projects. MIS Quarterly 24(2): 299-325.
28. Kerth N. 2001. Project Retrospectives: A Handbook for Team Reviews. Dorset House: New York.
29. Kumar K. 1990. Post implementation evaluation of computer-based information systems: current practices. Communication of the ACM 33(2): 203-212.
30. Lyytinen K, Robey D. 1999. Learning failure in information systems development. Information Systems Journal 9(2): 85-101.
31. Mitroff I, Kilmann RH. 1975. Stories managers tell: a new tool for organizational problem solving. Management Review 64:18-28.
32. Munson TN. 1962. The Essential Wisdom of George Santayana. Columbia University Press: New York.
33. Nonakal. 1991. Knowledge-creating company. Harvard Business Review 69(6): 96-104.
34. Polanyi M. 1967. The Tacit Dimension. Anchor Books: New York.
35. Power M, Bonifazi C, Desouza KC. 2004. Ten outsourcing traps to avoid. Journal of Business Strategy 25(2): 37-42.
36. Roth G, Kleiner A. 1999. Car Launch, The Human Side of Managing Change. Oxford University Press: New York.
37. Røyrvik E, Bygdås AL. 2004. Knowledge hyperstories and context-sensitive knowledge enabling. In Living Knowledge, The Dynamics of Professional Service Work, Carlsen K, von Krogh G (eds.). Palgrave Macmillan: UK, 184-203.
38. Rus I, Lindvall M. 2002. Knowledge management in software engineering. IEEE Software 19(3): 26-38.
39. Tiedeman MJ. 1990. Post-mortems - methodology and experiences. IEEE Journal of on Selected Areas in Communications 8(2): 176-180.