There are some fundamental laws of software economics that should drive executive-level decisions about business and product strategies. It’s easy to forget them, or decide they don’t apply to our special situation. (Gravity’s not just a good idea, it’s the law.)
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.