www.MemoryGym.dk (backend)
| Lotte Facer Eliasson | lott4328 | GitHub Profile |
| Mikkel Olsen | mikk39k3 | GitHub Profile |
| Jakob Agger Johannessen | jako894n | GitHub Profile |
| Hannan Ahmed Mohamad Noor | hann7575 | GitHub Profile |
| Dan Viktor Jørgensen | danx8076 | GitHub Profile |
- 3 Static Web Apps on Azure to host frontend for each branch.
- 3 Web Apps on Azure to host backend for each branch.
- 2 Repositories. One for backend + one for frontend.
- 1 VM on Azure to host a containerized MySQL database using Docker
Our branching strategy incorporates several key elements commonly used in collaborative software development.
We use the 'main' branch as our released codebase. For new developments, we create feature branches from our development branch. Once a feature is complete, we initiate a pull request to merge it into the 'development' branch. This triggers automated builds and tests via GitHub Actions, and if successful, the changes are deployed to Azure Dev Web App service. When the sprint is complete, we deploy our successfully deployed development branch to our staging branch for further testing. When customer accepts the changes, we merge staging into main.
Key elements in strategy
- Main Branch (live production)
- Staging Branch (pre-production)
- Development Branch (continous development)
- Feature Branches
- Pull Requests (Approval required from another team member)
- Continuous Integration (CI) with GitHub Actions
- Deployment with Azure Web App Service
- Merging Staging into Master
- Daily Scrum Stand-up at 9am
- Workdays: Monday - Friday
- Work hours: 09:00 to 16:00
- Location: Online or KEA
- Customer Meetings: Tuesdays - Exact time to scheduled no later than the preceding day.
- Agenda to be shared at least the day before the meeting.
- Everyone should be punctual.
- All members are expected to come prepared, having reviewed the agenda and any related materials.
- Primary Communication Channel: Discord
- Secondary Communication Channel: Smoke signals / Telepathy