Agile

What is the best way to build a website? After almost 10 years of experience in the Internet world, we think we might know the answer. More importantly, we apply our answer in daily practice: make ideas tangible as quickly as possible. It is only when you make an idea concrete that you can see if it works. And then you have all the time you need to make adjustments.

Agile Manifesto

The Agile Project Method from Indivirtual originated from the 'Agile Manifesto'. This was the result of a reaction to the classic "waterfall" product methodology, with one phase preceding another. The Manifesto argues for a totally different approach: look at software development as a dynamic, iterative process instead of linear and static. Work out ideas, test them, go back to the drawing table is the motto.

Cooperation from start to finish

How does a project look when it follows Indivirtual's Agile Project Method? Each time part of the website is ready, we submit it to our client. It could be a certain functionality, or a HTML version of the home page. The client can respond directly with what he feels needs to be changed, and which adjustments should take priority. Other iterations are also taken into account. Cooperating on this level with the client helps us arrive at end products which actually satisfy the expressed preferences and expectations of our clients.

Four golden rules

1. Individual and interactive instead of procedures and tools
We work with motivated, independent project teams. The core principles are daily personal contact, open communication and personal responsibility.

2. Working website components more than detailed documents
A functioning website or application is the only serious way to measure the progress of a project. Earlier versions help us to detect and neutralize any project vulnerabilities.

3. Cooperate with clients instead of negotiating contracts
Future users of a website or application work as intensively as possible with the Indivirtual project team. This produces the best results and the highest degree of acceptance.

4. React to change instead of follow a plan
Even in the final phase of a project, major changes may be required. To react quickly to these challenges, we emphasize architecture, design, quality, and above all, simplicity.