Experiences with conducting project postmortems: Reports vs. stories and practitioner perspective

Kevin C. Desouza, Torgeir Dingsøyr, Yukika Awazu

Research output: Chapter in Book/Report/Conference proceedingConference contribution

13 Citations (Scopus)

Abstract

The most popular unit of work in organizations is a project. Managing knowledge in and about projects is salient for successful project management. Explicit knowledge is easier to manage than tacit knowledge as it is an outcome of work. Tacit knowledge is abstract and is managed in a cursory mode in projects. In this paper, we will discuss how postmortems can be used to capture tacit experiences in projects. Conducting a postmortem, either after a milestone or at the end of a project, is salient in order to gauge what has been learnt, what were the main issues faced, and what can be used to improve the processes of work in the future. The conducting of postmortems aids in articulation of tacit experiences into explicit forms, this enables for experiences to be better re-used in the future. Re-using of postmortem findings depends heavily on the nature of the postmortem outcome. We will compare two kinds of postmortem outcomes - traditional reports and stories. Management must choose the right kind of postmortem report to calibrate depending on the project and learning outcomes. We also highlight lessons learnt from conducting postmortem reviews in several software organizations.

Original languageEnglish (US)
Title of host publicationProceedings of the Annual Hawaii International Conference on System Sciences
EditorsR.H. Spraque, Jr.
Pages233
Number of pages1
StatePublished - 2005
Externally publishedYes
Event38th Annual Hawaii International Conference on System Sciences - Big Island, HI, United States
Duration: Jan 3 2005Jan 6 2005

Other

Other38th Annual Hawaii International Conference on System Sciences
CountryUnited States
CityBig Island, HI
Period1/3/051/6/05

Fingerprint

Project management
Gages

ASJC Scopus subject areas

  • Engineering(all)

Cite this

Desouza, K. C., Dingsøyr, T., & Awazu, Y. (2005). Experiences with conducting project postmortems: Reports vs. stories and practitioner perspective. In R. H. Spraque, Jr. (Ed.), Proceedings of the Annual Hawaii International Conference on System Sciences (pp. 233)

Experiences with conducting project postmortems : Reports vs. stories and practitioner perspective. / Desouza, Kevin C.; Dingsøyr, Torgeir; Awazu, Yukika.

Proceedings of the Annual Hawaii International Conference on System Sciences. ed. / R.H. Spraque, Jr. 2005. p. 233.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Desouza, KC, Dingsøyr, T & Awazu, Y 2005, Experiences with conducting project postmortems: Reports vs. stories and practitioner perspective. in RH Spraque, Jr. (ed.), Proceedings of the Annual Hawaii International Conference on System Sciences. pp. 233, 38th Annual Hawaii International Conference on System Sciences, Big Island, HI, United States, 1/3/05.
Desouza KC, Dingsøyr T, Awazu Y. Experiences with conducting project postmortems: Reports vs. stories and practitioner perspective. In Spraque, Jr. RH, editor, Proceedings of the Annual Hawaii International Conference on System Sciences. 2005. p. 233
Desouza, Kevin C. ; Dingsøyr, Torgeir ; Awazu, Yukika. / Experiences with conducting project postmortems : Reports vs. stories and practitioner perspective. Proceedings of the Annual Hawaii International Conference on System Sciences. editor / R.H. Spraque, Jr. 2005. pp. 233
@inproceedings{060b3095a0314fe69999c312a5dfbd24,
title = "Experiences with conducting project postmortems: Reports vs. stories and practitioner perspective",
abstract = "The most popular unit of work in organizations is a project. Managing knowledge in and about projects is salient for successful project management. Explicit knowledge is easier to manage than tacit knowledge as it is an outcome of work. Tacit knowledge is abstract and is managed in a cursory mode in projects. In this paper, we will discuss how postmortems can be used to capture tacit experiences in projects. Conducting a postmortem, either after a milestone or at the end of a project, is salient in order to gauge what has been learnt, what were the main issues faced, and what can be used to improve the processes of work in the future. The conducting of postmortems aids in articulation of tacit experiences into explicit forms, this enables for experiences to be better re-used in the future. Re-using of postmortem findings depends heavily on the nature of the postmortem outcome. We will compare two kinds of postmortem outcomes - traditional reports and stories. Management must choose the right kind of postmortem report to calibrate depending on the project and learning outcomes. We also highlight lessons learnt from conducting postmortem reviews in several software organizations.",
author = "Desouza, {Kevin C.} and Torgeir Dings{\o}yr and Yukika Awazu",
year = "2005",
language = "English (US)",
pages = "233",
editor = "{Spraque, Jr.}, R.H.",
booktitle = "Proceedings of the Annual Hawaii International Conference on System Sciences",

}

TY - GEN

T1 - Experiences with conducting project postmortems

T2 - Reports vs. stories and practitioner perspective

AU - Desouza, Kevin C.

AU - Dingsøyr, Torgeir

AU - Awazu, Yukika

PY - 2005

Y1 - 2005

N2 - The most popular unit of work in organizations is a project. Managing knowledge in and about projects is salient for successful project management. Explicit knowledge is easier to manage than tacit knowledge as it is an outcome of work. Tacit knowledge is abstract and is managed in a cursory mode in projects. In this paper, we will discuss how postmortems can be used to capture tacit experiences in projects. Conducting a postmortem, either after a milestone or at the end of a project, is salient in order to gauge what has been learnt, what were the main issues faced, and what can be used to improve the processes of work in the future. The conducting of postmortems aids in articulation of tacit experiences into explicit forms, this enables for experiences to be better re-used in the future. Re-using of postmortem findings depends heavily on the nature of the postmortem outcome. We will compare two kinds of postmortem outcomes - traditional reports and stories. Management must choose the right kind of postmortem report to calibrate depending on the project and learning outcomes. We also highlight lessons learnt from conducting postmortem reviews in several software organizations.

AB - The most popular unit of work in organizations is a project. Managing knowledge in and about projects is salient for successful project management. Explicit knowledge is easier to manage than tacit knowledge as it is an outcome of work. Tacit knowledge is abstract and is managed in a cursory mode in projects. In this paper, we will discuss how postmortems can be used to capture tacit experiences in projects. Conducting a postmortem, either after a milestone or at the end of a project, is salient in order to gauge what has been learnt, what were the main issues faced, and what can be used to improve the processes of work in the future. The conducting of postmortems aids in articulation of tacit experiences into explicit forms, this enables for experiences to be better re-used in the future. Re-using of postmortem findings depends heavily on the nature of the postmortem outcome. We will compare two kinds of postmortem outcomes - traditional reports and stories. Management must choose the right kind of postmortem report to calibrate depending on the project and learning outcomes. We also highlight lessons learnt from conducting postmortem reviews in several software organizations.

UR - http://www.scopus.com/inward/record.url?scp=27544513216&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=27544513216&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:27544513216

SP - 233

BT - Proceedings of the Annual Hawaii International Conference on System Sciences

A2 - Spraque, Jr., R.H.

ER -