On time and on budget
We do this without making concessions to the intended quality. By effectively steering on scope and budget in close cooperation with our client, we achieve the right balance.
Assured Delivery
Our agile process is an important foundation of what we do and something that we have continuously developed since 1999 into what it is today.
We call this Assured Delivery: a scrum-based process for successful software development for your business. On time and within budget. Maintainable and future-proof.
Maintainable and future-proof
Only a well thought-out software architecture ensures maintainability and flexibility in the future.
Pragmatic Scrum Process
We say ourselves that we are Scrum-pragmatists, not Scrum-purists.
We believe in an agile approach such as Scrum because it ensures the involvement of the client throughout the project, gives room for progressive insight and interim adjustments and facilitates continuous improvement of the joint process.
What matters to us is making use of those advantages in order to achieve the best possible result. It is not about executing the process according to the letter of the manifesto or some scrum manual.
Project approach and phasing.
Every project starts with a high-level design phase from which an estimate of the scope follows. Based on this, a detailed budget can be determined and a planning can be made. Subsequently, in different iterations parts of the application are developed and delivered.
When all required functionality is realized a final User Acceptance Test follows. Once the final touches have been made, the application can be taken into production.
Monitoring quality
Developers at Ibuildings know that delivering software is only possible if you can do so with confidence. And you can only deliver with confidence if you are convinced of a high degree of internal and external quality.
During development, developers continuously run a test suite with unit tests for the majority of the written code. This ensures that what is delivered works, and that future changes do not affect existing, working functionality.
In addition, there are integration tests that automatically check whether communication with external services still works as expected.
Finally, developers write automated acceptance tests. This ensures that the application as a whole demonstrably does what it is supposed to do and supports the desired use cases. All test suites and code analysis tools are run in the development environment and also on an external environment.