Role proposals

The team-structure and organization of the teams is up to the teams. However it may make sense to define areas of responsibility.

To give you some hints on which areas could be relevant for you, please consider:

Area	Description	Change
Team Coordination	Would be a part of a typical "project-management"role in the real world. Mainly invites for meetings, makes sure, that everyone has all relevant information, moderates meetings	You can rotate the role, but the role should stick e.g. two weeks with one person. Or you define it from the beginning. Please note: A project manager is not a "presenter", he or she is usually quite good in communication, but never should step into areas he or she is not responsible for.
System-Engineering and Configuration Management	Usually the configuration management takes care of documentation (that people document) and that all the traceability is available, and gives a framework for the digital twin. Here, it is mainly about keeping confluence clean and structure the team's matlab model.	You can try without this role. But if there is anyone who wants to take it, it will help your team to stay focussed and structured. This role is highly dependent on the full support of every team member, otherwise it is highly frustracting.
Discipline responsibles	You will probably have areas of software/logic, mechanics and electronics in your digital twin. You do not need to define it from the beginning, but sooner or later it may make sense that an area is taken over by one or two people to structure	If once assigned, keep it there. Classically mechanics is usually a little bit by iteself, whereas electrical and software topics may be covered by the same people for small projects
Weekly Presenter	There will be a topic each week where you need to present on for five minutes	Change this role depening on the topic each week. Everyone should present ideally twice during the course.