“When I was then able to acquire another project myself during my project time, all these areas that I had been responsible for benefited me. The new project was about automatic on-board network testing and I was allowed to take over the management. So I was a product from day 1 Owner, Scrum Master, Coordinator and Project Manager.”

The first project of his own is doing well and more follow, Thomas also likes to remember the night shifts when it was stressful, getting together with colleagues after work and watching juniors how they develop further in the project work.

Summing up his work as a product owner, Thomas says: “It’s better to ask twice than to go astray once. It doesn’t matter whether I’m starting a new project or taking over in the middle. I ask, ask and ask until I understand everything. Then I make sure that everyone involved has understood the same thing. At the beginning of the project you can set the rough goals, but that is only an approximate direction. Monthly, detailed check-ups with customers and developers are needed to find out “What is the goal” to be defined more and more.”

Thomas has learned that as a product owner you are responsible for a product, but comprehensive communication is still the main task.

“I can only expect good work if I have formulated the tasks well, made sure that everyone understands what needs to be done and that everything is properly documented. If I describe badly, I will get bad code back. Communication is everything.”