A customer approaches the product owner with a new requirement and asks for a rough estimation to implement it. The outline of the task would be similar to a prior deliverable.
What should the product owner do to properly inform the customer?
A customer approaches the product owner with a new requirement and asks for a rough estimation to implement it. The outline of the task would be similar to a prior deliverable.
What should the product owner do to properly inform the customer?
In an Agile project, the best approach to provide a rough estimation for a new requirement similar to a prior deliverable is to revisit the user story of that similar requirement. By learning about its story points and considering the team's velocity, the product owner can sketch out the time needed for the new requirement. This method relies on relevant historical data and the team's prior experience, which ensures a more accurate estimation.
I am torn between B and C. I suppose as "product Owner" is mentioned, we are in an Agile project. As WBS is more of a predictive tool, we want to chose the answer with the more agile tool, hence the user story and velocity in answer C.
Agree, C seems to be the logical answer.
C is the answer
C. Revisit the user story of the similar requirement, learn about its story points and velocity, and sketch out the time needed for this requirement. Explanation: Revisiting the user story of the similar requirement and using its story points and velocity provides a more accurate estimation for the new requirement, based on the team's prior experience and performance. This approach ensures that the estimate is informed by relevant historical data.
Revisit the user story since we have information available of previous deliverable