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

considered whether current use of IM plays a role. Where IM is successfully supporting project work, it might still be worthwhile for the team to account for the tool usage, to increase their understanding of their own work practice and to become aware of potential problems. Distributed project work can be successfully supported by instant messaging as a communication channel combined with shared workspace access, as seen in Example 1. The example illustrated how the social and the task-oriented aspects of working together were both present in the communication taking place through the tool. Such an arrangement should be considered an option in projects that for some reason depends on work to be conducted in a distributed way (e.g. when one or more students have to partially work from home). It should be noted, however, that in our projects, the team members‟ work is partially collocated. The likelihood of success of IM chat as a substitute for face-to-face interaction may be different with students who do not know each other from face-to-face interaction, but we cannot draw conclusions about differences between IM use in virtual and partially collocated teams from our study. The practice of letting the student teams choose the collaboration technology for their projects is in line with the independence seen as important in project-based learning. Also, it can be seen as a way of encouraging students to make use of their existing competence with certain tools, e.g. IM tools, and consider how they should be applied in a new and challenging context (e.g. that of coordinating complex work tasks and collaborating with external stakeholders). Being allowed to choose the collaboration technology for their projects, we assume that most teams will choose to use IM tools for some aspects of their work, given the ground that these tools has gained as personal communication infrastructure among the students. However, whereas most students in our study were users of a particular IM service, individual preferences vary. In the projects, we occasionally saw individual students refusing to use certain tools on principle (e.g. by being against proprietary software) while the rest of the team wanted to use those tools. In such cases, the teams might benefit from their supervisor‟s mitigation to find good solutions. For the organizing of SE project courses, we see the following implications of students‟ competence with IM tools: The student teams should be allowed to choose the collaboration technology for their projects, within the constraints of availability, the team‟s competence and the customer‟s requirements. Teams should be required to present their supervisor with an account of their practices of using instant messaging, and the supervisor should use this information as a basis for providing process guidance. In projects heavily depending on distributed work, the use of instant messaging chat to aid such work should be discussed with the team. Example 2 illustrated that informal collaboration between the team and the supervisor may be successfully conducted over IM. We believe that keeping IM open as a communication channel between team and supervisor can encourage students to get early in touch when they are in need of help, which makes it possible to solve problems before they escalate and before too much time is spent on being stuck. The viability of this solution depends on the supervisor‟s willingness to use IM in communication with the student and to be available for consultation on a fairly short, or at least explicitly agreed-upon, notice. We see the following general implication for the organizing of SE project courses: Course staff may use instant messaging as a collaboration tool for providing informal supervision or otherwise communicate informally with the project students. Expected availability (e.g. response time) should be explicitly addressed as the use of IM for collaboration is agreed with the team. Example 3 illustrates the general challenge of stakeholder communication and, in particular, communication with the customer, in project work. Successful stakeholder communication depends on project teams‟ ability to share the right information in the right format at the right time. Where there are language and/or cultural barriers, the challenges of communication increase. As Frode from Example 3 put it in an interview after completion of their project: “We did not know if the customer was joking or if he was angry with us!”. The choice and use of collaboration technology strongly impacted on the communication. IM chat with the use of standard functionality (i.e. text only) provided opportunities for 130 22

immediate feedback in the heated discussion while conveying a sense of informality and providing limited opportunities for the communicating parties to monitor each other‟s reactions (e.g. through tone of voice and body language). In Example 3, the mismatch between the communication needs and the affordances of the communication medium was particularly severe. The Molotov cocktail of problematic factors included the team and customer never having met, not knowing each other, having different native language and cultural background (including organizational/university culture – one being hierarchical and the other flat), having different conceptions of responsibilities connected to the customer role in the project, and the team being in a situation of severe problems (being far behind schedule while important resources were missing). The team may be unable to identify a potential mismatch between the choice of communication medium, the purpose of communication and the form of communicating. In some cases, as in Example 3, the customer might have suggested an inadequate arrangement for communication. A similar and typical example, related to another type of collaboration tool, is when the customer insists on the use of email for all student enquiries but turns out to be very slow in answering his email. The biggest and most general problem illustrated in Example 3, however, is that IM is being used for formal collaboration. Many project issues require a formal meeting, properly prepared and documented, or formal, thought-through, written communication, with copies and attachments. Instant messaging can be seen to encourage an informal tone and comments which are not meant to be revisited for purposes of documentation, even if logging is possible. If IM is used in team-customer collaboration, the logs should be kept by the team for purposes of process documentation, and the customer should be informed about this usage. For instance, the IM log from which Example 3 is drawn was an important part of the documentation of the project process and used by course staff in the evaluation of the project. The IM log illustrated some reasons for the disappointing project result. In contrast to Example 3, our findings from the SE project course also included examples of successful use of IM in team-customer collaboration, enabling teams to have quick feedback from a remote customer (See Section 4.2) on mainly technical aspects of software development. In this case, the purpose and issues of IM conversation were limited and clear. Implications for the organizing of SE project courses of the challenges of using IM for customer communication include: Given the high project risk associated with unsuccessful customer communication, project supervisors should make sure that they are aware of, and accordingly require the team to account for, how collaboration with stakeholders is conducted in the team, including the use of collaboration technology, e.g. instant messaging tools. If the customer has asked for an arrangement of communication highly likely to cause problems for the team, the supervisor might provide the team with advice on how to change the arrangement or point out what are the pitfalls. With respect to formal communication, in general, instant messaging should be used with care. The participants should ensure that the needs of formal communication are met, for instance that there is enough information to provide the social awareness necessary for the parties to understand each other‟s views and feelings (e.g. satisfaction, anger) when important issues are discussed. This might not be possible over instant messaging alone if the parties are not familiar with each other from previous face-to-face interaction. Also, the parties should make sure that the communication is documented in a way suitable for archiving and later retrieval. If any collaboration with the customer takes place over instant messaging, the conversations should be logged, in agreement with the customer If the customer is motivated to use instant messaging to be able to give rapid feedback on technical issues, the team should use the opportunity. Many of the implications outlined in this section address issues that apply to the use of collaboration technology in general to support work in the SE student teams, not only to the use of instant messaging. Even if most teams in our study seemed to be capable of choosing adequate media for various aspects of cooperative work, we suggest that it be made a topic in the introductory presentation of the project course. 131 23

considered whether current use <strong>of</strong> IM plays a role. Where IM is successfully supporting project <strong>work</strong>, it<br />

might still be worthwhile for the team to account for the tool usage, to increase their underst<strong>and</strong>ing <strong>of</strong><br />

their own <strong>work</strong> practice <strong>and</strong> to become aware <strong>of</strong> potential problems.<br />

Distributed project <strong>work</strong> can be successfully supported by instant messaging as a communication channel<br />

combined with shared <strong>work</strong>space access, as seen in Example 1. <strong>The</strong> example illustrated how the social<br />

<strong>and</strong> the task-oriented aspects <strong>of</strong> <strong>work</strong>ing together were both present in the communication taking place<br />

through the tool. Such an arrangement should be considered an option in projects that for some reason<br />

depends on <strong>work</strong> to be conducted in a distributed way (e.g. when one or more students have to partially<br />

<strong>work</strong> from home). It should be noted, however, that in our projects, the team members‟ <strong>work</strong> is partially<br />

collocated. <strong>The</strong> likelihood <strong>of</strong> success <strong>of</strong> IM chat as a substitute for face-to-face interaction may be<br />

different with students who do not know each other from face-to-face interaction, but we cannot draw<br />

conclusions about differences between IM use in virtual <strong>and</strong> partially collocated teams from our study.<br />

<strong>The</strong> practice <strong>of</strong> letting the student teams choose the collaboration technology for their projects is in line<br />

with the independence seen as important in project-based <strong>learning</strong>. Also, it can be seen as a way <strong>of</strong><br />

encouraging students to make use <strong>of</strong> their existing competence with certain tools, e.g. IM tools, <strong>and</strong><br />

consider how they should be applied in a new <strong>and</strong> challenging context (e.g. that <strong>of</strong> coordinating complex<br />

<strong>work</strong> tasks <strong>and</strong> collaborating with external stakeholders). Being allowed to choose the collaboration<br />

technology for their projects, we assume that most teams will choose to use IM tools for some aspects <strong>of</strong><br />

their <strong>work</strong>, given the ground that these tools has gained as personal communication infrastructure among<br />

the students. However, whereas most students in our study were users <strong>of</strong> a particular IM service,<br />

individual preferences vary. In the projects, we occasionally saw individual students refusing to use<br />

certain tools on principle (e.g. by being against proprietary s<strong>of</strong>tware) while the rest <strong>of</strong> the team wanted to<br />

use those tools. In such cases, the teams might benefit from their supervisor‟s mitigation to find good<br />

solutions.<br />

For the organizing <strong>of</strong> SE project courses, we see the following implications <strong>of</strong> students‟ competence with<br />

IM tools:<br />

<br />

<br />

<br />

<strong>The</strong> student teams should be allowed to choose the collaboration technology for their projects, within<br />

the constraints <strong>of</strong> availability, the team‟s competence <strong>and</strong> the customer‟s requirements.<br />

Teams should be required to present their supervisor with an account <strong>of</strong> their practices <strong>of</strong> using<br />

instant messaging, <strong>and</strong> the supervisor should use this information as a basis for providing process<br />

guidance.<br />

In projects heavily depending on distributed <strong>work</strong>, the use <strong>of</strong> instant messaging chat to aid such <strong>work</strong><br />

should be discussed with the team.<br />

Example 2 illustrated that informal collaboration between the team <strong>and</strong> the supervisor may be<br />

successfully conducted over IM. We believe that keeping IM open as a communication channel between<br />

team <strong>and</strong> supervisor can encourage students to get early in touch when they are in need <strong>of</strong> help, which<br />

makes it possible to solve problems before they escalate <strong>and</strong> before too much time is spent on being<br />

stuck. <strong>The</strong> viability <strong>of</strong> this solution depends on the supervisor‟s willingness to use IM in communication<br />

with the student <strong>and</strong> to be available for consultation on a fairly short, or at least explicitly agreed-upon,<br />

notice. We see the following general implication for the organizing <strong>of</strong> SE project courses:<br />

<br />

Course staff may use instant messaging as a collaboration tool for providing informal supervision or<br />

otherwise communicate informally with the project students. Expected availability (e.g. response<br />

time) should be explicitly addressed as the use <strong>of</strong> IM for collaboration is agreed with the team.<br />

Example 3 illustrates the general challenge <strong>of</strong> stakeholder communication <strong>and</strong>, in particular,<br />

communication with the customer, in project <strong>work</strong>. Successful stakeholder communication depends on<br />

project teams‟ ability to share the right information in the right format at the right time. Where there are<br />

language <strong>and</strong>/or cultural barriers, the challenges <strong>of</strong> communication increase. As Frode from Example 3<br />

put it in an interview after completion <strong>of</strong> their project: “We did not know if the customer was joking or if<br />

he was angry with us!”. <strong>The</strong> choice <strong>and</strong> use <strong>of</strong> collaboration technology strongly impacted on the<br />

communication. IM chat with the use <strong>of</strong> st<strong>and</strong>ard functionality (i.e. text only) provided opportunities for<br />

130<br />

22

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

Saved successfully!

Ooh no, something went wrong!