The conference reception for Human Centred Software Engineering yesterday was at the KTH Visualization studio.
We got the possibility to try different Virtual Reality Games. Of course I tried all available devices!
The visit also included a 3D planetarium demonstration with an extremely interesting presentation of the possibilities of technology.
Very cool indeed!!
If you ever get the chance – go there and try it! 🙂
Today we presented our paper Responsibilities and Challenges of Product Owners at Spotify at the Human Centred Software Engineering Conference at KTH in Stockholm. The paper is written together with Sigurhanna Kristinsdotti and Marta Larusdottir.
The Product Owner is responsible for the list of requirements and the work in the team together with the Scrum Master in the context of agile development.
What did we do?
In 2014 we did a study at Spotify. They have used agile development since 2006, and they focus much on usability as their slogan is “It’s easy”. Spotify reached 39 million subscribers in 2016!
The main research questions in the paper were:
- What are the main responsibilities of the Product Owners
- What are the challenges of a Product Owner, and how does he or she cope with them?
What did we find?
- Most of them found it hard to mesure the value when developing new features
- Some Product Owners use the number of users as their main parameter of success
- To lead the vision was a difficult responsibility that Product Owners struggled with
- “I think it‘s important that the POs see to it that the team has a vision – that they know what it is – but i don‘t thing it is solely the PO who creates that vision, I think that the team does that together, but the PO is responsible for having it.“
The visions needs to be understood and appreciated by the teams, and the product owners do not want to use their authority to make decisions:
“You can ususally see when the team has set the goals as a whole rather than the goals being delivered from someone else.“
The main results
The Product Owner role is very diverse. The challenges are many, and the job is very multifaceted.
The Product Owners need to have one foot in the daily work of the Scrum teams, and one foot in the future.
We have developed a new method for including the user perspective and the user’s digital work environment in software development.
The method is an adoption of the persona’s method where work environment aspects are included, and can be used when designing or procuring IT systems.
The method describes the holistic uses situation of a person with the 10-20 different IT systems that are used at work. It is based on a well known theory by Karasek and Theorell regarding control, demand and support in relation to stress.
For further reading see our book chapter on the topic. It is published in a Springer book.
Our book is now in print! 🙂
The editors are: Cockton, G., Lárusdóttir, M., Gregory, P., Cajander, Å. (Eds.)
Addresses the problems inherent in combining UCD with agile software development