The Product Owner of a city building-permits portal adds a “one-click plan markup” experiment to the Product Backlog. What must be explicit on that item for it to be an Evidence-Based Management experiment rather than just another feature request?
Select an answer to reveal the explanation.
Short Explanation
An experiment without a target is just a feature in a lab coat. Tie the backlog item to the Key Value Area and goal it is supposed to nudge, and say how you will know. Otherwise the team ships markup tools and still cannot tell if permits got any healthier.
Full Explanation
Under Evidence-Based Management, Product Backlog experiments exist to test a hypothesis about a goal and a Key Value Area—Current Value, Unrealized Value, Time-to-Market, or Ability to Innovate. Naming the KVA, the goal, and the measure makes inspection possible after the Increment. Architecture prescriptions, unconditional T2M promises, and frozen annual outputs turn the item back into a feature factory request. The Product Owner should make the intended KVA movement explicit so learning, not just delivery, is the point.