> "Agile development" just means not complaining when the specs change. > > It's a mind game managers play with developers to keep them thinking > moving targets are "normal" and "good" when in practice they are not.
There's some truth to that. But basically any development methodology can be corrupted and perverted by management (and all are, at one point or another). Agile has several manifestations. One is in a shop that does lots of little, discrete jobs, and for this the "textbook" agile w/scrum is actually a very good approach. For the development of new large systems, however, other variations are needed -- the rigid adherence to textbook examples will lead you astray. Oddly, for the new large system situation one of the important things is to delay as many decisions for as long as possible. Net-net is that development is an art. There is no formula, just some attempts at imposed structure that are worse than others. And you need an artist at the core of the design, one way or another -- having a bookkeeper do the design is always a recipe for disaster. On May 26, 3:55 pm, Greg Donald <[email protected]> wrote: > On Wed, May 25, 2011 at 6:58 PM, Indicator Veritatis <[email protected]> > wrote: > > But quite a few other people have complained -- with no less evidence > > -- that Agile methods have failed to deliver on their promise. > > "Agile development" just means not complaining when the specs change. > > It's a mind game managers play with developers to keep them thinking > moving targets are "normal" and "good" when in practice they are not. > > -- > Greg Donald > destiney.com | gregdonald.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
