Usually this starts with an Analysis of the business process and definition of the system requirements. According to the project complexity, onsite visits may be performed in order to have detailed information on project scope, deliverables, functionalities and timelines. Use cases are developed at this point and along with the Software Requirements Specification document they should establish the basis for the agreement on what the product is intended to do.

The Design phase includes functional, graphical design, technical and database designs, workflow diagrams. Technologies evaluations are made in order to help defining the right tools and programming libraries that will be used in the implementation phase. We work hard for a reliable, re-usable, extendable and maintainable design. Detailed reviews are to be made with the client.

We know the risks of an Implementation phase started before previous phases are done. We have done this before as a natural urge of a developer to write code but we also recognize the pitfalls and we enforce a discipline for all our projects. When coding, we follow Extreme programming practices such as: unit testing first, collective code ownership, code reviews. Focus on quality and self-documenting code is a must, but also documentation using tools such as Wikis.

Testing is a must on every project as we strongly belive that "code not tested does not work". A key principle is to have this process defined in a clear test plan. This is to be executed by individuals others than developers or designers of the system. Bugs are logged using a specialized tracking system and, for each bug, an acceptance test is written in order to later validate the fixing of the bug.