Why couldn't his be B or D?

Last post 05:35 am October 31, 2015
by Ian Mitchell
3 replies
Author
Messages
03:51 pm October 28, 2015

I took the Product Owner Open Assessment and missed only the following. I chose "D" after deliberating between "D" & "B". Could anyone expand on why "B" is the better answer?

How does an organization know that a product built through Scrum is successful?

Correct answer: B)
You chose: D)

A) By measuring that velocity has increased since the last release

B) By releasing often, and updating key performance indicators (KPIs)
on value after every release and feeding this information back into
work on the Product Backlog

C) By measuring the actual time spent on development versus the
time estimated for development

D) By the Product Owner and stakeholders accepting the Increment
at the Sprint Review

Your input is much appreciated.

04:15 pm October 28, 2015

Hi Phillip,
I would suggest that it is only after the intended audience use the product and feedback does the understanding of value be realised.
Until that point there is an assumption that you are building a good thing. If the stakeholders and PO are happy, that is great - now they can test the assumption.
How many movies bombed as the audience didn't like them?
Can you think of any product that just confounds you how it got in to the public domain?
The assumption that they were going to be used wasn't tested.
Hence, B is the better feedback to rely on.

Thanks
Simon

04:16 pm October 28, 2015

The PO orders the Product backlog with incomes like estimate of effort and ESTIMATES of business value.

At the Sprint review, the PO and stakeholders have an accurate view of the current state of the product, they observe that the process is actually delivering "something" as expected, but they still don't know if the Scrum team is building the right product.

Only after the release to the market can the PO collect effective datas (KPI) on the true value of the product.

05:35 am October 31, 2015

This question is about empiricism, and why it is important in Scrum. Acceptance of an increment in a Sprint Review is not empirical evidence of its suitability or success; it is merely a decision to release into an environment where such evidence may be obtained.