21370RE: [scrumdevelopment] Re: Sprint Review and Planning Process
- May 4, 2007Good day Petri,My experience has been fairly inline with your own. I believe that there are many variables that play into this; team maturity with Scrum, Product Owner needs, technology advances, expansion of good development practices, more supportive organizations, etc...Chris Sterling“Experience is easy to provide and quickly put to good use by people with all the other qualities." - Dee Hock
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of petriheiramo
Sent: Friday, May 04, 2007 3:43 AM
Subject: [scrumdevelopment] Re: Sprint Review and Planning Process
--- In scrumdevelopment@ yahoogroups. com, "myoungtai" <myoungtai@. ..>
>four weeks (i.e. one month).
> Sprints are
I'm actually curious how common are the 4-weeks sprints, as suggested
by Scrum. In our company, I can only think of one project out of quite
a few that have felt that four weeks might be good for them (or to be
more precise, they have felt the two-week sprints were a little too
short). In most cases, two weeks have been considered good, and then
there are some very innovation intensive projects that have used
one-week sprints and felt them best for themselves.
Any more comprehensive experiences?
Process Improvement Manager
- << Previous post in topic Next post in topic >>