Initial Analysis

It all starts with project estimation and design phase. We work with you to understand your key drivers in terms of time, cost and functionality, clarify your requirements, and convert that into a functional and technical design. These are the blueprints of the new application.

A methodology driven by time and budget

During the build phase, Ibuildings typically uses an Agile based approach. We combine Scrum and XP methodologies to ensure rapid progress and that delivery fits your business needs. In most cases, the time and budget are fixed, so you can rest assured that there will be no nasty surprises with regards to the deadline and the ultimate cost.

The methodology is not based on desired functionality, as functionality often changes during the course of a project. Instead, possible changes are immediately compared against the original functional and technical designs to get an idea of how the changes would affect original planning. This method encourages both you, the customer, and us, the developers, to focus on mission-critical requirements. The key advantage is that you can count on the project being completed on time, within budget and of the intended quality.

Step-by-step development

With an iterative development process, you will always be up-to-date on the progress of your project. Your web application is developed in steps, and after each step, you will see a finished sub-application that you evaluate with us. There are three advantages to this approach:

• New insights and priorities can be incorporated into the project during later development stages.
• You might not always know in advance precisely what the application will look like. Thanks to the step-by-step approach, you will have a much clearer idea of how the application will look like well before the end of the project.
• Our development approach is highly collaborative. During the development process, you become part of the development team. The closer we can work together, the better the final product will match your expectations.

Test-driven approach

You would not want your web application to go live before making sure that it works just as it's supposed to. That's why our development process is test-driven. Before starting to build functionality, we write the test procedure we wish to perform. As soon as the functionality is ready, the test is automatically run.

Documentation

When the project is finished, you will receive a clear set of documentation detailing all you need to know about your new application. During the development process, both the functional and technical designs are adjusted as soon as any changes occur. This way, documentation on the application architecture is always up-to-date, allowing us to implement new changes and enhancements easily.