Re: Scrum V Waterfall decision tree
- I would just like to say thanks for all of the replies to my post. As always it is great to get opinions and feedback from more experienced Scrum users than myself, thanks for the help but don't think thats the last time I will pick your brains:)
--- In email@example.com, Jeff Anderson <Thomasjeffreyandersontwin@...> wrote:
> My clients ask me to do this all the time, problem is you are asking
> the wrong question.
> First ground whatever method you can choose from in common principles.
> Next I recommend looking at your various context of you project and
> determining whether various practices can help (ambler has something
> called the agile scaling model which is pretty good)
> Going pure agile or waterfall isn't realistic, you will likely end
> up with different hybrids of the two for different situations.
> On 3/4/10, mattspottiswoode <mspottiswoode@...> wrote:
> > Currently pilotting and moving to adopting Scrum within my organisation, all
> > so far has been successful and I have got some backing from the top to
> > progress further. However we have some way to go before all would be
> > comfortable to use Scrum on everything. I have therefore been asked to
> > create a decision tree that we would use at each project startup to
> > determine whether we should run that development using Scrum (further pilot)
> > or Waterfall. I can think of some local reasons why we would still choose
> > our traditional method over Scrum which are relating to where we have not
> > yet understood how to use it within certain project types but I wondered if
> > there are any more general reasons why an agile approach may not be the
> > choice. Oh and by the way I have a long list of reasons why to use Scrum but
> > I am trying to maintain some sort of balance. Any ideas?
> Sent from my mobile device
> Jeff Anderson