Working as an IT professional

We use a specific process – the Scrum process – in the software development phase.

In the first step, we collect information on the product requirements of our customers. After that, we hold discussions to determine which tasks can actually be carried out – and in which period of time. Then we launch the iteration phase, which we refer to as a «sprint»and which lasts anywhere between one and four weeks. The «sprint» is a key element in the development cycle.

We also hold a «Daily Scrum» meeting for no more than 15 minutes in which we exchange information on the current status of development projects. These meetings focus on three questions that apply to everyone:

• Which tasks have you completed since the last meeting?
• Which tasks will you be working on between now and the next meeting?
• Are there any problems that are preventing you from completing your tasks?

At the end of every sprint, the team has a neutral and objective discussion about what went well and what needs to be improved. In this and other ways, the team organises itself, and all members are jointly responsible for completing all tasks.

Scrum doesn’t just describe a development cycle; it also utilises agile principles. The following four agile principles serve as the foundation for our collaboration:

1. individuals and interaction are more important than processes and tools;
2. functional software is more important than comprehensive documentation;
3. continual cooperation with customers is more important than contracts;
4. openness to change and the courage to accept it is more important than following a plan.