ABSTRACT
Development of enhancements in a legacy environment poses a major application development challenge to many finance and insurance companies. Investment in modernizing architectures does not always immediately realize operational and customer-perceivable value mandated of agile environments. And top-down service portfolio management does not consider architecture impact on decision making to make the priorities and investment realistic. To address these challenges we provide the Agile Modernization Framework (AMF) for systematic decision-making that includes bottom-up architectural and infrastructure information along with top-down and strategic customer and operational needs to make business decisions. We show how this unique hybrid prescriptive framework 1) guides the decision making of legacy-related application features, 2) aligns and constrains implementation in the context of an agile business environment and strategy, and 3) applies to realistic examples where services are often based on shared components and numerous services are involved in complex interrelationships.
Categories and Subject Descriptors
D.3.3 [Programming Languages]: Language Contructs and Features – abstract data types, polymorphism, control structures. This is just an example, please use the correct category and subject descriptors for your submission. The ACM Computing Classification Scheme: http://www.acm.org/class/1998/
General Terms
Management, Measurement, Documentation, Performance, Human Factors, Standardization, and Verification.
Keywords
Legacy portfolio decisions, decision-making metrics, modernization, migration, IT service portfolio management.
INTRODUCTION
We introduce the Agile Modernization Framework which supports a “stakeholder driven & legacy impact based” decision making process for the service portfolio of the enterprise. The overall benefit is to align Agile