http://www.blogstudio.com/aal/index.html Discuss the AAL concepts, implementation, and general philosophy en-us http://www.blogstudio.com/aal/index.html http://www.blogstudio.com/BlogCSS.gif Discuss the AAL concepts, implementation, and general philosophy http://www.blogstudio.com/SearchResults.jsp?Mode=G&Action=BL_Blog&Method=searchPosts&Subject=Introduction&Display=YES&Id=1057621477125000361792608558&OpenNew=NO&TargetMessageId=1058925677265 Project Canceled: XP asks the customer to choose the smallest release that makes the most business sense, so there is less to go wrong before going into production and the value of the software is greatest Response: A factor that XP seems to ignore is the cost of customer involvement from both the customer's perspective and the developer's. The customer may desire small, incremental releases but the cost involved can be substantial. A release is often reviewed by several people. The dev... http://www.blogstudio.com/SearchResults.jsp?Mode=G&Action=BL_Blog&Method=searchPosts&Subject=Introduction&Display=YES&Id=1057621477125000361792608558&OpenNew=NO&TargetMessageId=1058902163406 Schedule slips: XP calls for short release cycles, a few months at most, so the scope of any slip is limited. Within a release, XP uses one- to four-week iterations of customer-requested features for fine-grained feedback about progress. Within an iteration, XP plans with one- to three-day tasks, so the team can solve problems even during an iteration. Finally, XP calls for implementing the highest priority features first, so any features that slip past the release will be of lower value. (E...