Название: More on practice for Enterprise Architecture: Roles, skills, engagement and problem-issues
Автор: Tom Graves
Издательство: Leanpub
Год: 2022-12-12
Страниц: 229
Язык: английский
Формат: pdf (true), epub
Размер: 10.1 MB

This anthology from the Tetradian weblog explores more about real-world practice for enterprise-architecture and its related disciplines.

This book includes about 35 posts and 40 images from the weblog. These posts are split into four groups:

- Practice: Roles and Skills - assesses the various types and needs for skills in architecture practice and more.
- Practice: Engagement - summarises the challenges of engaging stakeholders and others in the processes of change, and practical tools and tactics to help that happen.
- Practice: Influences - suggests examples of elements and concerns that can influence architecture practice in various ways.
- Practice: Mispractice - describes examples of flawed discipline and poor practice that can or do cause damage to change-projects and to architecture itself.

The nearest to a conventional job-description for what I do is ‘Enterprise Architect’ – the structure of large organisations, with somewhat of an IT bent. So take a look with me at the listings on Jobserve UK: go to their site; select Job-type ‘any’, Within ‘1’ [day], and IT jobs only in the ‘Industries:’ list; then enter ‘architect’ in the box, and click ‘Go’. What you’ll get, on a typical day, is a list of about 400 jobs, all of which claim to be IT ‘architect’ roles of some kind or another. But of these, barely a handful – two or three at most, usually – are what I would think of as real enterprise-architect roles; the rest are… well… ‘architects’ of what, really?

In short, in most cases it seems that ‘architect’ means pretty much exactly the same as the old term ‘analyst/programmer’, except that these days said analyst/programmer is expected to know something about more than just the one application, and to have some idea of how to get the infernal things to actually communicate, in some fashion that doesn’t result in the outright demolition of all the data (the latter being a more frequent occurrence than the IT trade is generally willing to admit…).