What is GiPHouse?

GiPHouse is a virtual software company of the Radboud University Nijmegen, which has already been active for more than 25 years. GiPHouse is entirely run by students and is divided into two parts, which run independently from each other in the spring and fall semesters.

Our activities

During every first half of the calendar year (spring semester), GiPHouse develops software for paying customers. These projects are completely developed by students, who get credits for successfully participating in the courses that are linked to GiPHouse. Working on these projects is the main focus of the courses. Project teams usually consist of six to eight engineers (bachelor students) and a one to three project managers (master students).

During the second half of the calendar year (fall semester), a master about beginning a start-up course is given. In this course, students are tasked with developing software around a central theme. This software will hopefully be the start of a real start-up, which could go on even after the course is finished.

For students, working for GiPHouse is a perfect opportunity to get some real-life experience as a software developer, as a project manager or with creating a start-up.

Spring semester
Fall semester

Time division and documentation

Besides developing the software, we also expect students to spend time on team meetings, meetings with their customers, writing documentation and other important project-related work.

For the spring semester, we expect students to

For the fall semester, we expect students to

The students are usually free to choose their favourite programming language and platform, barring client wishes. Most students have experience with C++, Python and Java but other languages could also be an option.

At the end of the spring semester, the customer has to judge the quality of the product and the team-customer collaboration. The final grade for the course is an average of the customer judgement and a judgement of the teachers.

GiPHouse Structure

Within GiPHouse we simulate an actual corporate experience, we will try to explain the structure of the organization below. At the bottom of the page is a graphical representation of this structure.


Although the teachers do not have a concrete function within the organization, they are crucial for the courses surrounding GiPHouse. The teachers are responsible for the course material and the grading of the students.

Executive Board (Student Assistants)

GiPHouse is ran by the student assistants involved with the courses Software Engineering (SE) and Software Development Management (SDM). These students are responsible for the acquisition of projects and trying to ensure the success of every project. The board deals with most issues that the directors can not deal with and takes care of the contact with the teachers to ensure a smooth experience for students of the combination of the course and the company.

Directors (Students SDM)

The directors aid the student assistants and the teachers in keeping track of the progress of the teams. This means the directors will keep track of the progress of the various teams through reports and interaction with the managers of the teams. This progress is then reported to the executive board of GiPHouse through reports and discussion of all the teams. One pair of directors is responsible for several teams on which they will report, the other teams are covered by different director pairs.

Managers (SDM Students)

Every team has two or three managers whose responsibility it is to manage the project. The managers are responsible for the documentation for the directors, ensuring the expectations of the clients are managed correctly and steering the agile development process.

Engineers (Students SE)

Engineers are responsible for the code that is delivered at the end of the project. Aside from creating the features the client desires, they are also responsible for eventuel documentation and the testing of the code.


For employees the general approach to take when a problem arises is to contact the person that is one layer within the organization above you (e.g. engineers contact managers and managers contact directors). If this does not solve the problem or there is an issue with the person one layer above you, then you contact one layer higher.

For clients we recommend contacting the managers when a problem emerges. If the problem lies with the managers or contact with the managers is not fruitful, please contact the directors.

Organizational chart