managing the global it ecosystem microsoft dr. joseph williams, global technology director...
TRANSCRIPT
2
Background
We went from building applications
To worrying about support & management
To worrying about the ilities
To worrying about ROI/TCO
To worrying about reuse
To worrying about integration (internal & external)
To worrying about alignment
To worrying about strategic impact
Architects have always managed these
3
Perspective
IT Professionals are trained to optimize
IT is typically funded at a project level
IT now needs to manage chaos
IT Professionals are linear, myopic, and often religious in how they solve problems
4
Goal:
Healthy and Productive
IT Ecosystem
Driven by business realities
What is included:• Inputs• Outputs• Lifecycle management• Impacts
Why an Ecosystem Approach?
It recognizes that the goal is to manage the overall health of the IT ecosystem rather than to optimize it components
5
IT Ecosystem Health
Measured by carrying capacity
Idea is to find a productive balance and get away from point optimization
Threats Waste Predators Unintended consequences Disease or deprivation Migration out of the ecosystem Monovision (lack of diversity) or dependency
6
7
8
The Global IT Ecosystem
Just because a company is global doesn’t mean they are ready to manage their IT Ecosystem globally
This is a capability maturity problem
9
Global Architecture for the IT Ecosystem
It is almost 100% about command & control
The key issues typically are: Prioritization What to manage globally versus locally? How to manage a global deployment? What are the traps in each country / subsidiary? How to best shop for local deals / expertise / opportunities?
Manifestations are Enterprise architecture Enterprise Standards Global procurement /sourcing / licensing contracts IT Impact statements