The work-reflection-learning cycle - Department of Computer and ...

Contributions and implications
apply them in their professional career. This is another way of bringing about crosscommunity
learning through PBL.
To the CSCW field, the thesis provides new knowledge about how data stored in
collaboration tools through a work practice, can be utilized to support that work practice
through retrospective reflection. Framed in state-of-the-art industry practice for project
retrospectives in SE project work, current usage of lightweight collaboration tools in
project work (e.g. as manifest in Contribution 2), theory on human reflection and
learning, and a focus on the project process (e.g. trajectory and sub-trajectories) as the
main object of reflection, some key points are established. Firstly, day-to-day usage of
collaboration tools in a project determines what aspects (and challenges) of project work
become reflected in the tools. Secondly, particular tool features are useful for access to
and navigation of historical data stored in (or by) the tools in the context of
retrospective reflection. This includes chronological overview of the project process and
easy access from points in the process to project artifacts (e.g. the project product) in
their there-and-then state. Thirdly, the organization of the retrospective reflection
activity in which the historical data are used, should be designed to incorporate
individual as well as collaborative knowledge construction and attend to „facts‟ as well
as „feelings‟ about the project process. Fourthly, if collaboration tools are given a dual
role in a work practice, supporting day-to-day work as well as retrospective reflection
on that work, the effect on the work practice should be considered and preferably
empirically investigated (e.g. looking for signs of increased or improved information
sharing or information hoarding).
For tool designers, these key points can be used to inform the design of collaboration
tools with the aim of making the tools useful for retrospective reflection.
For researchers analyzing project work settings with the aim of identifying ways of
supporting the work practice, the key points illuminate the option of introducing or
redesigning retrospective reflection activities, e.g. by utilizing collaboration tools as a
resource for the reflection. In the field of Software Engineering in particular, the
proposed use of collaboration tools can be considered an answer to one of the
challenges to having SE professionals actually prioritize retrospective reflection on their
projects: getting access to relevant data to aid the reflection process.
59