The work-reflection-learning cycle - Department of Computer and ...
The work-reflection-learning cycle - Department of Computer and ...
The work-reflection-learning cycle - Department of Computer and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>The</strong> <strong>work</strong>-<strong>reflection</strong>-<strong>learning</strong> <strong>cycle</strong> in SE student projects: Use <strong>of</strong> collaboration tools<br />
provide a certain image <strong>of</strong> their project (internally <strong>and</strong> externally), as a coordination<br />
mechanism, <strong>and</strong> as shared <strong>work</strong>space.<br />
5.5 P5: Using Project Wiki History to Reflect on the Project<br />
Process<br />
Author: Krogstie, Birgit<br />
Published in: Proceedings <strong>of</strong> the 42nd Hawaii International Conference on System<br />
Sciences (HICSS) 2009<br />
In this paper, we address the potential <strong>of</strong> project wikis to support <strong>reflection</strong> on the project process<br />
through participants’ reconstruction <strong>of</strong> the project trajectory. Drawing on a case study <strong>of</strong> s<strong>of</strong>tware<br />
engineering project <strong>work</strong>, we illustrate how information on project history can be found in a project wiki<br />
<strong>and</strong> may be used to support recall <strong>of</strong> <strong>and</strong> <strong>reflection</strong> on the process. We discuss implications for<br />
postmortem project reviews by considering how the utilization <strong>of</strong> project wikis could addresses some<br />
challenges to successful reviews. We also propose extended wiki functionality that can be used to make a<br />
more selective review <strong>of</strong> project history based on user-tagged contents.<br />
<strong>The</strong> research presented in P5 was initiated based on findings from the research on dayto-day<br />
use <strong>of</strong> project wikis in the capstone projects. In our interviews <strong>of</strong> project team<br />
members about their use <strong>of</strong> project wikis, the wikis themselves were examined as an aid<br />
to the interview. It turned out that recall <strong>and</strong> <strong>reflection</strong> was effectively aided by the<br />
browsing <strong>of</strong> wiki contents. As a consequence I decided to focus not only on day-to-day<br />
use <strong>of</strong> the wikis in the projects, but investigate the potential <strong>of</strong> the wikis to be used<br />
retrospectively to aid recall <strong>of</strong> <strong>and</strong> <strong>reflection</strong> on the process.<br />
P5 demonstrates that given the current use <strong>of</strong> wikis as lightweight project management<br />
tools, there is a potential to utilize the historical information in the wikis for purposes <strong>of</strong><br />
recalling <strong>and</strong> reflecting on important aspects <strong>of</strong> the project process. Wiki contents (e.g.<br />
the various revisions <strong>of</strong> the project wiki main page) can be chronologically traversed in<br />
a „tour‟ <strong>of</strong> the project. By examining page contents <strong>and</strong> following hyper-links, the user<br />
can inspect details related to the process <strong>and</strong> some <strong>of</strong> the project artifacts. <strong>The</strong><br />
combination <strong>of</strong> chronological traversal <strong>and</strong> inspection <strong>of</strong> details aids recall <strong>and</strong><br />
<strong>reflection</strong>.<br />
P5 also identifies a potential for improvement <strong>of</strong> project wikis with the aim <strong>of</strong> providing<br />
better support for retrospective <strong>reflection</strong>. More focused navigation <strong>of</strong> historical data<br />
would be possible if the wiki allowed chronological browsing <strong>of</strong> the wiki pages<br />
considered most relevant to retrospective <strong>reflection</strong>. What is relevant in this respect will<br />
vary between projects <strong>and</strong> individual team members. Importantly, it should be possible<br />
to chronologically browse relevant page revisions (e.g. <strong>of</strong> the main page, showing the<br />
development <strong>of</strong> the team‟s frequently updated to do-list). <strong>The</strong> solution to this challenge<br />
42