Team Decisions

description

Table of contents

• Agile strategies
• Development strategies

Agile strategies

We decided in the team to roughly follow the extreme programming workflow.

@0815Sailsman (and in part @flamion) will mostly take over the role of PM and be responsible for populating the backlog with new issues. Once the team decides, that the todo column of our kanban board is too empty, we will have an IPM and as a team decide which stories from the backlog will be moved to the todo column. In the scope of this meeting, we will also discuss all of these moved tickets and answer any emerging questions regarding them. This ensures, that we always have enough work available as a team.

Development strategies

Testing

We as a team decided to put a lot of focus on testing our application. Especially the Bytecode VM should be tested extensively. If it fits your situation, try to apply TDD. In general, try to unit test more complex logic sections, by themselves, integration test stuff like endpoints, and e2e test larger workflows (e.g. an entire game walkthrough).

Git workflow

When it comes to our git workflow, we try to be relatively flexible. Your as a developer are responsible for deciding, if your current ticket / story / preference requires you to work on a branch inspired by gitflow or not. If you feel confident enough to adopt trunk based development feel free to do that aswell.

Architecture

We want to work with a hexagonal / clean architecture in the backend.

Documentation

Every developer is responsible by themselves for writing javadoc / doc comments in general for their methods and docs in general. Please be thorough with writing docs!