- from the business objectives to a portfolio of projects (or roadmap);
- from the brief initial project specs to a prototype;
- from a prototype to a deployable solution (processes and services);
- from a deployable solution to a deployed solution (by deciding where to deploy each service, e.g. in-house or in-cloud, IaaS, SaaS, PaaS, etc.);
- EA supervision of projects;
- platform-enabled agile solutions as an implementation enabler;
- melting pot of #entarch+#bizarch+#BPM+#SOA+#ECM+#ITIL+#governance+#strategy as a methodology enabler.
And resources which describe the parts of the chain.
1. Enterprise pattern “Strategy TO Portfolio” (STOP)
- Writing IT strategy http://improving-bpm-systems.blogspot.com/2011/09/writing-it-strategy.html
- Writing IT strategy - From business priorities to the planning of IT actions http://improving-bpm-systems.blogspot.com/2012/06/writing-it-strategy-from-business.html
- Linking business strategy and IT strategy http://improving-bpm-systems.blogspot.com/2013/02/linking-business-strategy-and-it.html
- Enterprise patterns: Strategy TO Portfolio (STOP) http://improving-bpm-systems.blogspot.com/2013/04/enterprise-patterns-strategy-to.html
2. Modelling of explicit and executable business processes
- presentation http://fr.slideshare.net/samarin/how-to-use-bpmn-for-modelling-business-processes
- presentation "#BPM for business analysts: modelling procedure"
- enterprise pattern “Cloud-Aware Processes and Services” (CAPS) http://improving-bpm-systems.blogspot.com/2011/07/enterprise-patterns-caps.html
3. Relationship between EA, PMO, an SDLC methodology and ITIL
4. Enterprise pattern “#Cloud-Ready Estimation and Evaluation Procedure” (CREEP)
5. Relationships between EA and PMO
6. Enterprise pattern “Platform-Enabled Agile Solutions” (PEAS)
- Enterprise patterns: PEAS http://improving-bpm-systems.blogspot.com/2011/04/enterprise-patterns-peas.html
- Quick delivery of solutions via a PEAS-architected platform http://improving-bpm-systems.blogspot.com/2012/07/delivery-via-peas-architected-platform.html
- Enterprise patterns: PEAS - example and technique http://improving-bpm-systems.blogspot.com/2013/02/enterprise-patterns-peas-example-and.html
- Quick delivery of solutions via a PEAS-architected platform - mini-projects http://improving-bpm-systems.blogspot.com/2013/02/quick-delivery-of-solutions-via-peas.html
7. Melting pot
- the book “Improving enterprise business process management systems" http://www.samarin.biz/book
- the blog http://improving-bpm-systems.blogspot.com/
The use of SIC enterprise pattern can help to avoid some risks in EA practice. (The list below is taken from a recent LinkedIn discussion http://www.linkedin.com/groups/What-are-potential-risks-in-36781.S.232446262 )
- Incorrect understanding of business strategy
- Incorrect translating from strategy to architectural design
- Not Balance well on EA aspiration & EA Practicality
- "Waterfall" type of EA, lack of Agile practice - Incremental-ism, Improvement and Iteration.
- Framework or Frameless? How to leverage well?
- "We know what we are doing, even though we've never done it before"
- "We just need a tool"
- No focus on delivering quantifiable value
- Too focused on IT
- "Modeling the Universe"
- "Let’s collect data and see what we find"
- EA Dept hoarding information
- Unable to articulate the value proposition of EA
- Unable to communicate effectively with stakeholders
- Unable to execute in an appropriate risk management approach that matches effort (investment) with return