tag:blogger.com,1999:blog-3697508237645642567.post6694311948445919129..comments2015-02-08T15:59:30.453+00:00Comments on David Sprott's Blog: Agile ArchitectureDavid Sprottnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3697508237645642567.post-38547383688245268212012-11-16T10:02:00.102+00:002012-11-16T10:02:00.102+00:00Hi Loek, Agree agility means one should be able to...Hi Loek, Agree agility means one should be able to change business processes and data with minimum impact. The Amazon case illustrates the primary enabler is an effective service architecture . DavidDavid Sprotthttp://www.blogger.com/profile/13837436108758464455noreply@blogger.comtag:blogger.com,1999:blog-3697508237645642567.post-19366267379143646032012-11-15T12:49:39.869+00:002012-11-15T12:49:39.869+00:00It seems to me that when we discuss agile business...It seems to me that when we discuss agile business with an underlying agile architecture, we should focus on 2 main imperatives:<br />1. Agility of process<br />2. Agility of data<br />IMHO an agile architecture should not prescribe the flow of control of a long running process, neither should it prescribe a certain use of data/information. Agility in this case means that one should be able to change business processes and the underlying manipulation of data/information in these processes without having to refactor parts or all of the architecture, be it on an enterprise or on a solution level. This is to me the holy grail of agility. Loek Vredenberghttp://www.blogger.com/profile/15187257718966716628noreply@blogger.com