Loading ...
Sorry, an error occurred while loading the content.
 

Re: Agile/Scrum disadvantages

Expand Messages
  • Dave Nicolette
    Ewww! Slimy hands! Dave ... http://kw-agiledevelopment.blogspot.com/2007/09/disadvantages-of-agile-software.html
    Message 1 of 135 , Sep 5, 2007
      Ewww! Slimy hands!

      Dave



      --- In scrumdevelopment@yahoogroups.com, "Henrik Kniberg" <h@...> wrote:
      >
      > >
      http://kw-agiledevelopment.blogspot.com/2007/09/disadvantages-of-agile-software.html
      >
      > Interesting list of "disadvantages" :o)
      >
      > - Active user involvement and close collaboration
      > - Requirements emerge and evolve
      > - Agile requirements are barely sufficient
      > - Testing is integrated throughout the lifecycle
      > - Frequent delivery, and the need to signoff each feature as Done.
      >
      > Challenges? Yes, certainly.
      > Disadvantages? Well....
      > Calling "Requirements emerge and evolve" a disadvantage sort of
      > implies that "You must specify everything upfront" would be an
      > advantage.
      >
      > Sort of like saying:
      > "The disadvantage of having the lethal tumor removed is that the
      > surgeon has to cut me"
      > or "The disadvantage of pulling the leach off my body is that my hands
      > will get slimy".
      > :o)
      >
      > I do get your point though. Many people of a waterfallish mindset will
      > initially *perceive* these as disadvantages, while the real
      > disadvantage is the fact that the transition may be difficult and
      > costly, which we must take into account.
      >
      > Great site BTW.
      >
      > /Henrik
      >
      > --
      > Henrik Kniberg
      > http://www.crisp.se
      > +46 (0)70 492 5284
      >
      > On 9/4/07, kswaters1 <allaboutagile@...> wrote:
      > >
      > >
      > >
      > >
      > >
      > >
      > > My thoughts on question #1 - what are the disadvantages of agile
      > > software development?
      > >
      > > http://kw-agiledevelopment.blogspot.com/2007/09/disadvantages-of-
      > > agile-software.html
      > >
      > > Kelly Waters
      > > http://www.allaboutagile.com
      > >
      > > --- In scrumdevelopment@yahoogroups.com, "Mike Bria" <bria526xp@>
      > > wrote:
      > > >
      > > > For clarity, I'd like to point out that I feel Deepinder has asked
      > > two
      > > > largely distinct questions:
      > > > 1/ What are the /disadvantages/ of using an agile methodology?
      > > > 2/ What are the /potential pitfalls/ when using an agile
      > > methodology?
      > > >
      > > > Some of the responses so far have addressed question #2.
      > > > Some of the responses have addressed an unasked (but good)
      > > question: "What
      > > > might adopting Agile expose about your organization?"
      > > > I don't think #1 (the subject of the thread) hasn't gotten much
      > > airtime
      > > > though.
      > > >
      > > > Does anyone have any thoughts on #1?
      > > > --MB
      > > >
      > > > On 12/28/06, PaulOldfield1@ <PaulOldfield1@> wrote:
      > > > >
      > > > > (responding to Deepinder)
      > > > >
      > > > > > All of you have experience in Agile and Scrum, I would like to
      > > know what
      > > > > > are the disadvantages of using Agile process where all it can
      > > fail as
      > > > > > compared with other traditional processes?
      > > > >
      > > > > Going by reports I've heard rather than any in-depth study; I
      > > seem
      > > > > to hear that while a relatively inexperienced team can do a good
      > > > > job at detecting problems, they are often not experienced enough
      > > > > to change things in a way that makes things better.
      > > > >
      > > > > One way to help counter this is to 'go by the book' for at least
      > > 6
      > > > > months and start to build up experience of what 'going by the
      > > book'
      > > > > can do for you (and hopefully, why it does). Another way is to
      > > get
      > > > > some good, experienced help to make any necessary tweaks
      > > > > and explain why they are good changes to make.
      > > > >
      > > > > Paul Oldfield
      > > > >
      > > > >
      > > > >
      > > >
      > >
      > >
      >
    • Dave Nicolette
      Ewww! Slimy hands! Dave ... http://kw-agiledevelopment.blogspot.com/2007/09/disadvantages-of-agile-software.html
      Message 135 of 135 , Sep 5, 2007
        Ewww! Slimy hands!

        Dave



        --- In scrumdevelopment@yahoogroups.com, "Henrik Kniberg" <h@...> wrote:
        >
        > >
        http://kw-agiledevelopment.blogspot.com/2007/09/disadvantages-of-agile-software.html
        >
        > Interesting list of "disadvantages" :o)
        >
        > - Active user involvement and close collaboration
        > - Requirements emerge and evolve
        > - Agile requirements are barely sufficient
        > - Testing is integrated throughout the lifecycle
        > - Frequent delivery, and the need to signoff each feature as Done.
        >
        > Challenges? Yes, certainly.
        > Disadvantages? Well....
        > Calling "Requirements emerge and evolve" a disadvantage sort of
        > implies that "You must specify everything upfront" would be an
        > advantage.
        >
        > Sort of like saying:
        > "The disadvantage of having the lethal tumor removed is that the
        > surgeon has to cut me"
        > or "The disadvantage of pulling the leach off my body is that my hands
        > will get slimy".
        > :o)
        >
        > I do get your point though. Many people of a waterfallish mindset will
        > initially *perceive* these as disadvantages, while the real
        > disadvantage is the fact that the transition may be difficult and
        > costly, which we must take into account.
        >
        > Great site BTW.
        >
        > /Henrik
        >
        > --
        > Henrik Kniberg
        > http://www.crisp.se
        > +46 (0)70 492 5284
        >
        > On 9/4/07, kswaters1 <allaboutagile@...> wrote:
        > >
        > >
        > >
        > >
        > >
        > >
        > > My thoughts on question #1 - what are the disadvantages of agile
        > > software development?
        > >
        > > http://kw-agiledevelopment.blogspot.com/2007/09/disadvantages-of-
        > > agile-software.html
        > >
        > > Kelly Waters
        > > http://www.allaboutagile.com
        > >
        > > --- In scrumdevelopment@yahoogroups.com, "Mike Bria" <bria526xp@>
        > > wrote:
        > > >
        > > > For clarity, I'd like to point out that I feel Deepinder has asked
        > > two
        > > > largely distinct questions:
        > > > 1/ What are the /disadvantages/ of using an agile methodology?
        > > > 2/ What are the /potential pitfalls/ when using an agile
        > > methodology?
        > > >
        > > > Some of the responses so far have addressed question #2.
        > > > Some of the responses have addressed an unasked (but good)
        > > question: "What
        > > > might adopting Agile expose about your organization?"
        > > > I don't think #1 (the subject of the thread) hasn't gotten much
        > > airtime
        > > > though.
        > > >
        > > > Does anyone have any thoughts on #1?
        > > > --MB
        > > >
        > > > On 12/28/06, PaulOldfield1@ <PaulOldfield1@> wrote:
        > > > >
        > > > > (responding to Deepinder)
        > > > >
        > > > > > All of you have experience in Agile and Scrum, I would like to
        > > know what
        > > > > > are the disadvantages of using Agile process where all it can
        > > fail as
        > > > > > compared with other traditional processes?
        > > > >
        > > > > Going by reports I've heard rather than any in-depth study; I
        > > seem
        > > > > to hear that while a relatively inexperienced team can do a good
        > > > > job at detecting problems, they are often not experienced enough
        > > > > to change things in a way that makes things better.
        > > > >
        > > > > One way to help counter this is to 'go by the book' for at least
        > > 6
        > > > > months and start to build up experience of what 'going by the
        > > book'
        > > > > can do for you (and hopefully, why it does). Another way is to
        > > get
        > > > > some good, experienced help to make any necessary tweaks
        > > > > and explain why they are good changes to make.
        > > > >
        > > > > Paul Oldfield
        > > > >
        > > > >
        > > > >
        > > >
        > >
        > >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.