Daily Scrum: daily time-boxed event of 15 minutes, or less, for the Development Team to re-plan the next day of development work during a Sprint. Updates are reflected in the Sprint Backlog.
I found this in the glossary, is it true that daily scrum can be less than 15 minutes if the team has nothing to say. I really thought that this event is a fixed time box event and cannot be shortened for lesser weeks sprints. kindly enlighten me.
A time-box cannot take more than a fixed amount of time. What that fixed amount of time is actually set to be may depend on the length of the Sprint. In the case of a Daily Scrum it does not depend on this, and it can never exceed 15 minutes.
However, like any time-box, there's nothing to stop people from finishing the event before the time-box expires. that's what is meant by "15 minutes, or less" in this case.
I am confused on what is the right answer now to this question, i thought its daily scrum otherwise. I think the rule is to conduct the daily scrum for 15 minutes but in reality nothing stops the team to finish this off early.
Which of the following events cannot be shortened?
- Daily Scrum
- Sprint Planning
- Sprint Retrospective
- Sprint Review
They can all be shortened in the sense that a team can finish early, and not take up the entire time-box.
The time-box allowed varies for all events except for the Daily Scrum, which is set to a maximum of 15 minutes. In other words the 15 minute maximum never changes, but teams can still finish a Daily Scrum early.
The answer to the question is the sprint. If the development team complete the work in the sprint backlog before the end of the sprint time-box, the PO would select another item(s) from the top of the product backlog for the dev team to begin work on.
Yep, looking at the question it should be Sprint. Once a Sprint begins its duration is fixed and cannot be shortened and lengthened, this is from page# 7 in Scrum guide :-)
Rest all can be closed as soon as the purpose is fulfilled, before the timebox expires.
Once the sprint starts the timebox itself cannot be shortened or lengthened, but the team can still finish the planned work early. They don't *have* to do any further work during the remainder of the Sprint timebox once the Sprint Goal has been met.
The immediate line after what Sanjay has quoted answers this question
The remaining events may end whenever the purpose of the event is achieved.
It should be Sprint as per the Scrum Guide as it cannot be shortened or lengthened
@All - by any chance if this is the question from PSM I assessment, then please confirm the answer...
Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content.
The purpose of the forums is to cultivate understanding of the implementation of Scrum through the sharing of insight, knowledge and experience. They are not a source for specific answers to our Professional-level assessment questions. We do encourage you to use our forums as they were intended, and wish you the best in your continued learning of Scrum.
Enjoy your day!
I would say, that correct answer is 'none' unless we know more about Sprint. ( Is it running sprint or future sprint?)
It is not prohibited change duration of Sprint if it is not running but it is advised to have consistent duration.
All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved
If the correct answer is 'Sprint' than 'Once a Sprint begins' would be unnecessary and Sprint would have forever fixed length. So I think that 'none' is correct and if there should be some answer than question need adjustment.
The reason 'Once a Sprint begins' has been added because you don't have to follow a fixed duration of Sprints e.g. you can have all Even Sprints of 4 weeks and Odd Sprints of 3 Weeks :-)
Scrum doesn't force you on that but its more as a guideline/best to follow the consistent duration of Sprints during the development effort
In the (hopefully rare!) situation where your Sprint Goal becomes obsolete or otherwise untenable, the PO also has the option of cancelling a sprint early. I'm not sure if this would be considered "shortening" the event, but it is another scenario where a sprint could conclude prior to its originally-planned end date.
This is termed "abnormal" termination of a sprint. So should not be looked at as a shortening of the event as the other events by definition are allowed to be finished before the time limit.