The Friction of Agile
It is quite a common occurrence in my practice: I step into an engagement that involves hundreds of developers, testers, product managers, project managers, architects, user design specialists, and quite a few other disciplines, from all over the globe. The time zone difference between some of their most important sites is 10, 11, or 12 hours. The expectations of whatever agile software method I bring to bear is that it will improve quality, productivity, and time to market. Some of the clients actually ask me point blank: "Well, Israel, this is, after all, 2011, not 2004. You can certainly do better than what you accomplished back then with the agile transformation at BMC Software,1 can't you?!"
To continue, please log in: