Completing a three-post skills model for product owners, partly borrowed from product management… For some projects, product owners need market-facing skills as well as core agile practices (release/sprint planning, story writing, prioritization, backlog grooming). They *may* need to tell economic stories, segment users, design incentives and take a portfolio-level view.
Rich: I’m a product manager writing PRDs, but my features are always de-prioritized when engineering allocates resources. (We have constrained engineering bandwidth). How can I get priority for my features so that my PRD will see the light of day?
— Generating Reams of Unfunded MRDs and PRDs
Basic product owner descriptions assume a best-case situation: clear sponsor/user alignment, obvious project value, willing subject experts, budget authority and rational expectations. What skills do product owners need for real world projects?