I am considered a technical product owner however, looking at the amount of times my "user stories" and requirements get pushback from my Architect I am wondering whether being a technical product owner is a "real" thing and if so, maybe I am misunderstanding what it is about.
So could someone help clarify what is to be expected of a "technical product owner" if this really exists?
Just looking for some guidance/help here.
I am a PO for system-to-system API's.
UPDATE: I have come to understand there is no such thing as a TPO, however the way this company is setup and the phase they are in with regards to adopting agile helped me understand why my "position" was necessary.
To be able to translate customer needs related to "business logic" that needs to be implemented (i.e. retention policies on data based on domain, necessary filters and the design of the API itself)
To analyze feasibility of functional feature requests taking our integration layer into consideration (we do not only deliver API's we also created the integration between source and target system)
To help identify and manage any issues related to the source systems delivering the data as these are very functional in nature.