03

Students often look forward to it very much, when it's an open-ended assignment. It provides extra motivation.

Of course you can also do that with something that's not your own idea, but then you often need a stakeholder to see what they think of it. And now it's more: 'What do I think we need for this?'

[To prepare students for a larger] software project where they work with a group of 10 for a client. This way we have a line in the bachelor where they first do our [smaller] project and then have a big project at the end.

This was already the case when I followed the course, some eight years ago.

I think the main challenge is in grading students fairly on their weekly performance and also giving students the impression that they are assessed fairly in that way.

Sometimes it feels like we don't sufficiently assess the product.

In my experience, it is the case that in the end the average generally matches [the grade] you think the student should receive.

- Description and use cases: complete, detailed, aligned with the rest - Features, MoSCoW and components: matches description, appropriate and specific

- General polish, language use, and images: clarity, readability, visual appeal

If you have two teams that score close together, then it can happen that you do think like 'well, but this team did slightly better than the other, so they get slightly higher.' And sometimes it can happen that you're a bit in between categories. I think that in practice many do just copy the suggestion, but...