Agile working
We work according to the agile "Scrum" process model in small teams of up to seven software developers. For us, agility means being able to react flexibly to changing internal and external requirements. We are constantly on the lookout for innovations and improvements.
A few advantages of our way of working at a glance:
- Every employee has the freedom to try out new features.
- The view over the edge of the plate is demanded and promoted
- Expert knowledge can be acquired and deepened
- Innovations are recognized, tested and implemented at an early stage
At Scrum, there are three roles that are directly involved in the process:
- Product Owner (set business requirements and prioritized)
- Scrum Master (manages the process and removes obstacles)
- Team (develops the product)
The requirements are recorded, expanded and prioritized in the product backlog. A work package (increment) is taken from the product backlog at a fixed rhythm (e.g. monthly) and processed in a so-called sprint. In the sprint backlog, the current status of the divided work package (tasks) is recorded. In the Daily Scrum Meeting, this work status is compared and discussed in the team. The Daily Scrum Meeting always starts on time and lasts exactly 15 minutes.
After each sprint, the team presents the implemented functions in the live system to the product owner in the Sprint Review Meeting. After the meeting, the new requirements and feedback flow into the next Sprint Planning Meeting and the process starts all over again.
In order to be able to guarantee the quality objectives of our software, so-called Communities of Practice (CoP) have been formed in our IT. A CoP is a group of people. Its task is to discuss and document rules and concepts and to define guidelines within the framework of which and under the conditions of which software components are developed and operated at vit.
The respective expert knowledge is bundled in these CoPs. Every expert can exchange information on his topic and gain new insights. The expert then distributes this knowledge within his team, ensures compliance with defined standards and checks from time to time whether his team adheres to the measures and guidelines developed by CoP.