journey to the enterprise
TRANSCRIPT
Journey to the Enterprise
A little about me
• Coding since 1992
• VB, Java, C/C++, FoxPro, PB, RPG
• DB2, Oracle, MSSQL, bTrieve
• Specialized in Application Integration
• Microsoft since 2000• Architects, web security, mapping, web, cloud
@markjbrown
What is Enterprise?
Size of company?
• How about PC’s?
• What about employees?
• What about Governments?
What they do?
• What markets are companies in?
• Manufacturing, Oil & Gas, Pharma, Healthcare, Retail, Financial
Has an IT Department?
Has a data center?
Based on structure?
• Enterprise =
• 2+ business units (which are dependent on each other)
• Single set of financials
• Common systems for similar functions
• Enterprises, regardless of size, markets, IT, etc. all invest in…
http://blogs.gartner.com/mark_mcdonald/2009/06/15/is-your-company-an-enterprise-the-answer-matters/
Enterprise Applications
• ECM+C – Enterprise Content Management and Collaboration
• ERP – Enterprise Resource Planning
• EAM – Enterprise Asset Management
• CRM – Customer Relationship Management
• BI – Business Intelligence
• HRM – Human Resources Management
• BPM – Business Process Management
• EAI – Enterprise Application Integration
Enterprise App Vendors
Reduces Risk
• Enterprise App Vendors provide the following:
• Proof – Case Studies, white papers, reference customers
• Guidance – How to deploy, integrate and operate
• Help – Consultants, architects, developers, partners
• Support – Phone, on-site
Enterprise IT does two things
•Integrate•Build custom
ERP
Payroll
HR
BillingOrders
SCM
CRM
In the old days
ERP
Payroll
HR
BillingOrders
SCM
CRM
ESB
These days…
ERP
Payroll
HR
BillingOrders
SCM
CRM
But in reality…
ESB
So what about building Enterprise Solutions?
Functional Specs
Lots of Competing Stakeholders
Lots of Process…
Is it hard to believe?
• 37% of all IT Projects Fail*
• Failure is more than an option. It’s likely.
• Complexity increases Failure
• Process slows innovation
* http://www.pmsolutions.com/collateral/research/Strategies%20for%20Project%20Recovery%202011.pdf
WHY????
• Requirements: Unclear, lack of agreement, lack of priority, contradictory, ambiguous, imprecise.
• Resources: Lack of resources, resource conflicts, turnover of key resources.
• Schedules: Too tight, unrealistic, overly optimistic.
• Risks: Unidentified or assumed, not managed.• Identify• Estimate• Quantify• Manage
Keep it simple
A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system. – John Gall
Systemantics: How Systems Really Work and How They Fail. (1975)
In other words…
How to Succeed
• Ensure high-functioning PM with clear skills & authority
• Clear requirements (stakeholders are aligned)
• Right people with right skills
• Identify and Manage Risks: Run water through the pipes, eliminate unknowns
• Bite-sized deliverables (If you see a waterfall, run)
How Change HappensFrom innovation to obligation
CompetitiveAdvantage
to Firm
First firm in an industry implements innovation
Second firm in the industry implements innovation
Third firm in the industry implements innovation
TIME
Source: Chappell & Associates
Window of differentiation
Build or Buy?Making the choice
Create a custom application
Buy a packaged application
CompetitiveAdvantage
to Firm
TIME
Source: Chappell & Associates
In the year 2014
In the year 2014
The Cloud will dominate
• Cloud = $47 Billion in 2013
• AWS > $4 Billion in Revenue
• Microsoft PaaS 2010. IaaS 2012
• Google PaaS 2011. IaaS 2012
• Oracle, IBM and SAP now all entering market
API Management
• Next great thing to happen to Integration
• Evolution of SOA
• Evolved because of cloud
• SaaS integration makes it real
• The WEB makes it REAL
• It’s where the Enterprise and YOU come together
Thank You
https://joind.in/10498
@markjbrown