AGILITY & SCRUM

How We Work

We work with Scrum

Agility derives from the Latin word “Agilis” and means “skillful, nimble, swift.” We want to follow this principle – especially in our software development. We have recognized how important it is to adapt quickly and without bureaucracy and to respond rapidly to changes. This allows us to seize more opportunities, build on our strengths, and better navigate challenges. Our quality management serves as an effective and supporting pillar in this process.

What agility means to us?

• We want to truly understand you and genuinely inspire you.
• Our focus is on customer satisfaction, quality, and speed.
• We want to work more closely with you and develop software for you that you actually need.
• We promise to respond to changes together with you and not just follow a plan.
• We strive to continuously improve.
• Together, we want to open new perspectives and think about the future today.

SCRUM

Scrum is defined by a set of rules, roles, and meetings that enable a team to deliver product increments within two to four weeks. Specifically, this means that after each development interval (the so-called sprints), following a certain onboarding phase, a real working software version is available, which subsequently gains steadily in functional scope. Which functionalities are implemented, and with what priority, is agreed jointly with the clients after each sprint.

All project participants, both on the contractor’s and the client’s side, have complete transparency at all times regarding the current development status as well as possible obstacles. Through the possibility of short-term changes to individual subtasks and/or their prioritization, the project course can be adjusted at any time. This means that elaborate change requests are, as a rule, a thing of the past – the project result corresponds to the current requirements at that time.

The following essential characteristics are relevant to the Scrum approach:

• Joint definition of a product/project vision
• A fixed contact person as a link between client and development team (Product Owner)
• A specially trained process manager/coach (Scrum Master) who accompanies the team throughout the entire project
• Joint creation of a task list (Product Backlog)
• Joint prioritization of individual tasks (User Stories/Tasks)
• Discussing, estimating, and planning individual subtasks for the next work cycle (sprint, 2-3 weeks) as a team
• Implementation of individual subtasks in the development team, accompanied by daily team meetings
• Joint review of the sprint result (product increment)
• Continuous analysis and reflection on the approach, combined with the goal of steadily improving it