A user story says that a product must be very fast. During the demo, the Product Owner is dissatisfied with the speed of the product. The most likely reason that this occurred is that the user story was:
a) not descriptive of the value.
b) too large.
c) not estimated correctly.
d) not testable.
My initial thought was 'what does fast mean?' - was that defined? The term fast is relative; and subjective.
Seemingly the answer would be A - not descriptive of the value, aka, 'fast' is not defined. One could say D (not testable) as a result of A (not descriptive). How do you test if it is fast if fast is not defined? Saving Changes...
I agree with Andrew, as in user stories the requirements are to be clarified in detail as possible.If the Product owner had specified the speed criteria like after submitting the required data the page should open in 5 secs.( my projects are web based so this came to my mind)
I too agree with Andrew and Rajesh for option A,
We cannot define fast, there has to be some parameter which could be used for defining the word,
Similar, you cannot define either intensity. Saving Changes...
I am looking at Vinod, and it seems that he is in the health care industry. Generally speaking, Andrew is correct, however, I think Vinod, is addressing an environment in which he is dealing with, in defining the term "Not very fast." I could be wrong, but that may explain the nature of question.
I have bean heavily involved in product development and management, and I wrote about this topic also.
Still the term "Very Fast" has to be clearly defined. However, as stated by Soali, the acceptance criteria is the reference. Saving Changes...
I am looking at pure Scrum theory, in Agile Scrum Methodology User Story characteristics are Independent, Negotiable, Valuable, Estimable, Small, Testable (INVEST). So I think D is the right answer here. eg: If user story says 100GBps speed, it's testable, estimable & negotiable too. I agree with "descriptive value" in broader PM point of view. Saving Changes...