Greg, changing requirements is not a mind-set of managers, but it's a reality of life. High-tech market is very dynamic and if you want to adhere to original specs you'll soon go out of business. Seriously, do you think that managers are happy when the original specs change, the deadlines are missed and the planned revenue is not met? In my experience, engineers evangelize the agile approach to managers and NOT the other way around. Let's face it, market dynamics in high-tech are a bit chaotic and agile tries it's best to put things in order a bit. For example, your customer tells you what he needs, you work hard on it and just when you are inches close to finishing it, someone releases a nice and shiny device which sells like crazy. Ooops, your customer is very much interested in running the great app you have been developing on that device as well. What are you going to say to your customer? Dictate him what his business interests should be? Tell him to ignore the new trend in the market? Try it, and in some months you'll have to start washing cars.
On May 26, 10: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
