2974RE: [scrumdevelopment] RE: What to do with "loose ends"
- Mar 11, 2004
> -----Original Message-----I've not got any scientific measurements, but I can report that we
> From: PaulOldfield1@...
> (responding to Karl)
> > My first thought is why are there so many loose ends? As well
> > as looking to catch them before the sprint review, could it also
> > be because the team is commiting to too much in each sprint?
> > What would happen if they commited to a little bit less so
> > there's less of a rush to get things finished?
> Has anybody measured what happens if the team commits to
> less during a sprint? There was a hypothesis that it might
> lengthen the "decompression" time at the beginning of the
> sprint and shorten the rush at the end. This would hypothetically
> give better quality software owing to more time to think about it,
> but you still get the rush at the end of the sprint. If you're in a
> rush all the time, OTOH, then committing to less should help.
consciously decided to plan with a reduced velocity, with the intention
that it would result in increased quality. The perception so far is
that it has succedded.
The other thing we have focussed on to minimise loose ends is acceptance
testing (we're XPing aswell as Scrumming if you hadn't guessed!). This
has reduced the number of false assumptions which the developers make
about the finer details of the expected behaviour.
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 specifically
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately. Please note that the
BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
- << Previous post in topic Next post in topic >>