Yep, I’ve finally Got Round To It: I’ve created a full set of materials for an EA training-course, building on the whole-of-enterprise approach that I’ve championed all of these years. (Whole-of-enterprise, that is, in contrast to the arbitrarily-constrained IT-is-the-centre-of-everything approach that almost everyone else still seems to promote…)
It’s based on the Five Elements structure that I’ve used in many places in my work, such as – in the diagram below – the relationships between strategy, tactics and operations:
In practice, it’s split into six sessions:
- Introduction – why enterprise-architecture, architecture and design, architecture and services, architecture as story, core framework (Five Elements)
- Part 1: Purpose – overall business-context, stakeholders, unifying story, vision and values
- Part 2: People – people in enterprise-architecture, stakeholder-engagement, viewpoints, skills, power and responsibility, politics of enterprise-architecture
- Part 3: Preparation – governance, tools and frameworks, trade-offs and uncertainties, everything-as-a-service, design for uncertainty (backbone and edge), viable services, service-context, architecting for change
- Part 4: Process – complexity, tame-problems and wicked-problems, innovation and invention, sensemaking and decision-making, role and development of checklists
- Part 5: Performance – meaningful metrics and benefits-realisation, continuous-improvement and the learning organisation
There are ‘practicals’ – breaks for practice and experimentation – throughout each of those sessions. I also recommend that each participant (or group of participants) bring with them a real-world challenge that they want to work on during the course.
(This is an intentionally-generic framework, appropriate for any type of architecture. That’s why I haven’t yet mentioned business-models or reference-architectures or application-architectures or the like: to me, those are all instances of architectures, examples of what we might choose to work during the course, rather than explicit or mandatory ‘content’ to apply in every architecture. That’s an important distinction, actually…)
It can be run as:
- half-day (not recommended, because it gives almost no time for practicals – but some people would need to do it that way)
- one-day (minimum recommended – gives useful time for practicals plus some application on participants’ worked-examples)
- two-day (recommended – gives more time for in-depth practicals, plus equivalent of whole day on worked-examples)
The Introduction session is also short enough, and visual enough, for use as a standalone ‘introduction to enterprise-architecture’, for time-starved executives and suchlike.
Pricing would vary dependent on travel-costs, number of participants (for training-materials and reference-sets), commercial versus not-for-profit and other factors – but would be comparable to other courses of this type.
Given my various rants about certification and the frequent evils thereof, the only ‘certification’ offered will be a pretty certificate to say that a participant has done the course. If anyone needs one, that is.
More details on the Tetradian website, eventually. For now, if you’re interested in doing this, or perhaps organising one for a company or as an open-to-the-public event, please let me know?
Many thanks to all, anyways.