tag:blogger.com,1999:blog-1953389229399417080.post1102176727395128289..comments2009-03-23T09:17:30.772-07:00Comments on SmartAgile.com: The Cone of Sanityaaron shttp://www.blogger.com/profile/10762440807623907623aaron@agile101.comBlogger3125tag:blogger.com,1999:blog-1953389229399417080.post-54366871986831365122009-03-23T09:17:30.772-07:002009-03-23T09:17:30.772-07:00I agree that this can be a tough one. One of the m...I agree that this can be a tough one. One of the main points of Agile is to remain flexible, but disciplined. I have consulted at marketing-driven companies where developers had 100% planned workloads but spent another x% of their time handling last minute requests. And while some requests were completely valid, some were whims of a particular employee that would end up delaying more important aaron shttp://www.blogger.com/profile/10762440807623907623noreply@blogger.comtag:blogger.com,1999:blog-1953389229399417080.post-6337345935914982012007-12-09T22:57:00.000-08:002007-12-09T22:57:00.000-08:00I've found that this can work sometimes, but often...I've found that this can work sometimes, but often the customer (in my case, the marketing department) demands changes now, NOT in the next iteration. This happens a half dozen times every iteration. How would you handle this kind of a demanding customer?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1953389229399417080.post-32148838109450741292007-12-09T22:50:59.480-08:002007-12-09T22:50:59.480-08:00I get this. It is great to be flexible, but someti...I get this. It is great to be flexible, but sometimes customer ADD can get ridiculous. It is a good idea to put a stake in the ground and provide some stability for the development team.Anonymousnoreply@blogger.com