Martin Fowler在他最新的
bliki：RigorousAgile 中提到：
“The complainer may talk about how this means that you can't tell if a particular team is using an agile method or not. They may also say that this makes it hard to teach people how to do agile methods - what's the curriculum?”（這些抱怨者指出他們很難區分是否在使用敏捷方法，也很難用固定的課程去教授如何使用敏捷方法）
然而，沒有一個嚴格的定義，正是敏捷方法的核心哲學 （“This lack of rigorousness is part of the defining nature of agile methods, part of its core philosophy.”）
Martin接著指出：
“Different kinds of systems have different kinds of pressures and forces, which makes it very difficult to come up with a rigorous statement of what to do that's sufficient to cover them.”（不同的系統有來自不同方面的壓力，這種情況使得很難定義出一個嚴格的過程，去定義如何有效的解決這些問題）
而另一關鍵的問題是：人，軟件開發的主體，是一個最大的可變的因素 （“This effect is compounded by the fact that software development is such a people-oriented activity, and people are naturally inconsistent and highly variable. ”）
倡導敏捷方法的人，之所以沒有為敏捷方法制定出一個嚴格的定義，就是為了將軟件開發中最大的可變因素，而又是過程的執行者：人，忽略掉。（“ that's its not effective to try and bind software development to a rigorous process, because that's ignoring the essential nature of the primary (human) components that will execute that process”）
閱讀全文
Martin Fowler
inconsistent and highly variable
Email this store to a friend (send a short email with a subject to this story)
Subscribe to kukooBlog (subscribe kukooBlog's RSS feed)
Send me feedback on this story
Software，Agile Programming 
Programming