hi Saket, one question. In my previous team I worked for a very less time, I observed while giving estimations by the Development team, the PO (technical guy) pushes the team to reduce the efforts by telling his perspective towards developing the functionality. Say if Dev team says 2 SP, he tells his perspective and tries if it can be set at 1 SP. Now my doubt is why any PO or BA does that? Is there any hidden benefit from business perspective in doing so?
I see this as an effort to clarify requirements, and it is just estimation the reality will come later, and team is experiencing good match between estimate and reality (mean team meets the sprint goal) than its good, else team need to learn how to estimate well.
@@izenbridge I agree it can be seen as an effort to clarify requirement. Can it also be seen as an effort to improve ROI? Will it be better if team make proper assumption based on the outcome from such tasks (Clarity VS Actual effort took for completion)
Very clear and patient Saket. Thank you
Thank you
Thank you Saket
Thank you too
hi Saket, one question.
In my previous team I worked for a very less time, I observed while giving estimations by the Development team, the PO (technical guy) pushes the team to reduce the efforts by telling his perspective towards developing the functionality. Say if Dev team says 2 SP, he tells his perspective and tries if it can be set at 1 SP.
Now my doubt is why any PO or BA does that? Is there any hidden benefit from business perspective in doing so?
I see this as an effort to clarify requirements, and it is just estimation the reality will come later, and team is experiencing good match between estimate and reality (mean team meets the sprint goal) than its good, else team need to learn how to estimate well.
@@izenbridge I agree it can be seen as an effort to clarify requirement. Can it also be seen as an effort to improve ROI? Will it be better if team make proper assumption based on the outcome from such tasks (Clarity VS Actual effort took for completion)