TDDD83 Automatic translation; Swedish version is authoritative

Groups and supervision

Project groups

You will be divided into groups of approximately 8 people. The development groups are self-organised. Individual members of the development group may have specialist competence and focus more on certain areas, but responsibility lies with the group as a whole. Examples of areas of responsibility include Git manager, documentation manager, meeting chair, room booking manager, test manager, development manager, architecture manager, front-end manager, back-end manager, scrum master, etc. Note however that all group members should have knowledge and insight into all areas, and being responsible does not mean doing the work alone. Everyone on a Scrum team must develop and test.

The Scrum master:

• Acts as coach for the group.
• Ensures adherence to the process.
• Removes obstacles to the group's progress.
• Synchronises between the group and other stakeholders.
• Participates in Scrum master meetings.

If any group is not functioning, in the sense that not everyone is doing their part, the supervisor must be notified immediately.

The supervisor

• Each group is assigned a supervisor. In the bachelor's project, the individual's and group's own participation and responsibility are central, and the group is supported by a supervisor who plays a supportive role. This person is NOT a subject teacher who will explain how everything works; rather, the supervisor's task is to help the group function well, to learn how to learn, and to solve problems.
• The supervisor can, for example, help the group understand what is happening in the project by asking questions, drawing attention to what is happening in the group or how they work. The supervisor does not intervene unnecessarily, only when needed. It may also involve making students aware of how relevant certain elements are to the project and the bachelor's work.
  Since students are also expected to learn the technical development and process themselves, the supervisor's contributions change over time as students become more and more proficient. It is therefore also important that the supervisor does not intervene too quickly if it looks as though the group is about to make some kind of mistake, since it is important that students themselves learn to notice and correct mistakes.
• The supervisor will provide feedback on the first version of the report and assess the report submitted before the opposition, identifying any deficiencies and weaknesses.
• You will have weekly meetings with the supervisor. In the schedule these occasions are booked and marked with "Supervision". At these occasions you should start by holding the daily stand-up Scrum meeting. At the first meeting the supervisor will raise important aspects such as the principles of the course and the syllabus. The group and supervisor should at the first meeting discuss relevant ground rules that shall apply during the course. At the other meetings it is the group that drives the meeting, not the supervisor. Attendance is mandatory.
• Contact information for supervisors is available on the Contact info page

The groups

Will be published before the course starts in Lisam in the course room under Course Documents. If you are not on the list, contact the examiner immediately.

Page responsible: Martin Sjoelund
Last updated: 2026-02-27