Quality

Through adequate documentation of the source code and the technical requirements and concepts, the interchangeability of developers and the ability to optimize, revise, and extend the software are significantly improved.

Consistent object-oriented programming helps to abstract less important (private) information and behavior, and by defining streamlined interfaces, it lays the foundation for reducing complexity and improving quality, extensibility, and maintainability. This also includes:

• Compliance with name conventions both in the source code and in the database
• The correct mapping of relationships/relations between objects (referential integrity, connected objects)

A clearly structured database design with correct mapping of the relations and maintaining referential integrity is essential for the fulfillment of a quality minimum claim and the creation of effective software development. Aside from that:

• Compliance with name conventions
• Optimizations regarding performance and redundancy (normalization - but also denormalization)

The "operation" of the software regarding the implementation of changes and extensions should also be as simple for developers as possible. For this purpose, techniques for creating a project internal frameworks can offer good support, which in turn also has a positive effect on quality.

Not only in larger teams, the procedural model of agile software development "Scrum" has proven itself in practice. Scrum is a continuous process to improve quality, efficiency and customer satisfaction.

Intelligent task management to avoid malfunction and the manufacture of clear communication, which is known to be of crucial importance not only for larger projects: The specification known from conventional software development is called "Product Backlog" in Scrum.

It contains the requirements for the application to be created in list form, whereby the individual items of the list are prioritized according to the customer's business value. The degree of detail of the product backlog increases with higher priorities, i.e. at the beginning of development,

the requirements do not necessarily have to be specified down to the smallest detail. This creates space for changes to the specification, which is known to only result during development. What is contained in the Product Backlog is determined by the Product Owner.

This channel all requirements of other interested parties (stakeholders) to the development team, so that the development team has only one contact person on the subject of "what" is to be developed. The "how" (how should the requirements be fulfilled by software) is only decided by the Development Team.

The development is organized in so -called sprints, this is a unit of time, usually from the duration of a month in which a potentially deliverable release of the software is created. Within the sprint, the Development Team processes a lot of items from the Product Backlog. There is a planning interview at the beginning,

A presentation date and a retrospective at the end. A decisive advantage of Scrum is that false directions in the development process and other grievances can be recognized relatively quickly (transparency) and can be removed. The "encapsulation" of the development team creates a dynamic of our own,

which can be very beneficial for the project. The role of the Product Owner and the Product Backlog creates clear communication and the opportunity to focus on the most important thing. You can find more information in the scrumguide.