CDW Talk on Enterprise 2.0 Technologies

3. • Deployment of COTS ERP and CRM applications • Organizations moved from mainframes to relational databases • The introduction of e-mail, ecommerce, and relatively simple websites • Far too often, data silos hamstrung organizations and their employees Enterprise 2.0, # 3

4. • Increase communication and collaboration among employees • Increase quality of—and access to– enterprise data • Change the focus: Move from department or application to organization Enterprise 2.0, # 4

5. Enterprise 1.0 With few exceptions, only large companies could afford best-of-breed technologies. Enterprise 2.0 Companies of all sizes can afford best-of-breed technologies. Enterprise 2.0, # 5

6. Enterprise 1.0 Organizations had to evaluate relatively few technology vendors and solutions. Enterprise 2.0 The number of options available to organizations is downright dizzying. Enterprise 2.0, # 6

7. Enterprise 1.0 Extremely expensive. Storage requirements needed to be anticipated. Enterprise 2.0 Very cheap; a commodity. Storage needs can be adjusted on the fly. Organizations can pay for only what they consume. Enterprise 2.0, # 7

8. Enterprise 1.0 Small Data Relational, structured, transactional, table- friendly, and orderly. Enterprise 2.0 Big Data Non-relational, unstructured, not table-friendly, and messy. Enterprise 2.0, # 8

9. Enterprise 1.0 IT provisioned BlackBerrys for a few key executives. Few proper “apps” existed for cell phones Enterprise 2.0 Just about every employee is carrying a smartphone, tablet, or both. BYOD has arrived. Apps have exploded. Enterprise 2.0, # 9

10. Enterprise 1.0 Hosted on-premise or via ASP. Enterprise 2.0 An array of options exists: • On-premise • Different types of clouds Enterprise 2.0, # 10

11. • There is one cloud • You have to go “all in” with the cloud • The cloud is a panacea Enterprise 2.0, # 11

12. Enterprise 1.0 Almost always Waterfall- based. Top-down. Enterprise 2.0 A hybrid. Both agile and Waterfall methods are used. Enterprise app stores allow for near-instant deployment. Often organic and bottom-up. Enterprise 2.0, # 12

13. 1. Hands On A. Big Brother B. Obstructionist 2. Hands Off 3. The Enabler Enterprise 2.0, # 13

14. • Know your organization’s limitations from the get-go • Get a little bit pregnant with the cloud • Bridge the IT-Business Divide Enterprise 2.0, # 14

15. Enterprise 2.0, # 15

16. • Prepare for sudden, unexpected growth • Embrace uncertainty • Consider the developer ecosystem, not just the platform Enterprise 2.0, # 16

17. “Culture eats strategy for lunch.” –Peter Drucker Enterprise 2.0, # 17

18. www.philsimon.com @philsimon Enterprise 2.0, # 18

Notas do Editor

Hello. My name is Phil Simon. Today I’ll be talking about the arrival of Enterprise 2.0. I’ll be talking about cloud computing, SaaS, Big Data, mobility, and a whole host of other topics. I’ll be referencing my second book, The Next Wave of Technologies. Transition – who’s this guy? Offer prize/book to winner.
Yogi Berra was a former American Major League Baseball catcher, outfielder, and manager. He played almost his entire 19-year baseball career (1946–1965) for the New York Yankees. As a general comment on baseball: "90% of the game is half mental.” – when you come to a fork in the road, take it. LET’S GO BACK 15 YEARS TO A MUCH SIMPLER TIME WITH RESPECT TO IT.
4 bullets 1. Mention Why New Systems Fail 2. Oracle, IBM & SQL server 3. Email has remained the killer app 4. Emphasis was on the application, not the enterprise. Transition: IN THE LATE 2000s, we began to hear the term Enterprise 2.0.
3 BULLETS – this is not a definitive list DEFINE E2.0: Technologies include Cloud computing, MOBILITY, MDM, SaaS, open source, SOA, web services 1. Move beyond email and intranets; unleash power of information in organization 2. Data is very powerful, but only if people can access it—and its quality isn’t suspect. 3. Remove focus from department, group, and division; begin to think enterprise- or company-wide TRANSITION: Now let’s compare enterprise 1.0 and 2.0 across a number of different dimensions
Table 1 Hedge funds Table 2 QUESTION: ASK PERSON IN FRONT HOW MANY EMPLOYEES WORK AT YOUR COMPANY. You can use the same services as Netflix – a $12B company-> Even a small business can use AWS, just like multi-billion dollar Netflix. Mention the new small
Table 1 MOST COMPANIES RAN WINDOWS, OFFICE, ETC. Many small businesses ran their own MS exchange servers Table 2 And if you can’t find what you want, just build it. The number and variety of APIs, SDKs, ISVs, and robust development platforms has exploded.
Table 1 Children’s Place Example Table 2 Mention Kryder’s law Minimize waste; more company-friendly pricing models
Table 1 MEGABYTES AND GIGABYTES Table 2 TERABYTES AND PETABYTES
Table 1 Early innings of mobility Table 2 Define BYOD Apple – more than 50 billion app downloads
I’d like to talk a little about about the cloud and dispel a few myths.
3 bullets 1. Not true. Public cloud, private cloud, semi-private cloud 2. Many organizations have migrated slowly, one application at a time. 3. It doesn’t fix bad data, dysfunctional business practices, etc.
Table 1: Mention long implementation times (often a number of years). Very expensive projects. Consultants parked on site. Table 2: Much shorter implementation times Talk about Yammer – 1.2B TRANSITION – AGAINST THIS INCREASINGLY CHAOTIC BACKDROP, WHAT SHOULD THE ROLE OF IT BE?
So, with the consumerization of IT and the explosion in technologies, what should be the role of IT? Here are three schools of thought 1. Hands on a. IT is omniscient and omnipotent b. if left to their own devices, end users will cause the organization—and IT—quite a few headaches 2. Laissez faire – IT can’t and shouldn’t contribute 3. IT should give the business what it needs–and occasionally step in as needed.
1. If you don’t have internal expertise developing apps, don’t try. Use Merck systems’ analogy. Would IBM make its own aspirin? 2. It’s not a binary 3. As I write in Why New Systems Fail, this kills many projects. Involve key players early on.
What is this?
1. Always better to have excess capacity and not need it than vice-versa 2. Predicting the future is futile. 3. Interoperability is essential; don’t build new silos. Remember the infamous words of Peter Drucker
No matter what the technology or strategy, beware of bad culture or employees.

CDW Talk on Enterprise 2.0 Technologies

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (13)

Semelhante a CDW Talk on Enterprise 2.0 Technologies

Semelhante a CDW Talk on Enterprise 2.0 Technologies (20)

Mais de Phil Simon

Mais de Phil Simon (6)

Último

Último (20)

CDW Talk on Enterprise 2.0 Technologies

Notas do Editor