Re: very long product backlog
This is an interesting discussion but i must say I am very suspicious
about shortening the sprints. It seems to me that everybody wants to
change the SCRUM theories. As a SCRUM master in my company, one of my
hardest jobs, is to tell people, not to start changing theories
before we have a referance plan. Seems to me, everybody at my company
have come up with ideas of how to improve SCRUM. If I would follow
all of them, we would end up with 4 hour sprints, consisting of 2
My most important argument against shortening sprints, is that it
gives the team decreased respronsibilty, which thereby gives
decreased enjoyment, decreased team dynamic and decreased efficiency.
Buisness owners usually wants more control and are worried that the
team can not handle it. I belive it is a SCRUM Masters job to educate
the buissnes, about letting go. Trust the team, they are good and
responsible people. But, if the team wants to decrease a certain
sprint, then I would probably do it for that particular sprint.
SCRUM is a proven method, when you choose to follow the methodology.
I am a beliver of 4 week sprints.
--- In firstname.lastname@example.org, "Karl Scotland"
> > -----Original Message-----
> > From: mintywalker [mailto:mintywalker@y...]
> > Shorter sprints might work really well. It is an interesting
> > idea, as despite seeing Scrum work well, business owners still
> > concern about being able to be highly re-active to short-noticewith
> > requirements.
> > On the flip side, I think we might suffer business owner burn out
> > a sprint review and planning meeting every week.With
> > All that said, one of the business owners already and seperatly
> > suggested 2 week sprints. I believe we have a winner :)
> You'll want to scale back your sprint planning and sprint reviews.
> our 1 week sprints, we've just started doing a combined sprintlonger
> review/planning meeting at 10am Monday morning, which lasts no
> than 2 hours. We've also found that by the time we get to thereview,
> the customer has usually seen most of the functionality alreadybecause
> they've been involved with "Customer Testing", so its more of aprogress
> report for anyone else whos interested, which doesn't take too long.specifically
> BBCi at http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain
> personal views which are not the views of the BBC unless
> If you have received it in error, please delete it from your
> Do not use, copy or disclose the information in any way nor act inthe
> reliance on it and notify the sender immediately. Please note that
> BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
- (responding to Deb)
> Can anyone recommend articles, other references, onIt's probably worth looking at
> Fear and Agile? Of course I'll check Alistair's book first,
> since his slant is always to the people side of things...
> what else?
...look in particular for Inaccurate Risk Perception
but you might find other topics useful. (feedback