There is only one Scrum, as Bas says. There
are many ways to fill in its blanks to optimize productivity and ROI, but those
vary with each situation. I may implement Scrum differently if there is
hardware and software involved, if there are various levels of engagement
throughout the enterprise, if the engineers are more or less competent –
but it is all Scrum.
Ken
From:
Sent: Saturday, July 28, 2007
11:05 PM
To:
Subject: [scrumdevelopment] Re:
Scrum Evolution: Type A, B, and C Sprints
Sorry, realized I forgot to say a couple of things. One of the
reasons type C scrum can be so important is that it can result in
fewer projects taking place at any one time. True, working on the
most important thing will add a lot of value, but working on fewer
projects can have the teams be more efficient because people aren't
thrashing so much by switching between projects. There are also
fewer dependencies (technical and otherwise) when fewer projects are
in place at any one time. This may be very obvious why what I just
said is true, but if it isn't I would point you to Mary and Tom
Poppendieck'
Concept to Cash.
Or ask me - but I am trying not to discuss Lean too much here. ;)
Alan Shalloway
CEO, Net Objectives
Gold Sponsor, Agile 2007
Offline 
Send Email