Hacker News Reader

Comment by sam_lowry_ | Hacker News Reader

You may consider "product owner" a term, but I take these two words at face value.

Product owner is the person who can make decisions on product features and the development priorities.

Whether they actually arrange the backlog or fire orders or participate in aparté meetings with analysts who then pass the outcomes into the backlog is not essential.

View on HN

Yes, and i have seen teams working entirely without a formal backlog of user stories. Some use a large wall chart, some use a User Story Map without any kind of Scrum of Kanban process... in some teams this also works.

well, this seems detrimental to a discussion because as far as I know the term "product owner" was coined by SCRUM and has therefore a defined meaning other than say Product Manager...

Just checked the Scrum.org glossary definition for Product Owner and found no mention of Backlog.

A glossary definition? Try instead with the guide: https://scrumguides.org/scrum-guide.html#product-owner

Heh ;-)

The guide is says pretty much what i say. "How this is done may vary widely across organizations, Scrum Teams, and individuals."

OTOH, The humane, real-world understanding of the word "product" and the word "owner" coming together should prime over whatever definition there is, because none reads definitions except for the purpose of an argument ;-)

No, i'm not even sure if you're arguing here in good faith. The next sentence after the one you cited clearly states with examples: "The Product Owner is also accountable for effective Product Backlog management"

Reply on news.ycombinator.com