PO should inspect to see if outcomes have been achieved

From go-ELSE
Revision as of 01:54, 24 January 2024 by Ppugliese (talk | contribs) (Created page with "__NOTOC__ The PO should focus on the results that the product is achieving, focusing on individual behaviour change in product usage and have meaningful measures that illustrate progress towards business and product outcomes. This principle is moving the emphasis from measuring team(s) output to measuring the impact of their collective efforts against business value indicators. === Evidence/impact === * The PO, together with relative Teams, has established a system o...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The PO should focus on the results that the product is achieving, focusing on individual behaviour change in product usage and have meaningful measures that illustrate progress towards business and product outcomes.

This principle is moving the emphasis from measuring team(s) output to measuring the impact of their collective efforts against business value indicators.

Evidence/impact

  • The PO, together with relative Teams, has established a system of measurement mostly focusing on the impact their development is generating (“outcome”)
  • While output metrics might be used in some cases, they should be used as a way to give an indication of the progress towards business and product outcomes.
  • Focusing on outcomes is an effective strategy to reduce waste
  • Typical Tayloristic-age metrics have been abandoned: amount of hours worked, velocity, …
  • Outcome measurements require reaching outside the product development organisation, hence there will be several means implemented to collect outside feedback

Related Principles

  • Joint Sprint Reviews
  • Modern product management practices to gather customer feedback
  • Lean Startup
  • Beyond Management