Session Abstract: “IT has undergone major change, but the pace of change that lies in the immediate future has never been experienced. New platforms driven by cloud computing, new sources of infrastructure and applications solutions, the changing technology stack and resulting impact on skills will provide significant challenges to IT over the next five years.
- What will the enterprise of 2013 look like, and what will be the business drivers for IT change over the next five years?
- What changes in technology and sourcing of solutions will impact IT strategies?
- How will IT adapt to absorb the incredible changes that are on the horizon?”
Val starts by setting up what Enterprise 2013 looks like, he is sharing the dimensions, but wants the audience to score themselves in each area, from minor to extreme change.
Factors:
Macro level: Calibrating Executive Table and Core Lifecycle Changes: New Leadership, Changes in Strategy, Business Processes, Business Information, Metrics, Core Lifecycles (product, supply, customer etc). [I would say: how does the business architecture / business design change]
Changes to user base: more online, broadband, mobile, social. User base on mobile side will be dramatically bigger than those working on computer.
IT Changes: Alternative delivery and consumption models, ie, Cloud Computing. How many layers will you shift to cloud? Servers, middleware, applications, information services, business services? Extreme version is shifting the build of your apps to the cloud. Staffing and sourcing. Disciplines spanning IT: SDLC meets ITIL.
Applications Changes: methodologies; who does the work; what environment & tools will be used (Application architecture: SOA, SODA, SOBA, WOA, CEP, context aware, composition, orchestration, assembly)
Val is talking now about bringing things together via roadmaps, matching business roadmap, IT roadmap and vendor/provider roadmaps.
Asking the audience, most folks scored themselves in the extreme change realm, some in moderate change, none in minor change.
In discussing strategies for moderate change, Val is suggesting:
1. “hollowing & retiring legacy systems” – pull out value, remove waste (duplication)
2. hybrids of internal, cloud and BPO. There is an integration center to this picture. First integration center box was ESB, B2B gateway etc. Now, that integration box is replaced with a Business Process Platform. Val is not suggesting buying BPM from one vendor. He is talking about bringing together services you need, for your change and portfolio, to integrate the business services and information.
Extreme Change Strategies – Application Perspective
Val has referenced Proctor & Gamble’s Open Innovation program. Suggests adopting that type of model for Open Applications Innovation. Your organization consume services from cloud, and “plugs” services back into cloud. “Leading companies will offer an external service portfolio … that can be leveraged in many clouds”.
Val has put up a slide of an External Services Platform Strawman for the Public Sector. In the center are business services, such as SSN, Citizen Information, etc. The right is Aggregate Information, non-PII. Left is user experience. Bottom was infrastructure (I think, slide moved).
Application 2013: Advanced Business Process Platform: “serious about BPM”, “serious about CEP & BAM”. Also, the world gets more simple. Val is calling out Salesforce.com, Twitter, iPhone. Talking about application’s capability vs. value. Excessive capability reduces an application’s value.
Applications 2013: Governance and Behavior: Business Alignment + Engagement and Accountability. Current maturity of organizations is very low, just around repeatable. Needs to be level 4 (think CMMI) quantitatively managed.
Enterprise 2013: Seek – Model – Adapt
Key Disciplines
- Pattern Seeking
- Performance Driven Culture
- Transparency
- Optempo Advantage: CEP comes into play. Ability to slow down, speed up, or change direction as needed
Bottom line: where will innovation happen, at externally facing points; advanced business processing will be from complex event processing, simplify your apps, improve your maturity.
Comments