==== Team work ====

== Use Agile Methodology ==
Break your project into small, manageable tasks (sprints). Regularly review progress and adjust plans as needed.

==Define sprints==
A sprint is a period in which a work is done to reach a final product. Before each sprint, it is decided what the final product should look like. We suggested defining daily sprints.

==Stand-ups==
Stand-ups are short explanations of each team member of what their work will be for the foreseeable future. This ensures that the whole team is up to date and that no time is wasted due to misunderstandings.

==Assign Roles and Responsibilities==
Clearly define who is responsible for what. This helps prevent overlap, ensures accountability, and plays into every team member’s strengths.

==Use management tools==
The use of management tools takes saves significant time, which is highly important in the amount of time available for this project.

==Trello==
[[https://trello.com/|Trello]]\\
Trello allows you to categorize User Stories, such that members can assign features to implementers and the progress status of features can easily be viewed. This takes some of the mental load off the leader's shoulders and provides a reference for all team members.

==GitHub Projects==
[[https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects|GitHub Projects]]\\
GitHub Projects is a feature that helps you organize and manage tasks, issues, and pull requests within a GitHub repository, providing a visual way to track progress and collaborate on projects. It allows you to create task boards, automate workflows, and prioritize work efficiently. This assumes some knowledge about GitHub, so it is only recommended if the whole team has experience with git.