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 />
Trac, <strong>and</strong> to incorporate individual sessions preceding the collective one. In the<br />
individual sessions, after the students had constructed their timeline <strong>of</strong> the project, we<br />
asked them to chronologically browse the timeline on the Trac main page see to see if<br />
this would make them remember events that had not been remembered by memory<br />
alone. This step would make it possible for us to observe differences between team<br />
members in their use <strong>of</strong>, <strong>and</strong> benefit from, the historical information; differences that<br />
might be attributed to their different roles in the project.<br />
Findings from the study showed that the historical data accessed through the tool helped<br />
the students remember events or detailed information about events (e.g. their exact<br />
time). Whereas all team members remembered something new to add to the purely<br />
memory-based timeline, the benefit <strong>of</strong> using Trac retrospectively was bigger for the two<br />
lead programmers than for the other three team members. <strong>The</strong> event „pre-study coding‟<br />
(e.g. the onset <strong>of</strong> coding <strong>work</strong>) was not remembered by anyone prior to use <strong>of</strong> Trac. <strong>The</strong><br />
use <strong>of</strong> Trac led the two lead programmers to remember <strong>and</strong> acknowledge that coding<br />
<strong>work</strong> took place early in the project. In the collective timeline construction, pre-study<br />
coding was brought into the shared timeline <strong>and</strong> achieved „<strong>of</strong>ficial status‟ as important<br />
in the team. However, as the follow-up interviews from the study demonstrated, there<br />
were viewpoints among the three other team members on how the pre-study activity<br />
was conducted that were not brought up, probably due to the dominance <strong>of</strong> the two lead<br />
programmers <strong>and</strong> their version <strong>of</strong> what pre-study programming was about. This is<br />
further elaborated in the evaluation <strong>of</strong> the research process in 7.3.1.<br />
<strong>The</strong> findings from the study are summarized in three main points about what was<br />
important to make the tool-aided <strong>reflection</strong> successful: the organization <strong>of</strong> the <strong>work</strong>shop<br />
into individual <strong>and</strong> collaborative steps <strong>of</strong> knowledge construction with the use <strong>of</strong><br />
adequate representations <strong>of</strong> the project process; the tool features for giving<br />
chronological overview <strong>of</strong> project events; <strong>and</strong> the tool features for navigating between<br />
overview <strong>and</strong> detail. <strong>The</strong> latter features permitted access from the chronological<br />
overview to there-<strong>and</strong>-then versions <strong>of</strong> project artifacts, thus supporting the close<br />
linking <strong>of</strong> process <strong>and</strong> product that is characteristic <strong>of</strong> SE <strong>work</strong>. Based on the findings,<br />
P8 outlines a set <strong>of</strong> guiding questions that can be used to help assess the potential <strong>of</strong> a<br />
collaboration tool to aid <strong>reflection</strong> on SE <strong>work</strong>. <strong>The</strong> questions are intended as a step<br />
towards a frame<strong>work</strong> relating various types <strong>of</strong> collaboration tools to the aspects <strong>of</strong> dayto-day<br />
SE <strong>work</strong> supported by the tools <strong>and</strong> the potential for the tools to aid retrospective<br />
<strong>reflection</strong>.<br />
P8 also provides an example <strong>of</strong> how the <strong>reflection</strong> model from P7 can be instantiated so<br />
as to comprise selected elements <strong>of</strong> a specific <strong>work</strong>-<strong>reflection</strong>-<strong>learning</strong> <strong>cycle</strong>, in this<br />
case focusing on the role <strong>of</strong> Trac in the case study <strong>of</strong> P8 (see Figure 15).<br />
50