Comment by Guest on 2006-03-02 04:56:06 Jonathan's thoughts are a quality counter punch to the tons of Agile talk that tells us to get rid of QA and testers. If Agile had to be successful, we would have seen widespread adoption by now. the fact that even after many years, very few and that too primarily small teams use agile, shows that the resistence from the software dev community is too big for Agile hype to overcome. A clear division of work suits best for mankind. developers doing everything won't sustain. |
Comment by Guest on 2006-03-06 21:35:06 "If Agile had to be successful, we would have seen widespread adoption by now. the fact that even after many years, very few and that too primarily small teams use agile, shows that the resistence from the software dev community is too big for Agile hype to overcome." There are lots of possible explanations for that resistance. Some of it is healthy, some not terribly so. A lot of it throws the baby of pragmatic ideas out with the bathwater of Agile dogma. In my experience, Agile does indeed seem better suited to some contexts than others; nothing surprising about that. The trouble is this: absolutist statements--either in support of Agile, or against it, from inside or outside--tend to [I]ignore[/I] context, or [I]deny[/I] it. Most dogma ignores people and focuses on practice as the cause of or solution for all of our problems. It's odd that dogmatic statements like the ones Jonathan cites--“manual tests are harmful”, or “every test must be automated”, or “testers are the Quality gatekeepers on a project”--come from a community that supposedly values people and interactions over processes and tools. Jonathan's interview is a refreshing antidote to that stuff; there's little cant, lots of personal experience, and lots of context to support what he says. |
Comment by GUEST on 2008-05-08 22:21:54 Hi , I am not getting this point. |