Meeting 2026-06-09

• Course leadership: are we happy with the current team of two?

We are open to add a third person, from NBIS or NAISS. We will look for people ourselves and we'll discuss our favorite candidate.

• Should we transfer the repo to https://github.com/NAISS-Training?.
• R: Against. Keep the repo where it is, as it does not benefit teaching to change URL.
• Should the course be script-first or package-first?:
• RB: Script first, as there is no literature that recommends using a package
• Should we publish the Zoom URL in private repository?:
• RB: yes, as this rewards the people that do prepare
• Should we invite more teachers?.
• RB: yes. I suggest to invite former course participants
• How to evaluate? RB is unsure that the way Retrospects are done follows the literature; and feel it is mostly done on gut feeling. RB can be convinced on the idea to do a formal evaluation like this, but has never found the formal rules of it, nor has found a book on this so.
• RB: follow the formal Retrospect rules, or use regular daily anonymous evaluation.
• Specify course goal again: it was decided to be 'Give an understanding of formal principles of software development'. Teaching at the (Bloom) 'Understand' level does not call for a project to Apply it, hence RB suggested to discuss with the team to remove the project. However, the team decided to keep it. This means that we teach at the Apply level
• RB: the course goal should then be: 'Apply formal principles of software development'.
• How often should the course run?
• RB: twice a year