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 ...

21.01.2014 Views

The work-reflection-learning cycle in SE student projects: Use of collaboration tools has been developed as a prototype and tested through scenario evaluation by expert groups (P5). For course staff and others involved in the organization of SE student projects, the tools for conducting retrospective reflection provide a way of implementing state-of-the-art SE approaches (e.g. agile development methodologies) in SE student projects as well as a way of improving the learning outcomes. The insights about the potential of collaboration tools to support retrospective reflection can help course staff decide whether to impose or encourage the use of particular tools in the projects, based on their potential to aid retrospective reflection. For organizers of PBL in domains other than software engineering, the thesis demonstrates that an important part of the reflective activity of a project team can be facilitated and organized in a workshop format. The design of the workshops as outlined in P6 is focused on project work and project process independently of the SE domain and is applicable to other work domains. As argued in the thesis, the ideal in PBL is that the retrospective reflection of a team be part of the real work practice and not a separate, educational exercise. Thus, for PBL-based courses within other domains the organizers should find ways of making the reflection workshops an integral part of the work practice, possibly by linking them to existing learning practices within the domain. As a second option, the thesis research indicates that reflection workshops can be introduced as more of an educational exercise: students appear to find it interesting to get the opportunity to reconstruct and account for their story about the project and hear the story of the other team members. The approach based on the drawing of individual and shared timelines and satisfaction curves allows participants to address the emotional aspects of project work in a form that does not put them off writing or talking „about their feelings‟ or spending what they see as too much time elaborating on the project process. The reflection workshop presented in P8 was adapted to a CSCW research agenda and is not a readily applicable design for retrospective reflection in PBL settings. However, the finding that steps of investigating historical data in collaboration tools can be incorporated into an existing workshop approach and thereby improve it, can be utilized by PBL organizers as in the development of other tool-aided reflection workshop designs. For the organizations (in industry or education) in which PBL takes place, the proposed approaches to retrospective reflections may contribute to organizational learning. Organizers of PBL efforts consider using the results from the reflection workshops as a way of informing the development of their courses, taking some precautions as discussed in P6. This would support the educational practitioners as researchers and developers of their own practice. Also, in formal education, successful incorporation of retrospective reflection workshops in PBL can ultimately contribute to industry practice if the students who learn the techniques find them useful and later 58

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

<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 />

has been developed as a prototype <strong>and</strong> tested through scenario evaluation by expert<br />

groups (P5).<br />

For course staff <strong>and</strong> others involved in the organization <strong>of</strong> SE student projects, the tools<br />

for conducting retrospective <strong>reflection</strong> provide a way <strong>of</strong> implementing state-<strong>of</strong>-the-art<br />

SE approaches (e.g. agile development methodologies) in SE student projects as well as<br />

a way <strong>of</strong> improving the <strong>learning</strong> outcomes. <strong>The</strong> insights about the potential <strong>of</strong><br />

collaboration tools to support retrospective <strong>reflection</strong> can help course staff decide<br />

whether to impose or encourage the use <strong>of</strong> particular tools in the projects, based on their<br />

potential to aid retrospective <strong>reflection</strong>.<br />

For organizers <strong>of</strong> PBL in domains other than s<strong>of</strong>tware engineering, the thesis<br />

demonstrates that an important part <strong>of</strong> the reflective activity <strong>of</strong> a project team can be<br />

facilitated <strong>and</strong> organized in a <strong>work</strong>shop format. <strong>The</strong> design <strong>of</strong> the <strong>work</strong>shops as outlined<br />

in P6 is focused on project <strong>work</strong> <strong>and</strong> project process independently <strong>of</strong> the SE domain<br />

<strong>and</strong> is applicable to other <strong>work</strong> domains. As argued in the thesis, the ideal in PBL is that<br />

the retrospective <strong>reflection</strong> <strong>of</strong> a team be part <strong>of</strong> the real <strong>work</strong> practice <strong>and</strong> not a separate,<br />

educational exercise. Thus, for PBL-based courses within other domains the organizers<br />

should find ways <strong>of</strong> making the <strong>reflection</strong> <strong>work</strong>shops an integral part <strong>of</strong> the <strong>work</strong><br />

practice, possibly by linking them to existing <strong>learning</strong> practices within the domain. As a<br />

second option, the thesis research indicates that <strong>reflection</strong> <strong>work</strong>shops can be introduced<br />

as more <strong>of</strong> an educational exercise: students appear to find it interesting to get the<br />

opportunity to reconstruct <strong>and</strong> account for their story about the project <strong>and</strong> hear the<br />

story <strong>of</strong> the other team members. <strong>The</strong> approach based on the drawing <strong>of</strong> individual <strong>and</strong><br />

shared timelines <strong>and</strong> satisfaction curves allows participants to address the emotional<br />

aspects <strong>of</strong> project <strong>work</strong> in a form that does not put them <strong>of</strong>f writing or talking „about<br />

their feelings‟ or spending what they see as too much time elaborating on the project<br />

process. <strong>The</strong> <strong>reflection</strong> <strong>work</strong>shop presented in P8 was adapted to a CSCW research<br />

agenda <strong>and</strong> is not a readily applicable design for retrospective <strong>reflection</strong> in PBL<br />

settings. However, the finding that steps <strong>of</strong> investigating historical data in collaboration<br />

tools can be incorporated into an existing <strong>work</strong>shop approach <strong>and</strong> thereby improve it,<br />

can be utilized by PBL organizers as in the development <strong>of</strong> other tool-aided <strong>reflection</strong><br />

<strong>work</strong>shop designs. For the organizations (in industry or education) in which PBL takes<br />

place, the proposed approaches to retrospective <strong>reflection</strong>s may contribute to<br />

organizational <strong>learning</strong>. Organizers <strong>of</strong> PBL efforts consider using the results from the<br />

<strong>reflection</strong> <strong>work</strong>shops as a way <strong>of</strong> informing the development <strong>of</strong> their courses, taking<br />

some precautions as discussed in P6. This would support the educational practitioners as<br />

researchers <strong>and</strong> developers <strong>of</strong> their own practice. Also, in formal education, successful<br />

incorporation <strong>of</strong> retrospective <strong>reflection</strong> <strong>work</strong>shops in PBL can ultimately contribute to<br />

industry practice if the students who learn the techniques find them useful <strong>and</strong> later<br />

58

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!