ArchitectedERP
SAP Architecture & Innovation
SAP Architecture & Innovation
Architecting IT with ArchitectedERP
IS/IT Architecture & Innovation posts
Services Thinking
Download area
IT Architecture services
Contact us
Blog Mendel Koerts on SAP Architecture & Innovation
When would you need ArchitectedERP?
What makes ArchitectedERP unique?
What do others say about ArchitectedERP?
e-book Table of Contents
Get your complimentary e-book!
Terms and conditions
e-book Table of Contents
Architected
ERP - Table of Contents:
Foreword
Preface
1
The Delivery of Strategy
1.1
An approach to the delivery of strategy
1.2
Aren’t there plenty of methods available?
1.3
Babel-like confusion - another succes killer
1.4
Process thinking versus services thinking
1.5
Big is beautiful – and habitually rigid
1.6
What is
Architected
ERP
1.7
What makes
Architected
ERP unique
1.7.1
There is nothing like it
1.7.2
A multi-disciplinary approach to Strategy Delivery
1.7.3
Converges Business and IT through
services thinking
1.7.4
Helps you building your foundation for execution
1.7.5
Unrivalled in broadness
1.8
Book navigator
1.9
The
Architected
ERP community
1.10What you can expect from the detailed version of
Architected
ERP
2
Enterprise-Level Dynamics
2.1
There is value in it – now how to get it?
2.2
It’s getting lean
2.2.1
Setting the scene
2.2.2
Project outline
2.2.3
What can you learn from this?
2.3
Balancing innovation and stability
2.3.1
Setting the scene
2.3.2
Project outline
2.3.3
What can you learn from this?
2.4
Why not do it all at once
2.4.1
Setting the scene
2.4.2
Project outline
2.4.3
What can you learn from this?
2.5
Shareholders as major stakeholders
2.5.1
Setting the scene
2.5.2
Project outline
2.5.3
What can you learn from this?
2.6
Reflections on the approach to Enterprise Transformation
3
Volatility-proof Solutions
3.1
Implementing solutions in an era of continuous transformation
3.2
From the cradle to the grave
3.2.1
Setting the scene
3.2.2
High-level requirements
3.2.3
High-level solution
3.2.4
What does this teach us?
3.3
Solutions for the subterranean
3.3.1
Setting the scene
3.3.2
High-level requirements
3.3.3
High-level solution
3.3.4
What does this teach us?
3.4
Departmental distress
3.4.1
Setting the scene
3.4.2
High-level requirements
3.4.3
High-level solution
3.4.4
What does this teach us?
3.5
Integrated insight
3.5.1
Setting the scene
3.5.2
High-level requirements
3.5.3
High-level solution
3.5.4
What does this teach us?
3.6
Rightshore
®
, for sure
3.6.1
Setting the scene
3.6.2
High-level requirements
3.6.3
High-level solution
3.6.4
What does this teach us?
3.7
Reflections on obtaining volatility-proof solutions
4
At Crossroads
4.1
Introduction
4.2
Trends in business
4.2.1
Introduction
4.2.2
Cost structure transformation
4.2.3
Business collaboration
4.2.4
Changing business-customer relationships
4.2.5
Industry consolidation
4.2.6
Regulatory change
4.2.7
Technological innovation
4.3
Trends in technology
4.3.1
The You Experience and From Transaction to Interaction
4.3.2
Process-on-the-Fly and Thriving on Data
4.3.3
Sector-as-a-Service and the Invisible Infostructure
4.3.4
Open Standards and Service-Orientation
4.4
The services thinking paradigm
4.5
Services thinking put in practice
4.6
The business case for
services thinking
4.7
Summary
5
The Methodology Library
5.1
The shoulders of giants
5.2
The Open Group Architecture Framework (TOGAF)
5.3
PRojects IN Controlled Environments (PRINCE2)
5.4
SAP Enterprise Architecture Framework (SAP EAF)
5.5
Integrated Architecture Framework (IAF)
5.6
Structured Expert Method for Business Analysis (SEMBA)
5.7
Planned Change Approach (PCA)
5.8
Methodology for Accelerated Transformation to SOA
5.9
RApid INnovation (RAIN)
5.10 Accelerated SAP (ASAP)
5.11 Accelerated Delivery Platform (ADP)
5.12 Wrap-up
6
The Foundations of A
rchitected
SAP
6.1
Managing complexity
6.2
Architected
ERP
6.3
A lingua franca
6.4
Talking big or small?
6.5
Building blocks for project or program assembly
6.6
Engagement type interaction
6.7
Wrap-up
7
Enterprise Transformation Planning and Portfolio Management
7.1
Introduction
7.2
Enterprise Transformation Planning from a bird’s eye view
7.3
How Enterprise Transformation Planning is organized in detail
7.4
An example of
Architected
SAP-based Enterprise Transformation Planning
7.5
More details on Enterprise Transformation Planning
8
Solution Crafting
8.1
Introduction
8.2
Solution Crafting from a bird’s eye view
8.3
How Solution Crafting is organized
8.4
More details on Solution Crafting
9
Solution Delivery and Transition
9.1
Introduction
9.2
Solution Delivery and Transition from a bird’s eye view
9.3
How Solution Delivery and Transition is organized in detail
9.4
More details on Solution Delivery and Transition
10
Putting
Architected
ERP To Work
10.1 From vision to reality
10.2 From independent formats to a business network
10.3 Something more straightforward…
10.4 Epilogue
About the authors
Architecting IT with ArchitectedERP
IS/IT Architecture & Innovation posts
Services Thinking
Download area
IT Architecture services
Contact us
Blog Mendel Koerts on SAP Architecture & Innovation
© 2010 ArchitectedERP - All rights reserved.