Principles - psit4-lamas/PSIT4-LaMaS GitHub Wiki

KISS: Keep it simple, stupid

To reach the goal of a working set of core features at the end of May, things are kept simple. This helps to keep the code easily maintainable and extendable for features that arise during the development process and may be desired in the future.

Boy Scout Rule

It is every team members responsibility, to refactor and “clean” the program code while working on it. This will help to improve the quality of the code during time. Additionally, team members can learn from the changes others made to the code and improve their own skills.

JED: Just enough documentation

The development process shall be documented in a way that enables new developers and stakeholders to understand the application’s intent and its architecture. However the documentation has to be concise and limited to key aspects to avoid redundancy.

RDUF: Rough design upfront

We will create a rough high-level design early that will be refined during the project.

Continuous Integration and Delivery

CI/CD are used to discover and address issues during the development process from early on and avoid integration issues in later development phases.

Git workflow

The Git-Flow model will be used as defined by Vincent Driessen.