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 ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<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 />
Figure 12: Snapshot <strong>of</strong> the whiteboard after the <strong>reflection</strong> <strong>work</strong>shop <strong>of</strong> one<br />
project team, showing the shared project timeline with the individual satisfaction<br />
curves. <strong>The</strong> numbers along Max’s curve indicate where he explained this<br />
experience to the rest <strong>of</strong> the team. From P6.<br />
5.7 P7: A model <strong>of</strong> retrospective <strong>reflection</strong> in project based<br />
<strong>learning</strong> utilizing historical data in collaborative tools<br />
Author: Krogstie, Birgit<br />
Published in: Proceedings <strong>of</strong> EC-TEL 2009<br />
In project based <strong>learning</strong>, <strong>learning</strong> from experience is vital <strong>and</strong> necessitates <strong>reflection</strong>. Retrospective<br />
<strong>reflection</strong> is a conscious, collaborative effort to systematically re-examine a process in order to learn<br />
from it. In s<strong>of</strong>tware development student projects it has been empirically shown that project teams’<br />
retrospective <strong>reflection</strong> can help the teams collaboratively construct new knowledge about their process<br />
<strong>and</strong> that historical data in collaborative tools used in daily project <strong>work</strong> can aid the teams’ recall <strong>and</strong><br />
<strong>reflection</strong> on the different aspects <strong>of</strong> project <strong>work</strong>. In this paper, we draw on these results as well as other<br />
findings on the use <strong>of</strong> collaborative tools in a similar setting. We use the frame<strong>work</strong> <strong>of</strong> distributed<br />
cognition to develop a model <strong>of</strong> retrospective <strong>reflection</strong> in which collaborative tools used as cognitive<br />
tools for daily project <strong>work</strong> are utilized as cognitive tools in retrospective <strong>reflection</strong>, aiding the creation<br />
<strong>of</strong> individual <strong>and</strong> shared representations <strong>of</strong> the project process.<br />
P7 sheds light on the potential to use historical data in various types <strong>of</strong> collaboration<br />
tools in retrospective <strong>reflection</strong>. A reason to utilize different tools is that they are<br />
applied for various purposes in day-to-day project <strong>work</strong> <strong>and</strong>, as a consequence, contain<br />
historical data on different aspects <strong>of</strong> the project process. <strong>The</strong> relevance <strong>of</strong> historical<br />
information in project wikis <strong>and</strong> issue trackers was demonstrated in P5 <strong>and</strong> P8. Email<br />
46