8
leste
3y

So I have this PO who is able to understand technicalities. He is also able to use postman and has access to our code - don't ask why. He is trying stuff out with our apis, looking through code to understand parts of the software, etc.
So there are two sides of having a PO who is able to understand us devs on a certain level:
On the one hand you can explain why story x is taking longer than expected. You can even discuss in a proper way, which is nice. On the other hand is he a bit over the top: when we plan stories he already analysed everything, put code into the story and is telling us how to solve an issue or implement a story.
The sad part is that none of my colleagues seem to be bothered by the fact that he is doing my work.
And recently i even heard a sentence like: "I do not understand why this story should have 3Sp. Would be way lower when I do it". Well.. then do it yourself freaking idiot.
That goes so far that he tells other teams how to fix their code when there is an issue, because he has access to the code and can (unfortunately) read it..

Very unpleasant. :/ So: do you guys have/had the same issues? Am I overreacting?

Comments
  • 4
    Oh, he definitely must be in your or your subordinates' position to propose such engineering solutions first. Decline everything.
  • 6
    Yeah, do it yourself, you idiot

    No. You are not overreacting. I have had such people annoy me. It is easy to convince they are wrong once you reveal the details and explain. It is hard to invest time into helping them understand they are wrong but once they are proved wrong, it is easier subsequent times
  • 3
    When something like that happens and he/she is wrong, I only explain how I'll implement and what he/she is wrong with the time they will give just a suggestion. Sometimes I got good ideias from them, but its rarely, try to use they suggestion as a small tip, to start the task. So, try always to show why you implemented something, with details, as boring as you can 😅 they will think two times before do it again
Add Comment