Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Why does the PO have the permissions to do that? Why does the PO talk to the devs at all? POs are suposed to be in contact with some of the design team (I don't know how they're structured), the PM and a couple devs just to validate that what they imagine is possible and to potentially suggest shortcuts or features that play well with the implementation and the PM might not think of.
-
I guess these titles mean something completely different company to company, and as their role is so dynamic a lot depends on how pushy a person is.
-
But in my experience POs are concerned exclusively with features and workflows, and they supplement the PM with a point of view that's much closer to the users' than theirs, as PMs have to think about sprints, dev hours, releases and a ton of other stuff that relativises the feature set and adds weights invisible to the end user.
-
hjk10157313yWe don't have a PM and the PO is part of the team. Planning and direction is his main concern. The business analyst (also part of the team) is even more involved with the users and devs.
-
@vintprox he's very angry with JIRA because it flags scope creep when he tries to add the whole backlog to a sprint
When the Product Owner is so angry about Agile that he removes all the Dev team from JIRA?!?! Then has a tantrum about nothing being delivered.... hmmm... because, mate, we can read your flipping mind!
rant