8:30 a.m.
Arrival at the office, first coffee, brief overview of topics and messages from emails and MS Teams.
9 a.m.
Discussion with developer colleagues about projects and private matters.
9:45 a.m.
15-minute “daily chat” with everyone in the coffee kitchen. In English, of course. ;-) Our “Scrum Master” asks us three questions: What did you do yesterday? What’s on the agenda today? And: are you having any problems? Everyone has a chance to speak and, if possible, show his work live on the screen.
10 a.m.
Discussion with the developers about the architecture of our latest app. What is the development status of the mobile app? When will the new features be ready? When can we start the tests?
11 a.m.
Feedback from the back-end services: Is our new data lake finished? What will be included in the release? What features are truly important? At times, such discussions can get heated on a specialist level.
12 p.m.
Lunch. Anyone who wants can join the group in the canteen. After that it’s time for a brief round of table soccer.
1 p.m.
Grab a cup of coffee and go over the overall architecture with our Scrum Master Paul: What will we put in the new release? How could changes impact the architecture and the back-end?
2:30 p.m.
Next meeting: Planning the next sprint. We break down the status into tasks at hand, combine them with user stories and include everything in the next sprint. This enables us to keep an overview.
5:30 p.m.
Finished. The day can last longer or start earlier if we have to talk with our colleagues from the United States and Japan.