Proceedings <strong>of</strong> the 42nd Hawaii International Conference on System Sciences - 2009 7. Conclusion <strong>and</strong> further <strong>work</strong> In this paper, we have drawn upon a detailed study <strong>of</strong> a postmortem interview from a capstone SE student project to demonstrate the potential <strong>of</strong> project wikis to be used as a means for the recall <strong>of</strong>, <strong>and</strong> <strong>reflection</strong> on, a project process, thus making the project wikis already in use even more useful to the project teams. Some limitations to our research provide directions for further research. <strong>The</strong> interview forming the core <strong>of</strong> our empirical data was partially exploratory, <strong>and</strong> adequate for pointing out the potential for project wikis to aid in postmortem <strong>reflection</strong>. Our findings indicate how various types <strong>of</strong> information may be used to recall <strong>and</strong> reflect on various types <strong>of</strong> issues. However, we do not have sufficient data to reasonably generalize about the connections between the two. We suggest that wiki-aided postmortem reviews be conducted in other projects <strong>and</strong> the interaction <strong>and</strong> tool use <strong>of</strong> the participants during the sessions be analyzed. <strong>The</strong> interviews should follow a well founded design for a postmortem review <strong>and</strong> be video recorded. In this way it might be possible to identify what type <strong>of</strong> information in a project wiki promotes <strong>reflection</strong> in certain ways or on certain topics. Also, collective, toolmediated postmortem <strong>reflection</strong> should be investigated. Our wiki walkthrough tool needs to be evaluated through use in real projects to see if it is deemed useful by the project teams. <strong>The</strong> idea <strong>of</strong> utilizing history stored in a collaboration tool in <strong>reflection</strong> on the process is relevant to other tools. E.g., source code management <strong>and</strong> bug tracking tools contain a history <strong>of</strong> commented project artifact revisions. <strong>The</strong> student teams at our university increasingly prefer this type <strong>of</strong> tool (e.g. Trac) to manage their SE projects. A next step in our research is to conduct <strong>and</strong> evaluate postmortem reviews mediated by these tools to see if they, too, can help students learn from their SE project experience. 7. Acknowledgements Thanks to Monica Divitini, Arne Martin Aurlien, Håvard Håskjold <strong>and</strong> William Young. <strong>The</strong> research was funded by the MOTUS2 project at NTNU. 8. References [1] P. H. Carstensen <strong>and</strong> K. Schmidt, "<strong>Computer</strong> Supported Cooperative Work: New Challenges to Systems Design," in H<strong>and</strong>book <strong>of</strong> Human Factors/Ergonomics, K. Itoh, Ed. Tokyo: Asakura Publishing, 2002 (1999). [2] G. Fitzpatrick, W. J. Tolone, <strong>and</strong> S. M. Kaplan, "Work, Locales <strong>and</strong> Distributed Social Worlds," presented at CSCW, Stockholm, Sweden, 1995. [3] M. Keil, J. Mann, <strong>and</strong> A. Rai, "Why S<strong>of</strong>tware Projects Escalate: An Empirical Analysis <strong>and</strong> Test <strong>of</strong> Four <strong>The</strong>oretical Models," MIS Quarterly, vol. 24, 2000. [4] J. Dewey, Democracy <strong>and</strong> education. New York: <strong>The</strong> Free Press, 1997 (1916). [5] D. Schön, <strong>The</strong> Reflective Practitioner:Basic Books, 1983. [6] C. Argyris <strong>and</strong> D. Schön, Organizational Learning II. Reading, MA, USA: Addison Wesley, 1996. [7] P. Senge, <strong>The</strong> Fifth Discipline. London, United Kingdom: Doubleday, 1990. [8] E. Wenger, "Communities <strong>of</strong> practice <strong>and</strong> social <strong>learning</strong> systems," Organization, vol. 7, pp. 225-246, 2000. [9] P. C. Blumenfeld, E. Soloway, R. W. Marx, J. S. Krajcik, M. Guzdial, <strong>and</strong> A. Palinscar, "Motivating Project-Based Learning: Sustaining the Doing, Supporting the Learning," Educational Psychologist, vol. 26, pp. 369-398, 1991. [10] J. Dewey, How we think. A restatement <strong>of</strong> the relation <strong>of</strong> reflective thinking to the educative process (Revised edtn.) ed. Boston: D. C. Heath, 1933. [11] G. H. Mead, Mind, Self <strong>and</strong> Society. Chicago: <strong>The</strong> University <strong>of</strong> Chicago Press, 1934. [12] A. Strauss, Continual permutations <strong>of</strong> action. New York: Aldine de Gruyter, 1993. [13] P. Berger <strong>and</strong> T. Luckmann, <strong>The</strong> Social Construction <strong>of</strong> Reality. London: Penguin Books, 1966. [14] G. Fitzpatrick, <strong>The</strong> Locales Frame<strong>work</strong>: Underst<strong>and</strong>ing <strong>and</strong> Designing for Wicked Problems: Kluwer Academic Publishers, 2003. [15] J. Lave <strong>and</strong> E. Wenger, Situated Learning. Legitimate peripheral participation. Cambridge: University <strong>of</strong> Cambridge Press., 1991. [16] I. Sommerville, S<strong>of</strong>tware Engineering, Sixth Edition: Addison-Wesley, 2001. [17] E. J. Conklin <strong>and</strong> K. B. Yakemovic, "A Process- Oriented Approach to Design Rationale," Human-<strong>Computer</strong> Interaction, vol. 6, pp. 357-391, 1991. [18] A. H. Dutoit, R. McCall, I. Mistrik, <strong>and</strong> B. Paech, "Rationale Management in S<strong>of</strong>tware Engineering: Concepts <strong>and</strong> Techniques," in Rationale Management in S<strong>of</strong>tware Engineering, A. H. Dutoit, R. McCall, I. Mistrik, <strong>and</strong> B. Paech, Eds.: Springer, 2006. [19] T. Dingsøyr, "Postmortem reviews: purpose <strong>and</strong> approaches in s<strong>of</strong>tware engineering," Information <strong>and</strong> S<strong>of</strong>tware Technology, vol. 47, pp. 293-303, 2005. [20] B. Bygstad, B. Krogstie, <strong>and</strong> T.-M. Grønli, "Scaffolding Project Based Learning with the Rational Unified Process. Experience from 5 years <strong>of</strong> Student Projects in S<strong>of</strong>tware Engineering," presented at NOKOBIT, Norway, 2006. [21] V. Kasi, M. Keil, L. Mathiassen, <strong>and</strong> K. Pedersen, "<strong>The</strong> post mortem paradox: a Delphi study <strong>of</strong> IT specialist perceptions," EJIS, vol. 17, pp. 62-78, 2008. [22] B. R. Krogstie, "<strong>The</strong> wiki as an integrative tool in project <strong>work</strong>," presented at COOP, Carry-le-Rouet, Provence, France, 2008. [23] S. M. Smith <strong>and</strong> E. Vela, "Environmental contextdependent memory: A review <strong>and</strong> meta-analysis," Psychonomic Bulletin & Review, vol. 8, pp. 203-220, 2001. [24] "DokuWiki home page," vol. 2009. [25] E. Derby, D. Larsen, <strong>and</strong> K. Schwaber, Agile Retrospectives. Making Good Teams Great: Pragmatic Bookshelf, 2006. 10 Authorized licensed use limited to: Norges Teknisk-Naturvitenskapelige Universitet. Downloaded on February 5, 2010 at 09:00 from IEEE Xplore. Restrictions apply. 160
Research paper P6 Title: Shared timeline <strong>and</strong> individual experience: Supporting retrospective <strong>reflection</strong> in student s<strong>of</strong>tware engineering teams Authors: Birgit Krogstie <strong>and</strong> Monica Divitini Published in: Proceedings <strong>of</strong> CSEE&T 2009 Pages: 8 Complete reference: Krogstie, B. R. <strong>and</strong> M. Divitini (2009). Shared timeline <strong>and</strong> individual experience: Supporting retrospective <strong>reflection</strong> in student s<strong>of</strong>tware engineering teams. Conference on S<strong>of</strong>tware Engineering Education <strong>and</strong> Training (CSEE&T) 2009, Hyderabad, 17-19 Feb. IEEE <strong>Computer</strong> Society. 161
- Page 1 and 2:
Birgit Rognebakke Krogstie The work
- Page 3 and 4:
Figure 1: Most used terms in the th
- Page 5 and 6:
Abstract In project based learning,
- Page 7 and 8:
Preface This thesis is submitted to
- Page 9 and 10:
Acknowledgements I would like to th
- Page 11 and 12:
Contents 1 Introduction ...........
- Page 13 and 14:
Research paper P4 135 Research pape
- Page 15 and 16:
Figure 17: Support for learning in
- Page 17:
Abbreviations CSCL CSCW IS NITH NTN
- Page 20 and 21:
The work-reflection-learning cycle
- Page 22 and 23:
The work-reflection-learning cycle
- Page 24 and 25:
The work-reflection-learning cycle
- Page 26 and 27:
The work-reflection-learning cycle
- Page 28 and 29:
The work-reflection-learning cycle
- Page 30 and 31:
The work-reflection-learning cycle
- Page 32 and 33:
The work-reflection-learning cycle
- Page 34 and 35:
The work-reflection-learning cycle
- Page 37 and 38:
3 Software Engineering student proj
- Page 39 and 40:
Software Engineering student projec
- Page 41 and 42:
Software Engineering student projec
- Page 43 and 44:
Software Engineering student projec
- Page 45:
Software Engineering student projec
- Page 48 and 49:
The work-reflection-learning cycle
- Page 50 and 51:
The work-reflection-learning cycle
- Page 52 and 53:
The work-reflection-learning cycle
- Page 55 and 56:
5 Results This chapter presents an
- Page 57 and 58:
Results The background of P2 is a l
- Page 59 and 60:
Results project management and coll
- Page 61 and 62:
Results proposed in P5 was to allow
- Page 63 and 64:
Results Analysis of the results sho
- Page 65 and 66:
Results archives are found to conta
- Page 67 and 68:
Results (SVN). Trac provides lightw
- Page 69:
Results Figure 15: A model outlinin
- Page 72 and 73:
The work-reflection-learning cycle
- Page 74 and 75:
The work-reflection-learning cycle
- Page 76 and 77:
The work-reflection-learning cycle
- Page 78 and 79:
The work-reflection-learning cycle
- Page 81 and 82:
7 Evaluation In this chapter, I eva
- Page 83 and 84:
Evaluation adds to the CSCW literat
- Page 85 and 86:
Evaluation 7.3 Evaluation of the re
- Page 87 and 88:
Evaluation In the longitudinal stud
- Page 89 and 90:
Evaluation According to the princip
- Page 91 and 92:
Evaluation However, only some of th
- Page 93 and 94:
Evaluation to design is problematic
- Page 95 and 96:
8 Conclusion and further work This
- Page 97 and 98:
Conclusion and recommendations for
- Page 99 and 100:
9 References Abran, A., Moore, J. W
- Page 101 and 102:
References Cobb, P. (1994). "Where
- Page 103 and 104:
References Herbsleb, J. D., Mockus,
- Page 105 and 106:
References Leont'ev, A. N. (1981).
- Page 107 and 108:
References Stahl, G. (2002). "Build
- Page 109 and 110:
Glossary B Boundary object - artifa
- Page 111 and 112:
Glossary maintaining the system aft
- Page 113 and 114:
Appendix A: Research papers P1 P2 P
- Page 115 and 116:
Research paper P1 Title: Cross-Comm
- Page 117 and 118:
Cross-Community Collaboration and L
- Page 119 and 120:
the course staff may improve the co
- Page 121 and 122:
4: Case findings: students’ view
- Page 123 and 124:
own account of why each artifact is
- Page 125 and 126:
Research paper P2 Title: Power Thro
- Page 127 and 128: Power Through Brokering: Open Sourc
- Page 129 and 130: Due to the openness of OSS communit
- Page 131 and 132: 5.1.2 Second phase (February-May):
- Page 133 and 134: Getting from the second to the thir
- Page 135 and 136: 6.2.1 Benefits for SE student proje
- Page 137 and 138: Research paper P3 Title: Do’s and
- Page 139 and 140: DO‟S AND DON‟TS OF INSTANT MESS
- Page 141 and 142: a chat window is opened. As soon as
- Page 143 and 144: three examples in the form of excer
- Page 145 and 146: Example 2. Excerpt from an IM log s
- Page 147 and 148: Example 3. Excerpt from an IM log s
- Page 149 and 150: immediate feedback in the heated di
- Page 151 and 152: Acknowledgements Thanks to Monica D
- Page 153 and 154: Research paper P4 Title: The wiki a
- Page 155 and 156: The wiki as an integrative tool in
- Page 157 and 158: type of use can be seen as an examp
- Page 159 and 160: ecome integration, and we identifie
- Page 161 and 162: project. Typically, a clean-up was
- Page 163 and 164: 5.1 The wiki as a knowledge reposit
- Page 165 and 166: 6. Conclusion We have shown how pro
- Page 167 and 168: Research paper P5 Title: Using Proj
- Page 169 and 170: Proceedings of the 42nd Hawaii Inte
- Page 171 and 172: Proceedings of the 42nd Hawaii Inte
- Page 173 and 174: Proceedings of the 42nd Hawaii Inte
- Page 175 and 176: Proceedings of the 42nd Hawaii Inte
- Page 177: Proceedings of the 42nd Hawaii Inte
- Page 181 and 182: Shared timeline and individual expe
- Page 183 and 184: presentation. In 2008, there were 1
- Page 185 and 186: congruent’ to sets that seem to o
- Page 187 and 188: team members and the co-constructiv
- Page 189 and 190: Research paper P7 Title: A Model of
- Page 191 and 192: A Model of Retrospective Reflection
- Page 193 and 194: 420 B.R. Krogstie Fig. 1. Shared ti
- Page 195 and 196: 422 B.R. Krogstie information about
- Page 197 and 198: 424 B.R. Krogstie and to express ho
- Page 199 and 200: 426 B.R. Krogstie 4.2 The Temporal
- Page 201 and 202: 428 B.R. Krogstie in combining them
- Page 203 and 204: 430 B.R. Krogstie Fig. 3. A model o
- Page 205 and 206: 432 B.R. Krogstie 20. Hutchins, E.:
- Page 207 and 208: Research paper P8 Title: Supporting
- Page 209 and 210: Supporting Reflection in Software D
- Page 211 and 212: 2 Background In this section we bri
- Page 213 and 214: There are 3-5 students in the teams
- Page 215 and 216: 4 Research Method The research repo
- Page 217 and 218: 5 Findings In this section we draw
- Page 219 and 220: As a consequence, ‘startup coding
- Page 221 and 222: The type of data involved included
- Page 223 and 224: potentially negative effects is if
- Page 225 and 226: unfolded may shed light on the proc
- Page 227 and 228: 5. Lyytinen, K. and D. Robey, Learn
- Page 229 and 230:
Appendix B: Other research publicat