Sprint Length Determination for new product
Who determines the length of a sprint for a new product development project? Is it PO?
Based on what factors it is determined. And who are all involved in this?
> Who determines the length of a sprint for a new product
> development project? Is it PO? Based on what factors it
> is determined. And who are all involved in this?
The purpose of a Sprint is to maximize product value, on a certain cadence. From your reading of the Scrum Guide, who is most likely to care about Sprint length from that perspective?
Who is most likely to temper this expectation, by bringing in concerns regarding technical delivery?
PO is the most appropropriate person to care about the sprint length, because he looks to maximize the product value through sprints.
For any concerns, SM will bring it to PO based on DT inputs. But final say is PO.
Is my understanding correct?
> For any concerns, SM will bring it to PO based on DT inputs.
Why wouldn't the Development Team collaborate directly with the PO on this matter?
> But final say is PO.
Why would any one role have a "final say"? Isn't there an essential balance to be struck between the timely release of business value, and the technical ability to deliver that value?
Ok. I understand now. It is the SCRUM TEAM's collective responsibility.
For first sprint,
PO will express his desired sprint length from customer value stand point.
DT will express this from technical ability.
ST will facilitate it.
For next sprints,
It is preferred not to change the sprint length. However, during sprint retro it can be discussed as needed.
thanks for your time.
Correct.
Thanks Ian.