06

The goal is [to] prepare them for reality.

We give them two lectures on Scrum with the same content. The first Scrum-lecture we tell them how it all works. The second Scrum-lecture happens after the first sprint. And we give them the exact same information again, just expressed differently. And I often got the comment: 'Why didn't you tell us earlier?' I did, but now you know. So show, don't tell. That is everything here.

This was the concept of the course from the beginning.

You can do one team per day, so it takes you two weeks full-time to do all. [...] And the week before you're reading all those peer reviews, so you have a month where you basically don't do anything else. [...] You want to take everything into account, and you can only do that at the end. That is the big problem.

This really is the most important aspect of the course: you always assess the process. A good process leads to a good product anyway.

Most of the time it results in the grade we intuitively feel, but we see why and we can explain it too.

Comments are missing in places where they are needed.

They started testing early (sprint 1 or 2).

Reliable presence in the group common room, Attendance of group meetings, Participation in group meetings, Attitude in group meetings, [...], Attitude in the development, Working as a team, Fair division of labour, Pair programming, Helping others