Sprint Length
Hi guys,
Can someone help me understand the following statement?
The length of a Sprint should be Short enough to be able to synchronize the development work with other business events.
Thanks
Robb
Id guess having smaller sprint cycles enables you to create usable increments quicker and the impact on business value can be accessed faster.
Perhaps if you have longer spirits, you work on larger items that are more complex and harder/longer to adapt to change if there is a change in business events or decisions.
I'm new to scrum, currently studying for the exam, so someone may have a bigger answer for you
Business events are not necessarily synchronized with sprints. Examples include the start and end dates of financial reporting periods, academic timetables, statutory deadlines, contract end dates etc.
The shorter a sprint is, the shorter the gap is likely to be between delivering an increment and a business event which has a dependency upon it.
Thanks Maurice.
@Ian, does that mean that if we have shorter sprints then we can deliver quicker increments for a business event that has dependency on this sprint?
May be. Please note that alignment with the business event is just one of the criteria.
It depends on how much risk the organization is ready to take while staying away from their customer - 1 week vs 1 month. How much is appetite of the organization towards Inspection and Adaption?