OU blog

Personal Blogs

Christopher Douce

Considering the dimensions of group work

Visible to anyone in the world
Edited by Christopher Douce, Thursday 12 February 2026 at 15:08

A couple of weeks ago I was asked to prepare a short contribution about group work to a TM253 module team meeting; TM253 is a new second level computing module that is being developed. When reflecting on this, I’ve realised that I’ve experienced online group work from a number of different perspectives: as a student, a tutor and a module chair.

What follows are some rough notes that summarise my experiences, followed by a really simple conceptual framework that relates to online academic group work. From a perspective of a student, the framework might be useful tool to understand what happens in your module. From the perspective of a module team member, if might be useful to understand how to think about group work.

Student experience: A335 Literature in transition

For one of the A335 TMAs, students had to contribute to a collaborative Wiki. We had to find some academic articles that related to some of our set texts, and share a summary of what we find, a couple of useful quotes, and a reference. In turn, we would get some marks for our trouble.

We would then use what was submitted within a longer essay. I really liked this activity, since the students ended up with quite a detailed bibliography that we could also refer to later if we ever needed to. It also focussed our attention to look at the texts that were not the focus of our substantive essay.

Tutor experience: M364 Interaction Design

I tutored on M364 Interaction Design for ten years, starting in 2006. When I started, we all used a product called FirstClass, which was eventually replaced by a version of the Moodle VLE. One of the TMAs focused on evaluation. Students had to take a sketch of a design that they produced in a design TMA and share it with a fellow student. In turn, they would carry out what is called a heuristic evaluation, and suggest enhancements.

One of my duties as a tutor was to pair students together into sub-forums where they would share sketches and evaluation results. These areas had weird names (apparently names are friendlier than numbers) but I can’t remember what any of them were called. On the occasions where I had an odd number of students I would put them into groups of three. When students didn’t submit their sketches, I would share a sketch that had been prepared by the module team.

The whole reason for doing this was to enable students to gain a little bit of experience of collaboration. There was also the point that different evaluators can find different things. It kind of worked, but it was always a bit clunky, and it always took a bit of explaining.

Module chair experience: TM354 Software Engineering

Software engineering is a team sport. Software engineers use all kinds of tools to communicate with each other. They use formal diagrams, sketches on whiteboard, post-it notes, requirements documents, and a myriad of other representations. With this in mind, it would be remiss of us not to attempt to share an experience of team working.

One of the processes that TM354 talks about is agile. Agile development teams are small teams that work together to solve specific problems. Members of agile teams are constantly talking to each other. Talking makes software real. Sharing of sketches and diagrams makes software real, and this is what happens in TM354.

In a couple of TMAs students create sketches and then share them to an online tool called ShareSpace. Fellow students are then invited to make helpful constructive comments about the sketches that have been submitted. In turn, students then go onto refine their earlier diagrams, reflecting on what changes they might have made. The big idea is to simulate some of the work that can happen within module teams.

Conceptual framework

Here’s what I’ve come up with: a simple framework.

Groups vs Teams

There’s an important difference between groups and teams. A group is a group of people that can make contributions that individually may contribute to solving a defined problem, but these are separate from each other. A team is a group of people who solve a defined problem whilst also knowing something about each member’s interests, abilities, knowledge and skills. A team works together closely with each other. A team needs time to form.

More group work takes place than teamwork.

Authentic vs Artificial

The key question here is: does the assessment activity directly reflect the skills that a module aims to develop, or does it reflect what a student may be doing after they graduate? An interesting authentic assessment scenario I have heard that relates to software engineering are scenarios where requirements change part way through an assessment; a theoretical customer may discover a new set of requirements they had never through of before. This notion speaks to a sub-dimension: what is expected vs the possibility of the unexpected. In the real world, new situations can emerge, and things can go wrong.

As suggested, an artificial assessment is one that aims to test learning outcomes in a way that may be distinct from how those learning outcomes may be applied in real situations. Ideally, assessments should be authentic, but when students have a lot to study, assessments are typically artificial, but with authentic elements.

Real tools vs Simplified tools

This follows on from the earlier dimension. Should a module make use of tools that are used ‘out there in the world’, which might be potentially difficult to understand and work with, or should a module team use tools that are designed to help understanding?

In computing, a good example of this is introducing students to a fully-fledged integrated development environment (IDE), such as Microsoft Visual Studio Code, or an IDE that has been specifically developed to help students understand concepts. An example of a useful but restricted tool is BlueJ. Put another way, do we need to provide guard rails?

This topic has been subject to academic debate. My own view is to go immediately with industrial strength tools, if it is able to do so. Academics should be able to offer practical guidance to show how these tools are used.

Interaction matters vs Outcome matters

This pair reflects a design aim from the module team and those writing the assessment. What is the overall objective of the assessment? Is skills and knowledge represented by the interaction or the process, or the product at the end. A related question is whether students should reflect on the actions undertaken by the team, or the effectiveness of the final outcome?

The process is always important, whether it is writing an essay, or writing software.

Actions for points vs Completion for points

This dimension follows on directly from the previous dimension and relates to the question of what is done to gain credit for an assignment. Does completing tasks, and showing you have completed tasks gain credit, or should we assign marks for the completed artifact? In some ways, this is a bit like the idea of ‘showing your marking’ within a maths assignment.

Looking at this practically, there should be points gained for completing (and compiling) evidence of tasks.

Individual scores vs Team scores

If there is a large team supported by a small number of high performing individuals, how should the marks be allocated? Should the overall result reflect the outcome, or should it reflect the individual contributions? The answer to this may well relate to what is being assessed.

Ultimately, there should be some actions and work that enable the contributions by individual students to be differentiated between each other.

Tutor oversight vs Team autonomy

This relates to the amount of scaffolding a tutor should provide, and the extent of the guidance provided whilst teamwork (or groupwork) is taking place. Within this, there is the implicit question of whether a tutor has a ‘plan b’ just in case something goes wrong. This is also connected to the extent to which the module team provides pre-selected tools, guidance or frameworks.

It takes time to observe what occurs within a team, and it takes time (and experience) to productively intervene if things get difficult. Given that tutors often do not have a lot of time, the responsibility for setting everything up and structuring activities should fall to the module team.

Repeated scenarios vs New scenarios

This dimension relates to an issue that the module team needs to resolve. Should they adjust an existing scenario for every module presentation, or should they endeavour to create a new scenario. The risk of creating a new scenario is that it runs the risk of introducing problems (which could, of course, be authentic – but not necessarily related to learning outcomes that need to be assessed).

What typically happens (in my experience) is that a scenario framework is created, and changes are made within that framework.

Reflections

Collaborative work is a term that covers both group work and teamwork. It is a topic that is featured within descriptions of degree level qualifications that are provided by the QAA. Given the nature of higher education, it is difficult to create collaborative assessments that are intrinsically authentic. Perhaps the best we can do is to create assessments that employ and use authentic tools. When considering teamwork, it is also important to necessarily consider safety in terms of the integrity of the assessment process, and the emotional and physical safety of those who participate. Guard rails are important.

Permalink Add your comment
Share post
Christopher Douce

Student Interaction and Collaboration in Tutorials: Why, What and How

Visible to anyone in the world

On 13 June 2024 I attended a seminar that was run by three colleagues from the School of Maths and Statistics: Cath Brown, Vinay Kathotia, and Abi Kirk. The seminar was intended for ‘anyone interested in the development of online teaching’.

For anyone finding this blog post, it might be useful to view this summary alongside other posts about Adobe Connect , tutorials, and online pedagogy.

What follows are some brief notes that I made from each of the presentations. For concision, I have taken the liberty of abridging each of the titles. Some reflections and acknowledgments are shared at the end.

Why should we promote students working together?

The subtitle for this first presentation, which was facilitated by Vinay Kathotia with Cath Brown was: what are the pedagogical and broader benefits?

A useful term was introduced: student-centred pedagogy. Student adopting an active role during a tutorial can mean increases in confidence and self-efficacy. Interaction can be as simple as students making points, listening, arguing, and responding to a tutorial.

These points can be connected to ‘inquiry based mathematics education’ where collaboration has the potential to lead to higher levels of inclusion. There are some advantages of collaboration: mathematics is a collaborative activity. Through tutors demonstrating mathematical thinking, students can see that mathematics can be messy.

I noted down the phrase: “community enhances attainment”. Community can relate to the study of a module, and anything that helps to develop community, but is also useful is important.

We were asked a question: what were everyone’s experiences? How do we convince the students it is a good idea for them to come along to tutorials? Perhaps writing can be useful; asking students to write an account of what happened during a tutorial, is one approach that can facilitate sharing and suggest the benefits of tutorials.

The design and structure of collaborative tasks

The second session was facilitated by Abi Kirk. The full title of this second session was ‘some ideas and examples on the nature, design and structure of collaborative tasks’. The presenters described some collaborative tasks they have used for tutorials: small-group problem solving (which takes place on M337), and ‘pub quiz’ group work.

In the pub quiz activity, students were put into breakout rooms where they have access to five questions. In each room, students record their answers. This then leads to a plenary session which is facilitated by a tutor where all the results are shared using an Adobe Connect whiteboard.

A question was asked: how could collaboration using breakout rooms work in your context? One thought is to giving information in advance; perhaps it is important for everyone to know what is going to happen in a tutorial. There is an inherent tension of giving them too much in advance. Making a session look enticing and interesting is a skill all of its own.

Technology to enable collaborative work

The full title of this session was ‘technology to enable collaborative work - Adobe Connect and beyond’. In this session we were introduced to a variety of different Adobe Connect features and maths tools the presenters have used, such as GeoGebra, Desmos and PolyPad. Different subjects will, of course, necessitate the use of different tools. What I might use as a computing tutor will, of course, be different to what a maths tutor may use.

You can, of course, use features within Adobe Connect, such as screensharing, file sharing and polls with external tools and utilities. In some tools it is possible to create multipart activities, for example, and share URLs (web page links) with students through a text chat window.

One other idea is to open a shared Microsoft OneNote notebook. Any OU student can use it through Office 365. It can be used as a whiteboard where student can share their work. Control could be given to students, where they could interact with mathematical text.

Towards the end of the session, we returned to the topic of breakout rooms. They are pretty complex, which means that it is important to make sure you have a solid understanding of the interaction metaphors that are used. Tutors need to know how to set up and move between different layouts, how to adding and deleting breakout rooms, how to start and end breakout rooms, how to communicate to all rooms, moving between rooms, and combining results from different rooms together in a virtual plenary space.

Reflections

Quite a lot of time has elapsed between attending the seminar (June) and making these notes available (November). This means that there is risk that the sessions may not be summarised as accurately as I would have liked them to be. This said, I hope the points that I have shared are helpful, and apologies to the facilitators if I have misrepresented anything.

I went to this session since I hold the view that student interaction through online tutorials is important, but I also have the sense that it is very difficult to do well. This session was of specific interest since there are some key similarities between maths and computing: both subjects work with textual notations. With maths, there are equations (and whatever mathematicians do); within computing there are programming languages.

I do feel that there are multiple structural and technological barriers that are put in everyone’s way before interaction can become possible. More often than not, I don’t hear any student voices in tutorials, since no one really knows anyone. I remember that a book called eModeration by Gilly Salmon emphasises the importance of digital socialisation. In the currently tutorial world, where students can attend any number of different tutorials by different tutors, the tentative social connections between everyone works against interaction and collaboration. I don’t know what the solution is.

Using distance learning technology to facilitate interaction and collaboration is difficult. I don’t know where this comes from, but I’m always minded that perhaps digital educators have to become digital media producers and performers. To be good at digital performance, rehearsals are essential.

Acknowledgements

Many thanks to all facilitators.

Permalink Add your comment
Share post
Christopher Douce

C&C research fiesta: getting research funding

Visible to anyone in the world
Edited by Christopher Douce, Tuesday 27 June 2023 at 16:03

This is the second in a short series of two posts that summarises some of the highlights of a ‘research fiesta’ that has held by the School of Computing and Communications. This post summarises some of the points that were made during a panel session about research funding.

The panel comprised of four professors (if I’ve counted correctly), a research manager from the STEM faculty, and was facilitated by our director of research, Robin Laney. Although the focus was about research funding, it could have also easily had another title: how to become a professor.

Here’s a list of some really useful tips that I noted down about gaining research funding: 

  1. Think about how you might go about forming a working relationship with a funding body. This might mean keeping an eye out for different research related events that they run. Networking is important. Take time to speak to them.
  2. To develop relationships with funders, join mailing lists, check their websites and respond to calls for advice and consultation activities.
  3. Take time to understand the motivations of a funding body and what their priorities are. Simply put, the closer a research proposal or bid fits the aims and objectives of a funding body, the higher the probability of success.
  4. As well as understanding their aims and objectives, take time to understand the processes that they use, both in terms of bid submission and also in terms of how bids are evaluated. A key tip here is: talk to colleagues who have been successful and know what the procedures are.
  5. Always try to play to the strength of the university. Each institution is unique.
  6. Consider projects or proposals that are a little ‘left field’; proposals that are slightly unusual or explores an unexpected area may cause interest and intrigue.
  7. Look for new funding programmes. Getting in early might benefit both the funder and the organisation (and project) that is funded, especially as the funding programme builds up experience and finds its distinct focus.
  8. Successful bids often have components of interdisciplinarity and collaboration. Unsuccessful bids don’t present a clear story.
  9. Find collaborators who are able to work between disciplines; these are rare people who can help with the writing of project bids and proposals.
  10. Find external stakeholders who have a lot to gain from their involvement in a project. When describing this, present a clear project narrative that others can easily understand.
  11. When working with collaborators and stakeholders, make sure that you give them plenty of time to create supporting documents, such as letters of support. 
  12. Think in terms of teams. Working with a team of people means that funders might see certain bids as being less risky. Use your team to read and review your bid.
  13. Learn how everything works. Become a bid reviewer and seek out opportunities to sit on funding panels. The experience of reviewing other bids is invaluable.
  14. Speak to your university ethics committee early (and show that you have done so).
  15. Think about creating what could be described as a portfolio of ideas to work on at any one time.
  16. Smaller grants can be important; small grants can lead to large ones. Small grants can help researchers and research groups to develop their experience and expertise.

Summary

There are lot of really helpful points here. The biggest points I took away from this session was: be strategic (consider your portfolio of interests), look at what funding bodies are doing and what they are doing, and network to find collaborators, and build a team around project bids. In essence, take a collaborative approach. 

Addendum

This is late breaking edit, to share an article that was shared after the fiesta, which has the title: 25 research tips and strategies. It is worth a look.

Permalink Add your comment
Share post
Christopher Douce

South East region: Associate Lecturer Development Conference, March 2015

Visible to anyone in the world

On 2 March I went to the South East region associate lecturer development conference.  Although the regional office has been closed, it still exists as an important administrative unit within the university.  This time, the conference was held at The River Centre, in Tonbridge, which was a conference venue I had never been to before. 

This blog post aims to summarise the different sessions that I attended during the day, and has been written using notes that I made during the day.  I hope it is useful for those who came along to the event, and other colleagues within the university who might be seeking ideas for their own sessions.

A collaborative approach to teaching a level 1 module

The conference had two workshops; a morning workshop and an afternoon workshop.  The first workshop I went to was by Bill Adler, who tutors on L161 Exploring Languages and Cultures.  The aim of the workshop was just to share some experience of teaching as collaboration. 

L161is a compulsory level 1 (first year equivalent) language studies module that addresses intercultural skills and awareness.  It consists of four different books (one for each block) and a module web site.  Approximately one thousand students at any one time might be studying the module.  Interestingly, the module makes extensive use of on-line forums.  To make this work, tutors are allocated to a number of clusters (which is an idea which immediately made me think of the group tuition policy).  The reason for this is that one thousand students contributing to a single group of discussion forums is clearly too many; some students could be overwhelmed with posts.  A cluster that comprises of around 250 students is likely to be a lot more manageable, and there’s always something that is going on to make it sufficiently interesting.

Bill talked us through two different activities that can take place through his module.  The first was an autobiography of intercultural encounters (Council of Europe website).  We gave this a go, and this led to a reflection about our own cultural identity and what it meant.

The second was how to develop reading skills in a foreign language.  A challenge with this module is that everyone might be learning a different language (you might have students studying French, Spanish, or German, for instance).  A way around this was to choose and activity and a language that isn’t likely to be too familiar to students who are taking the module.  Our challenge (which we accepted) was to try our best to decipher a menu that was written in Welsh, without knowing anything about the language.  After having a go, we swapped strategies, and we discovered that, actually, we could figure out quite a lot!  Different participants used different strategies.

During the session, I made a couple of other notes.  One note was that: different students mean different backgrounds, which mean different skills and perspectives.  Diversity creates richness, and this is a point that is reflected in the module. 

Another note that I made was about the concept of peer monitoring.  Since tutors are working in clusters, there was an opportunity to allow tutors to work more closely together with each other.

The closing activity was to reflect on our own collaborative practice.  I remember the point that working together isn’t too difficult, but true in-depth collaboration takes time to facilitate and develop, since you have to know and trust the other people who you’re working with.

Also, collaboration can mean the sharing of materials.  If one tutor is particularly busy, another one can help to share the load. The broad point of the session was: there are quite a few opportunities for tutor collaboration.  It is, however, important that the staff tutor (or line manager) and module team work together to facilitate that collaboration.

Yet again on correspondence tuition: how do we teach through marking?

Correspondence is a perennial subject in AL development conferences, but I haven’t been to a session about it for quite a while.  In fact, the last one I went to could have been at an event for design ALs over two years ago.

This session was facilitated by Vicky Roupa, who spoke about the research that she carried out as a part of her OpenPAD project.  OpenPAD is a university ‘professional academic development’ programme, and leads to fellowship of the Higher Education Academy. 

Vicky mentioned the Supporting Open Learners reader, a book that I remember reading when I first joined the university.  Vicky made the point that correspondence tuition is, of course, the main form of teaching.  Other points that I noted was that it was important to engage in a dialogue with the student, and that correspondence tuition is an action that is student led.

We were asked a number of questions: what do we teach?  How do we encourage students to engage?  How do we develop writing so it becomes a major key to learning?

An important point was that students don’t always read (or, indeed, know about) the correspondence teaching that they have been given.  Also, students might not understand the feedback that they have been given, or be able to use the guidance.

To try to engage students, one approach is to choose the most important points to focus on.  Our challenge is to choose which comments are best placed to move a student along.  One other tip was to add links to useful resources within the script comments, such as a link to certain sections in the Skills for Study website.

Another point was that receiving feedback from a tutor can be sometimes tough and involves lots of different emotions.  Vicky’s research was all about trying to gather ‘feedback on feedback’.  Her point is that tutors often mark assignments, return them to students, and then never hear back from them.  Closing the feedback loop can have the potential of helping a tutor to learn more about how to improve their teaching practice.  This was connected to an earlier project (which was mentioned at an earlier South East conference), where students are encouraged to talk through their views about feedback.  Information about this project is available from the Languages Open Resource Online repository.

Towards the end of the session, I made a few final notes (and questions) which might resonate with fellow tutors.  These were: ‘are we assessing or are we teaching?’ (it does depend on the design of the module) and ‘avoid judging too much and too powerfully’ (so we can engage in a meaningful dialog with students).

Reflections

This AL development conference seemed to be smaller than other that I’ve been to.   For some reason, the autumn events seem to be a whole lot busier than the spring events.  I would have (personally) liked to have gone to one more session, to see what else was going on, but I do appreciate that timing is always going to be a challenge (tutors, of course, give up a lot of their Saturdays already!)

The biggest take away points of the day came from interactions with the other tutors in the sessions.  I found the activity in the morning session interesting (and fun!), and found the sharing of views about correspondence tuition useful and reassuring.

Permalink Add your comment
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 3643310