Blog

Reach Us

Mysteries Of Product Ownership

25 Aug 2016

Myths, Misconceptions & Mysteries Of Product Ownership

Here’s what the Scrum Guide says about the Product Owner Role:
“The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.”

Who is an effective Product Owner in Scrum? Is (S)He a requirements typist, user story writer, business analyst, domain expert, maybe all of the above? What are some effective practices of Product Ownership? What are the biggest myths and misconceptions around Product Ownership?

Five of the most respected Scrum.org PSPO Trainers – Ralph Jocham, Mark Noneman, Erik Weber, Hiren Doshi, and Simon Reindl talk and answer questions on Product Ownership myths, misconceptions and mysteries of Product Ownership.

Professional Scrum Product Owner

06 May 2016

15 things a Professional Scrum Product Owner (PSPO) actually does

15 things a Professional Scrum Product Owner (PSPO) actually does

PSPO_jpeg

The Product Owners – Steve Jobs and Jeff Bezos

  1. The Professional Scrum Product Owner (PSPO) is an Entrepreneur – a value Maximizer & Optimizer
  2. The PSPO sets a solid vision to help the Scrum Team keep laser sharped focus and direction that helps with incremental progress at the end of each sprint
  3. 1 Product == 1 Product Backlog == 1 Product Owner. Having one PSPO for the product helps with the clarity & focus, ensures quick decision making, and single person accountability for the success of the product.
  4. To validate the idea the PSPO frequently releases the increment of software to market to gain real customer insights
  5. The PSPO has the final say on the order of the Product Backlog. The PSPO orders the PBIs in the product backlog by keeping the Value of the PBI, the dependencies between PBIs and the dependencies on the other products in mind.
  6. The PSPO ensures that most valuable functionality is generated all times by the Development Team.
  7. The PSPO accounts for the Return on Investment and Total Cost of Ownership before a feature is built.
  8. The PSPO ensures that all work done by the Development Team originate from the single Product Backlog – a single source of truth.
  9. To determine the value of the product being delivered the PSPO might use metrics like time to market (cycle time / lead time), percentage of the functionality in the released product used by the customers & the overall customer satisfaction
  10. The PSPO is accountable for Interacting and engaging with the Stakeholders.
  11. The PSPO comes to the Sprint planning with a clear business objective in mind and works with the Development Team to craft a sprint goal based upon the forecast
  12. During the actual Sprint the PSPO is accountable for the Product Backlog Refinement, but may delegate the work to the Development Team.
  13. The PSPO  is the only one who can abnormally terminate the Sprint in case the Sprint goal becomes obsolete.
  14. The PSPO Is just one person and not a committee
  15. The PSPO builds trust by closely working with Development Teams. He is not hesitant to delegate the work of writing user stories / Product Backlog items to the Development Team.