---
# System prepended metadata

title: Final prezzy

---

# Final prezzy

## Technical challenges

> What were the technical challenges you faced during the development? What went easier than expected or was harder than expected? Give a team top 5 of technical things you learned. Don't forget to mention any achievements you made that are not directly visible in the prototype or that do not seem hard at first but turned out to be. If you do not mention it, we will probably don't know about it. 

Easier than expected:
- End-to-end testing web application
- For (almost) everything there exists a package
- Making simple UI with flutter

Harder than expected:
- Unity integration and business logic with flutter
- Loading Models with textures at runtime efficiently
- Finding a good test strategy for the web app

Top 5 learned:
1. Constantly searching for the best framework and adapting to it. (kafka, grafana, keycloak, dbs, 3d model viewer, ...)
2. The importance of testing
3. The importance of backups
4. Fully automated build pipelines using Jenkins
5. Learning to communicate with customers (museums)

## Group work challenges

> What were the group work challenges you were faced with? What went easier than expected and what was harder? How did you organize yourselves (in term of meeting face to face or online, hackathons, ...)? Give a team top 5 of group work things you learned. 

How did we organize ourselves?
- Stand-up meeting 3x a week
- Retrospective + planning on monday after each sprint
- 3 subteams instead of everyone working on anything

Easier than expected:
- Collaborating with a large group
- Keeping everyone motivated
- Quickly getting help from teammates

Harder than expected:
- Stopping when a feature/UI is 'good enough' (also UI)
- Coordinating releases of multiple repositories and multiple inter-dependencies.
- Making decisions that influence multiple subteams / communications between subteams

Top 5 learned:
1. It is impossible to be expert in everything, defining subteams and roles is important
2. Code reviewing
3. Pair programming 
4. Issue management using JIRA
5. Combining different code writing styles