Re: Is Agile truly scaleable?
"Cass Dalton [email protected] [SCRUMDEVELOPMENT]" <[email protected]> Mon, 11 Apr 2016 12:08:13 -0400
| Newsgroups | gmane.comp.programming.scrum.general |
|---|---|
| Message-ID | <CADA3vVUEO4g4F3+mkUrHf2x0VK5b3fL66tROURNi34mrttuv2g@mail.gmail.com> |
It seems weird to say "The age of Agile will soon be over" and then list a methodology that sounds very much like a good implementation of agile. Most of the issues the author has with Scrum are issues with poor implementations of Scrum. The methodology he describes is so similar to Scrum that I would argue it is a version of Scrum that has been tailored to the organization's needs. The author complains that Agile's focus on the end user is a fault and that "the last person who knows the right answer is the customer." He obviously hasn't seen real, functional Agile in person because it is Agile's empirical nature that directly addresses this issue. Agile is designed to embrace changing requirements and the vast majority of requirements changes come from the customer or end user not knowing what they want. So Agile, in fact, DOES address the issue of customers and end users not being able to articulate what they want. When you work with stakeholders sprint after sprint after sprint, you start extracting the REAL requirements out of the interactions and those real requirements go into the product backlog to be worked. I would argue that the failures he has seen have not been a failure of Agile or Scrum, but a failure of the POs that have been driving the PB. He also implies that agile makes architecture take a back seat to tactical progress. This can be true in a junior or inexperienced team with a short-sighted PO. But a good PO will prioritize with both short and long term goals in mind and a good development team will not create overarching architecture that will just get trashed as soon as the requirements change from the end user not being able to articulate what they want. "Meet the new boss, same as the old boss..." -Cass On Mon, Apr 11, 2016 at 10:49 AM, Nayan Hajratwala [email protected] [SCRUMDEVELOPMENT] <[email protected]> wrote: > FWIW, this topic was cross posted to the XP mailing list a few days back. > Here’s the thread: > https://groups.yahoo.com/neo/groups/extremeprogramming/conversations/topics/160050 > > --- > Nayan Hajratwala - 734.658.6032 - http://agileshrugged.com - @nhajratw > > On Apr 11, 2016, at 4:50 AM, [email protected] [SCRUMDEVELOPMENT] < > [email protected]> wrote: > > > In the last company I worked for, I found Agile to be clumsy and > un-scaleable. Bearing all of this in mind, can it actually be scaleable > (SAFe seems like a flawed mutation of Agile rather than a genuine > solution). This article makes me believe that this could be a better > methodology: Slaying the Agile Dragon: The age of agile will soon be over > <http://goo.gl/Q0h5ye>. What do you all suggest? How do you make it work? > [image: image] <http://goo.gl/Q0h5ye> > Slaying the Agile Dragon: The age of agile will soon be ... > <http://goo.gl/Q0h5ye> > Agile is clumsy, un-scaleable and lacks any appreciation of software > architecture. So why do people worship at the Church of Agile? It is time > for change; Winter is... > View on goo.gl <http://goo.gl/Q0h5ye> > Preview by Yahoo > > > > >