Change in technology, business and society is ever present and accelerating. It is very unlikely to slow down, thus it is a stable requirement. Our methods of doing strategy, devising future architectures and delivering systems capabilities in support of business processes, capabilities and delivery of services and products therefor need to address this.
A great deal of effort has been applied in Agile Methods over the past two decades to accelerate the system development process, i.e. doing things faster. No matter how quickly they deliver, however, these methods often produce something inflexible. This paper argues for a broader approach, which looks at: the context (much of the change required is outside the system delivery space; the focus (what should we be changing and why?); and three approaches to achieving the change with respect to system deliver: doing less things (de-scope, use packages, libraries, components, frameworks); do things faster (agile methods, automation, generation) and make more flexible things (runtime adaptable or domain model driven systems). The last of these is an unconventional approach that holds promise, even if you currently don’t practice, or succeed with, agile methods.
Finally, we also address the dilemma of accelerated delivery while dealing with large legacy application landscapes.
Published?
Keywords?