How we work – Agile
Our customers should see fast, tangible results, whether in smaller projects or major ones. From the very outset, we want to build trust through transparency, regular feedback and calculable outlay. From our earliest beginning, we have therefore worked on agile principles.
Agile project organisation using Scrum and Kanban
The methodology we use to successfully achieve our goals can be described as a "philosophy of rapid steps": an iterative, incremental style of development. The principle of "rapid steps" works systematically with small modules, complete in themselves, each of which delivers a tested, workable result. This solution grows and is refined further with every iteration, constantly taking into account user feedback.
Requirements change as the project progresses.
Change requests are part of every IT project. Our approach therefore takes them into account throughout the duration of the project, with decisive benefits for our customers. There are no major projects involving waterfall or big-bang methods: instead we use "rapid steps" with short timelines (2 weeks, for example). The rapid steps deliver immediately appreciable results with assessable outlay (time and costs) and low risks. Every step creates a viable version with genuine benefits. This systematically prevents any "rude awakenings" at the end of a project.
Project control through fine-grained communication
Translated to our daily business, this means that we work in 2-3-week sprints using daily meetings and backlog management. This allows fine-grained project management and ensures the teams maximum productivity. Unproductive work is prevented by transparent and fine-grained communication and by real-time control, reaction and optimisation.
Analysis, architecture and prototyping
Our experience has shown that sound analysis and a clean architecture enable users requirements to be successfully implemented for the long term. Every long-term concept must be brought to life in the short term. "Seeing is believing" - using prototypes to physically demonstrate a function is much more effective than any paper-based description. Prototypes enable you to actually see exactly how a solution will work. They therefore provide a solid foundation for both internal and external decision-making.
I look forward to hearing from you!