As the BVA Auctions software development crew in Amsterdam, we are organized in several multi disciplinary Scrum teams. We are self-managing and shape our own workplace. This Tech Blog is one of our own initiatives because we are proud on what we do and like to share it.
It’s fun to work here. Pair programming is normal and knowledge sharing is standard behaviour. We are fully responsible for the online platform 24/7 and continuously adding new features. We write our own automatic tests, have an automated deployment pipeline and choose the tools we like.
We use Scrum as our collaboration process and have sprints of 2 weeks. No fake Scrum, we follow the rules as how it is meant to be. There is a great Product Owner with mandate who sets the priority and understands technology; we really like to work for him. Of course we have a full-time Scrum Master as well. He supports us and protects the atmosphere. Even though we have sprints of two weeks, this does not mean we deliver features to production every 2 weeks. We deploy as often as we can and because of this we demo most of our features to the business on production. Our retrospective meeting is important and we really want to learn from each other.
The auction platform is very stable; something we are proud of. We maintain real hardware in two data centers. Team atmosphere is relaxed, people are dedicated and responsible. We trust each other and provide team members with all access they need.
Transparency is key. We easily share successes and mistakes: no blame, but support from colleagues. We are communicators, like discussions and respect each other’s opinions. No hierarchy levels: no architect or lead role; just show your experience about the subject and convince your colleagues.
We work in a steady flow and do not believe in overtime. Quality first and craftsmanship. There is also time for a personal chat.
We like diversity and have team members originated from many countries. Below you will find an overview of current members and their (core) role. This does not mean however that for instance a developer only does some coding! We love DevOps and developers help system engineers… well, we all help each other.
- Andrii Stoialtsev (back-end developer)
- Arpit Agarwal (DBA)
- Bas Schoone (back-end developer)
- Bunyamin Yildirim (front-end developer)
- Chris Watts (back-end developer)
- Daniel Rijkhof (back-end developer)
- Davide Arrigo (front-end developer)
- Deepthi Shetty (back-end developer)
- Faisal Afzal (back-end developer)
- Geert Nijpels (system engineer)
- Harrie Hoogeveen (back-end developer)
- Hemalatha Moorthy (back-end developer)
- Janneke Verschoor (back-end developer)
- Joram Visser (back-end developer)
- Jorrit Siebelink (front-end developer)
- Kristian Moynihan (back-end developer)
- Marcel van den Brink (back-end developer)
- Mario R. (front-end developer)
- Marius Malis (system engineer)
- Mohammed Laachir (back-end developer)
- Mourad Ahayan (back-end developer)
- Nikolai Matviiets (back-end developer)
- Roelof Knibbe (back-end developer)
- Samuel Fernández Muñoz (back-end developer)
- Thierry van Benten (user experience designer)
- Tijn Lambrechtsen (system engineer)
- Victor Kachan (front-end developer)
- Vincent te Beek (cro/web analyst)
General Scrum roles
- A. Pluim (Product Owner)
- Paul Sanders (Agile Coach)
- Rosa van Rooijen (tester)
- Steven de Kater (tester)