Our mission:

We believe in an open and tolerant society in which each person has the chance to access knowledge and communicate with each other.

Our project:

We are working on a new an intuitive way to use your computer. But wait! This application is different. We try to provide a solution for physically handicapped people to use a computer. One of our main target groups are people suffering from multiple sclerosis. These people are sometimes unable to move any part of their body besides their eyes. So we try to give them back a part of there liberties.

This goal should be reached with the Tobii Eye-X EyeTracker Dev Kit. This is a cheap Eye-Tracker for about 100€ shipped with two different SDKs for C++ and C#/.NET. So we are limited to the Windows Platform. For our project we chose the C# programming language.

These are the conditions we had at the beginning of the project.

At the beginning of this course we invented a own name and logo.

After that we had to gather a lot more information about the later users of our implementation.

First we did a lot of research to get more information about our target group: we brainstormed, wrote our main personas and anti-personas, put them in scenarios and discussed the user stories.

Then - to receive more user specific informations about the behavior of people using the eyetracker - we did a survey, where a lot of people tested the eyetracker and answered the questionnaire. Following we compared the results with our personas, scenarios and userstories and synchronized them with the survey results.

After gathering all the important information, we set up our main concept: what do we want to implement, what's important and what's not.

The next step we did was to make some sketches and mockups for the userinterface of our software. We had to decide which colors, buttons, positions and many more we wanted to use for our implementation.

We decided to make our software modulebased, that means that all functionalities that we implemented should be written as a module, so the user can manage alle the modules in the program: which one should be shown where in the eyetracking-taskbar.

Also, it's easier to add new own modules to the software, because you only need to copy one of the old ones and edit the icon and the executable code which is running when clicking on the module. It will automatically appear in the list of modules then and can be dragged into the eyetracking-taskbar.

After the first draft was finished, we started with implementing the GUI and getting the coordinates of the eyetracker.

Day by day we implemented the modules of the list we set up at the beginning. 

Implemented modules are the following:

• LeftClick-Module
• DoubleClick-Module
• RightClick-Module
• MiddleClick-Module
• Scroll-Module
• Zoom-In-Module
• Zoom-Out-Module
• On-Screen-Keyboard-Module
• Taskswitcher-Module
• Open-Browser-Module
• Settings-Module
• Exit-Module
• SampleConfigurable-Module
• Debug-Module

Week by week we improved the modules and the whole programm. Also we tested it on several machines (with Windows 7, 8 and 8.1).

Every morning we had a standup-meeting, where we mentioned what we did the day before, what we'll do this day and what we think which problems will come up.

Every wednesday we had our review-meeting, where we showed our customer what we've done the last sprint. After that we had a retro-meeting, where we discussed what was good, what was not at the last sprint. In the evening we planned our next sprint.

The last of our sprints we did the last bugfixes, created a poster for our team and recorded a video. Therefore, amongst other things, we invited some (non-IT-)people to test the eyetracking-programm infront of the camera. And we prepared ourselfes for the presentation. 

Now, at the last days of our teamoriented project, we all think that it's been a good chance to learn how scrum works. Or more like:

we learned how to live scrum!