Agility is also a function of design
WalkerRoyce 0600019HVS Visits (5157)
The trends in changing executable software baselines and particularly the cost-of-change trends are the true measure of the agility. Agility means changing easily so we need to quantify change trends. Both architectural integrity and process effectiveness will drive the cost-of-change. Therefore, agility is NOT just a process attribute, it is equally, if not more, an attribute of good design.
In the past, it has always struck me that most of the value of modeling was attributed to better representation of the architecture, namely more accurate, more shareable, and more machine processable. In this sense, modeling was seen to be much more effective documentation, more than anything else.
Far too little emphasis has been placed on the value of modeling for: reducing the cycle time from concept to executable. In several of my past experiences (most notably at TRW, Boeing, Raytheon and Ericsson), the primary value of modeling and its most discriminating contribution to agility was that it reduced the cost-of-change and cycle time in architectural prototyping, early refactoring, later iteration and maintenance. When change was easier, more experimentation got done and architectural quality improved dramatically, thereby increasing overall project agility and reducing late scrap and rework.