it is based on the Impact Mapping & Value Requirements model to improve the team's focus on value

Delivering value is the priority of agile teams. One of the principles

• “Our highest priority is to satisfy the customer via early & continuous delivery of valuable software”.

This principle sets the focus on delivering value to customers

• Value from the customer’s point of view is the benefit they think they will get
• The focus on customer value has led to measuring and tracking value delivered with user stories
• User stories are great for many reasons, but a user story is focused on a small set of stakeholders: A user story describes functionality that will be valuable
• Sprint Reviews lacks stakeholders, maybe because having the wrong discussions
• The discussion should address the value of all stakeholders not just customers

Questions for all

• A Product Owner may have the following value questions
  • Are we solving the right problem?
  • Are we building the right solution for that problem?
  • Are customers willing to pay for it?
  • Can I make money developing it?
• For a customer, value questions could be
  • Does it solve a problem I know I have in a better way than my current solution?
  • Does it solve a problem that I didn’t know I had?
  • Am I willing to use it?
  • Am I willing to pay for it?
• A stakeholder could be interested in
  • Am I making the right investment?
  • Am I reaching my stakeholder objectives?

various levels of outcomes and outputs: another definition of value and progress

<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> MODEL

We believe that if we implement [Product Outputs], the [Persona-WHO] will be able to [Product Outcomes], so we can achieve [Business Outputs], which will help the business to achieve [Business Outcomes]

• List of Team Outputs (CONCRETE FEATURE(S) )

• [Meassurments]

• The Business Level

• Persona-WHO

• The Product Level

• The Team Level

• [Meassurments] will let us know if the: </aside>

• Example - Airline company

  • Business Outcomes
    • increasing ticket sales in the current customer base with a 20% increase in revenue
  • Business Outputs
    • increase in the sales under frequent flyers from 10M to 12M
  • Product Outcomes
    • happy existing customer – save time and complications to book again
  • Product Outputs
    • Usability: increase the ease of rebooking
  • Team Outcomes
    • Usability: increase the ease of rebooking
  • Team Outputs
    • the potential solution ‘Auto-rebooking’ functionality
  • You now have linked the experiment of developing ‘auto rebooking’ to the expected business outcome of 20% increase in revenue
  • All you need to do now is quantify all the outcomes
  • Sprint Review you can discuss
    • how much product value you added by measuring Usability
    • after shipping your Increment, if an increase in Usability results in an increase in frequent flyer sales
    • if the business objective is significantly impacted
    • You can now measure progress towards different stakeholder values and have informed discussions in your Sprint Reviews about them