Our application developers integrate Graphical Information Systems (GIS) with other ICT systems based on your standard platforms and development tools. To this end, they employ toolsets and platforms supported by Esri:
Each application development is framed within Zachman and is performed based on a custom project methodology (Prince2 or Agile).
Ad-hoc project-leading may seem efficient, but it often results in lower quality, difficult maintenance and delays. SIGGIS, therefore, usually, works according to the principles of the Prince2 project methodology.
Prince2 comprises of a sequence of clearly defined and predetermined project phases. Every phase is fully documented, every development is tested and a complete report of the installation is produced.
The waterfall model is made up of different phases. Every phase has its own level which determines the sequence. The highest level is carried out first and the lower levels follow, just as in a waterfall.

Ad-hoc project management may work for smaller projects but carries extensive risks for larger projects. A Prince2 methodology has been proven to be effective and efficient, but it’s sometimes too rigid. This is why SIGGIS often employs the Agile methodology. Agile is also described as lightweight software development. It’s an incremental methodology where, through iterations, a functional workflow is enriched with new functionalities. Agile is based on these principles:
Scrum is a methodology based on Agile. Cross-functional teams work in short sprints (iterations); the goal is to always produce a working part of the required workflow. Cooperation and communication are key here. The term Scrum was not chosen haphazardly. It’s a reference to rugby, a sport where player try to cross a field by constantly tossing the ball to each other.
In the waterfall method of Prince2, each phase is carried out by specialists. They perform their assigned tasks and hand over the results to the experts of the next phase. With Scrum, however, experts from various phases are grouped together in one team. The “scrum-master” is in charge and holds a “scrum-meeting” at the start of the day. This meeting lasts about 15 minutes and every team member replies to these questions:
After this meeting every specialist continues working on his assigned tasks, always knowing he can rely on the team.