Skip to main content
Back
X
Back

Scrum Forum

Sprint starting point and ending point

Last post 02:01 pm January 9, 2014
by Anonymous
7 replies
Author
Messages
11:57 pm December 29, 2013

Hi,

What is the sprint starting point actually? will it be the Sprint planning session-1 or immediately after the conclusion of Planning session 2 ?

Thanks

03:46 am December 30, 2013

A sprint starts immediately upon termination of the previous sprint, assuming there was one. A sprint is a container for all of the other Scrum Events including Sprint Planning.

08:11 am December 30, 2013

So I understand a sprint starts with Sprint planning meeting and concludes with Sprint Retro.

Tnx

05:22 am December 31, 2013

You got that right Mouli.

02:17 am January 2, 2014

So I understand a sprint starts with Sprint planning meeting and concludes with Sprint Retro

source : book /software in 30 days published 2012, chapter 5, page 60
"...If you are going to proceed with another Sprint, building more increments of software, a Sprint Retrospective is held."

Is my interpretation correct?
If we run for example the last sprint or the sprint is cancelled by Prod. Owner then we have a sprint with review meeting but without a retrospective meeting.

03:58 am January 2, 2014

When a sprint is cancelled, it should end with sprint retrospective meeting.

It is the last and important event for a sprint and should be held whether sprint is cancelled or not
it holds more value in case of sprint cancellations

05:47 am January 2, 2014

> Is my interpretation correct?
> If we run for example the last sprint or the sprint is cancelled by Prod. Owner then we
> have a sprint with review meeting...

Correct. When a Sprint is cancelled, or indeed on the last Sprint, there must be a review of any work done and remaining.

> ...but without a retrospective meeting.

The Scrum Guide does not mandate a retrospective for cancelled sprints or for the final one. However, it would certainly be good practice to hold a retrospective in either case, since Scrum Team members have a duty to the wider organization and should carry forward any lessons learned. I'd be more inclined to call this inspection a Project (or Product) Retrospective than a Sprint Retrospective, because the remit is different and it isn't "official" Scrum.

This is on top of other non-canonical retrospectives that may be attended even if a team folds, such as Joint Retrospectives (between collaborating release teams) and a Retrospective of Retrospectives which may be held at a Scrum of Scrums level. These are not necessarily held at the conclusion of any particular Sprint, but they should still be held as close as possible to a Sprint boundary.

02:01 pm January 9, 2014

The Sprint start and end dates are published for e.g a 4 week sprint could be Monday Jan 13 to Friday Feb 7. Sometimes its not feasible to hold the planning meeting on Monday @8.00AM and retrospetive at Friday . You could do them on monday afternoon and retro on thursday but still have the sprint start and end on Monday and Friday.