Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, Estimating, Scrum
Please choose the right answer.
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 choice is d) not testable
Sort By:
Page: 1 2 next>
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?

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)

So the answer is A ....
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.
Option A.
The acceptance criteria should state the range of acceptable values.
I also agree with Andrew, A would drive the value and D would test to ensure A was achieved.
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.
I am in between D & A ... I agree with Andrew.
I agree with Andrew. The answer would be A. A good user story should describe a specific value first. And then, it should be measurable.
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.
Personally I would go for A, unclear specification, what is fast for one might be slow for an other. You need a clear spec.
Andrew comment on A and D is excellent
Page: 1 2 next>  

Please login or join to reply

Content ID:

"I think popular music in this country is one of the few things in the twentieth century that have made giant strides in reverse."

- Bing Crosby