Retrospective Meeting

Author: cef

Created: 2018-06-05 05:21pm

Edited: 2018-08-17 11:45am

Keywords: Bachelor supervision, supervisor/group-meetings, metacommunication, augmented meetings

Description:

Introduction

BA-group retrospective meetings are introduced by the supervisor, and held with a bi-weekly or monthly frequency. The retrospective meeting will take about 15 minutes.

Method

The retrospective meeting is a know concept from the SCRUM software process. Here it is meant as a mean for continuously changing and improving the way a staff of software engineers work in smaller teams.

Similar the process of construction systems and producing bachelor reports can be improved by leveraging on the same formal method. For the retrospective part, a series of per-circulated questions are to be discussed (from spørgeciklen), all dealing with how the students are coping with the process.

Intended Learning Outcomes:

This experiment is focused at one particular Learning Outcome (LO) from the BA-project: "Plan and execute a project in a project group in collaboration with internal and external partner"
The primary LO of this experiment will be, that the students will be in a better position to fulfill the BA-learning objectives.
A secondary LO will be feedback from both student/student and supervisor/student about the progression and potential problems in the project.

	Resources		Tasks		Supports
	Out-of-Class Activities: preparation
	Retrospective meeting introduction	→	Student read the introduction ↓	←	Teacher may make an oral introduction
	Meeting agenda	→	Students prepare via the agenda ↓	←	N/A
	In-class Activity: meeting
←	Resume and actions points	←	Retrospective Meeting ↓	←	Teacher acts as meeting mediator
	Out-of-class Activity: post meeting followup
→	Actions points	→	Follow up on actions points	←	N/A