The Top 10 Strategic Tech Trends for 2014 - Gartner Symposium - Oct 2013

The Top 10 Strategic Tech Trends for 2014
David Cearley

Trends you can't afford to ignore
  1. What trends will have the biggest impaction the enterprise over the next 3 years?
  2. What trends drive significant change and disruption? Rethink approach.
  3. Changes that are making an impact that is widely applicable.
Backdrop of the Nexus of Forces – social, mobile, info, cloud.
Converging Forces:
- mobile device diversity and mgmt
- mobile apps
- Internet of Everything
- Hybrid Cloud and IT as a Service Broker
Derivative Impact:
- Cloud/Client Arch
- Era a personal cloud
- SW defined anything
- Web scale IT
Future Disruptions:
- Smart machines
- 3D Printing

Mobile Devices
 - no single vendor or platform will dominate – google, apple, microsoft with distant 3rd position with only about 10% market share by 2015. Android and iOS dominate.
  • many form factors, Google glass, watches. Embedded technology, wearable devices
  • BYOC – bring your own clothing
  • Innovative BYO knowledge workers will use 3 to 5 devices by 2016
Managing Mobile Diversity
  • Rise of Enterprise Mobile Platforms
  • Think about building your own enterprise mobile device platform
  • Emerging leaders – Microsoft, SAP, IBM, SalesForce
  • MDM, MEAP, security containers, file sync/share, cloud mobile back-end services
The Internet of Everything
2020 – 25B things connected to the internet
Internet of People – Facebook 1.11B as of Mar 2013
Internet of Places – 3B Foursquare check-ins as of Jan 2013
Internet of Information – 30T web pages in Google index in 2013
  • Big data unlocks the value
  • Architecture Matters – where do we keep the data? Edge, gateway, cloud, enterprise?
Hybrid Cloud Computing
  • beware of the hype and the confusion
  • It's all about crossing boundaries
  • Public and private cloud environments
  • Extend storage tier out to AWS
  • SAML authentication to various services
Hybrid IT – IT as an advisor, broker and provider
Building private cloud services = IaaS and PaaS

Cloud/Client Architecture – The Developer Perspective
  • cloud is the control point and system of record – data logic and UI model
  • Cloud Service model
  • Apps span multiple client devices
  • Application is in the cloud; apps expose capabilities on the client
Rise of the Personal Cloud – the Human Perspective
  • cloud of services that each person uses
  • Not a single device but a cloud of services that each person uses
  • Shift of power
  • Unique collection of services for each person
Journey to Programmable Everything
  • software defined everything
  • Tons of vendor hype
  • OpenStack
  • Fabric-based computing
  • Software Defined Anything
The API Economy
  • greater consumption of APIs
  • You already live in the API economy if you tweet, register, check-in, deposit, like and comment.
Web-Scale IT 
  • Architecture designed to reduce outages
  • DevOps
  • You too can run with the big dogs – Facebook, Google, Microsoft.
The Rise of Smart Machines
  • Content Explosion
  • New Hardware
  • Algorithms
  • Network Scale
  • Movers – autonomous vehicles
  • Doers - machine–based helpers, robots
  • Sages – linguistically smart info-based helpers, personal assistants, smart advisors
3D Printing

  • rapid, iterative development of prototypes
  • 82% CAGR to $5.7 billion by 2017
  • Inhibitors - over–hype, need to adapt business processes

Comments

Post a Comment

Popular posts from this blog

Enterprise Architecture Inside Salesforce

Image
  Enterprise  Architecture Inside Salesforce Enterprise Architecture — How We Do It Internally The two words, “Enterprise Architecture”, elicit various reactions — everything from “ we tried that and it doesn’t work ” to “ we need that! ” to “ we have an effective EA practice ”. Unfortunately it is possible (even easy) to do Enterprise Architecture  incorrectly , with an approach that is lethargic, technology-first and theoretical — the classic ivory tower. (In Salesforce, the internal IT group reporting into our CIO is called “Business Technology” so you’ll see me use BT to refer to Salesforce IT) I lead the Salesforce Enterprise Architecture team within Business Technology and I’m often asked the following questions: how does Salesforce do Enterprise Architecture? why do you need Enterprise Architecture? how do you shift the conversation to business capabilities? Illuminate — The “How” of Salesforce Enterprise Architecture Let me start with the “HOW” first. Within Sales...
Read more

Illuminate - Business Model Exploration

Image
  Illuminate — Business Model Exploration One of our world-class Salesforce Enterprise Architects, Jonathan Laudicina ( https://www.linkedin.com/in/jonathan-laudicina/  ) has done amazing work on Business Model Exploration. I want to highlight some of his work and I think you’ll find it useful. As a reminder, Illuminate is the Enterprise Architecture Methodology that we use inside Salesforce as well as with our customers. The overall Illuminate methodology is depicted below. You will notice that Business Model Exploration is the first step in Illuminate. Business Model Exploration is the methodology we use with customers to articulate: External Forces pushing on the business Internal Forces pushing on the business Customer specific Business Model Canvas At the heart of Business Model Exploration is the Business Model Canvas. It is the place in which you capture key factors about a company’s specific value proposition, partners, customer segments, cost structure and revenue str...
Read more

5 Key Components of a Successful Enterprise Architecture Function

  5 Key Components of a Successful Enterprise Architecture Function 5 Key Components of a Successful Enterprise Architecture Function Creating and managing a successful Enterprise Architecture function requires a variety of different hard and soft skills. In addition, each company is different and the Enterprise Architecture function needs to calibrate and align itself to the specific company. However, there are five common features of a successful Enterprise Architecture function that are applicable to all companies. 1. Governance Enterprise Architecture (EA) requires governance, however not in the form of complex documents, forms or processes.  Definitely avoid EA being seen as the policy-enforcement team — people will avoid EA if the perception is that EA is a blocker.  The best governance starts with a simple, recurring dialogue across multiple functions facilitated by EA. I am always amazed at how valuable it is just to get cross-functional teams to  talk . Pick...
Read more