I have a role that combines the role of product owner with a role of software architect. I have final say for both product and technical decisions:
The Product owner role is similar as in scrum: I get requirement from my customers; I manage the product backlog, decide the priorities, decide which feature/requirement goes in which release. In a word I decide the product roadmap (of course, not alone but together with the team).
My role of software architect is to make the most important technical decisions. For example, I decide which tech stack for frond-end, whether to use nodejs or php/laravel for back-end, and design the most important database designs.
This situation is the reality in my company. As far as I know this kind of combined role is quite common, especially for start up company. I came cross this answer from quora, described the similar role at amazon too "On some teams, there are no Product Managers, and the Dev Manager owns both the product/business and the technology."
Like every practice, it has pros and cons. One of advantages of taking these 2 roles together is that I can know whether a requirement is feasible or not or whether a feature is too big to be done in a single development cycle. And to delegate and work with the team is the key to do both roles right.
However both roles are time-consuming and availability of both are required for the team to operate well. How should I split my time between both roles? Is there any best practice?
- I'm not asking for scrum compliance or advices not to do this because it is the reality in my company.
- I asked related question "Is there a well established name/title for a role taking the technical and product ownership together in the software industry?" at workplace.stackexchange.com because I felt that question was more workplace related. Too bad it was closed but I got 2 answers worth reading.