PO should inspect to see if outcomes have been achieved: Revision history

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

24 January 2024

  • curprev 00:5400:54, 24 January 2024‎ Ppugliese talk contribs‎ 1,195 bytes +1,195‎ 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..."
Retrieved from ‘https://go-else.org:443/index.php?title=PO_should_inspect_to_see_if_outcomes_have_been_achieved’