gistfile1.txt

Business value and MMF
    ======================
    You should discuss the “In order to” part of the feature and pop the why
    stack max 5 times (ask why recursively) until you end up with one of the
    following business values:
  
    * Protect revenue
    * Increase revenue
    * Manage cost
  
    If you’re about to implement a feature that doesn’t support one of those
    values, chances are you’re about to implement a non-valuable feature.
    Consider tossing it altogether or pushing it down in your backlog. Focus on
    implementing the MMFs (Minimum Marketable Features) that will yield the most
    value.
  
    Outcomes and bottom-up scenarios
    ================================
    The value provided by a system is what you can get out of it – not what
    you put into it (Chris Matts said that). Just like the value is expressed at
    the top of a feature (In order to…), the value should be in the steps of a
    scenarios too, more precisely in the Then steps.
  
    When you’re writing a new scenario, I recommend you start with the
    formulation of the desired outcome. Write the Then steps first. Then write
    the When step to discover the action/operation and finally write the Given
    steps that need to be in place in order for the When/Then to make sense.