Output vs Outcome

In your other post you identified the following KPIs:

1. Team velocity

2. Rolled over / carry over user stories 

3. Burndown / Burnup 

4. Improvement Item - Kaizen 

5. Release Cycle time 

6. DRE: Defect removal Efficiency

These are output-based. An outcome-based assessment might be:

- whether the Sprint Goal was met

- whether an hypothesis was validated

- whether an investment was recouped

- whether customer retention improved

etc.

In French, the translation for output and outcome is the same (= résultat) :-(

I understand output = "raw numbers (velocity...)" and outcome = "impact (business value...)"

ah I think I am able to differentiate in my head now :) 

thank you 

Anu

ok, I got a question - not sure if fits here but let me ask away

How do we asses the outcome for individual teams if there are lets say 10 teams working on one product. 

Here, the sprint backlog items for each team comes from one single Product backlog.

How do we asses the outcome for individual teams if there are lets say 10 teams working on one product.

Why would you want to?

As i understand outcome directly relates to collective effort by individual team

please do correct me if am going wrong here. 

Outcomes relate directly to business value. For example if a Sprint Goal is met then that outcome would be just as valuable irrespective of how teams self-organized to achieve it.

We used to have some of the outcome based assessment points (highlighted by Ian) covered in a review from our client at the end of a release which would finally say how many points we scored out of 7

My question is if it is a good idea to have outcome based feedback more frequently or there should be no such feedback from the stakeholders to the scrum team and this point is best left to the product owner who is anyways working to maximize the value of the work done and hence maximizing the outcome

Output: team velocity during sprint was 300% the average from previous 10 sprints.

Outcome: stakeholders were delighted, and the development team all handed in their resignations.

My question is if it is a good idea to have outcome based feedback more frequently or there should be no such feedback from the stakeholders to the scrum team and this point is best left to the product owner who is anyways working to maximize the value of the work done and hence maximizing the outcome

Note that the Scrum Guide says the following in regards to the Sprint Review, which is held every Sprint:

Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next

I like this movie :) It explains the difference very well:)

https://www.youtube.com/watch?v=AbzVjVdQUx8