2.0 KiB
Meeting 1
Quoted text will give you extra pointers to how an agenda should look like
Opening
Here you check if everyone is present
Approval of the agenda
Make sure everything that needs to be discussed is in the agenda or add it if something is missing.
Points of action
The items below are things you should look into after the meeting. During the meeting you can divide (some of) the work between the team members, so that everybody has something to do afterwards.
Your TA will you for the meeting. Note down all other questions that you have so that you can ask them then.
- Create a planning and convert it to GitLab issues
- Discuss a cake rule: If you are late or not there at all, you have to bring cake (or something similar)
- Create a readme with your names, a picture and your personal development plan
- It is your job that you and your team contribute (equally)
- If there is a problem it is your responsibility to notify the TA
- Things to research:
- Scrum (See Brightspace)
- Why should you use it?
- What is a scrum master?
- How are you going to use scrum in the team?
- How will you document the sprints? (tip: templates)
- Schedule for taking notes and chairing
- Git (See Brightspace)
- How does it work?
- What is branching?
- Maven (See Brightspace)
- What does it do?
- How do you add a library to the pom file?
- Have you set the team id?
- Code structure
- How will you use packages?
- Database options
- Json
- Gson
- Jackson
- SQL
- Plain text
- Json
- GUI
- JavaFX
- IDE
- Eclipse
- IntelliJ
- Scrum (See Brightspace)
Any other business
If anybody has something that should be discussed but came up with that after the agenda was finalized (in point 2), he/she should bring that up now so that it can be discussed after all.
Question round
If there are any questions, now is the time to ask them.
Closing
Now you can start working on the project. Good luck!