How Should we use Cloud?
How should we use Cloud? This is the key question at the start of 2013. The Open Group® conferences in recent years have thrown light on, “What is Cloud?” and, “Should we use Cloud?” It is time to move on. Continue reading →
Enterprise Architecture is not aimed at creating models. Is that so?
Architecture, in general, is about models. Hence, enterprise architects are to devise architecture, that is to model the enterprise. If you don’t do that, then you are not doing architecture.
Our relationship to technology isn’t only utilitarian. It…
Our relationship to technology isn’t only utilitarian.
It is also emotional.
Technology empowers us, it amplifies us in the world, and gives us super powers.
Maybe productivity is a not just a function of the design, but also of our attachment to it.
A…
Our relationship to technology isn’t only utilitarian. It…
Our relationship to technology isn’t only utilitarian.
It is also emotional.
Technology empowers us, it amplifies us in the world, and gives us super powers.
Maybe productivity is a not just a function of the design, but also of our attachment to it.
And maybe that emotional connection best expresses itself aesthetically – in personalisation, decoration and symbols of individuality.
And just maybe the reverse applies and standardising, commoditising, and depersonalising technology degrades the productivity of those who have to use it.
Types of Cost
When planning and measuring business benefits there are three basic contributing elements: revenues, costs and intangibles. If you look for guidance on “types of cost” most sources decompose cost types […]
The Art of Accepting Feedback
As practicing solution and enterprise architects we regularly present our work to our stakeholders for feedback. Those stakeholders range from mentors to peers to project teams to executive sponsors. In any and all of those situations, it is important to be able to accept feedback. In some cases the feedback will have been solicited by […]
Successful Enterprise Architecture using the TOGAF® and ArchiMate® Standards
The discipline of Enterprise Architecture was developed in the 1980s with a strong focus on the information systems landscape of organizations. Since those days, the scope of the discipline has slowly widened to include more and more aspects of the enterprise as a whole. Architects, especially at the strategic level, attempt to answer the question “How should we organize ourselves in order to be successful?” Continue reading →
Worst Methods for Enterprise Architecture
On the opposite side of the spectrum, Burton outlined her baker’s dozen of “worst” enterprise architecture practices. The EA methods that Burton said muddied efforts and missed overall business returns are as follows:
1. No link to business strategic planning and budget process.
2. Confusing “IT Architecture” with “Enterprise Architecture.”
3. Lack of governance.
4. Too much standardization.
5. Focusing on the art/language of EA rather than the outcomes.
6. Strictly adhering to architectural frameworks.
7. An “Ivory Tower” approach by IT and EA team members.
8. Lack of communication and feedback.
9. Limiting the teams to IT resources.
10. Missing performance measures.
11. Picking a tool before understanding business needs.
12. Focusing on the current state first and primarily.
13. Thinking that implementation equals completion.
2013: The year the Internet-of-Things takes-off?
I’ve been reading a lot about M2M/’The Internet of Things’, many pundits believe 2013 will be the year the concept finally goes mainstream – it’s been a while since its inception in the late ‘90s!
I have to say I…
Context of Architecture Roles
Today I was triggered by some posts where there was some opinions on where the line between Architecture and Design is.
One discussion was around an interesting blog post from Mark Wilson: “Where’s the line between [IT] Architecture and Design“. From my point of view Chris Potts answered it in a great way:
No line. An architect designs. | RT @martinhowitt: The line between architecture & design? By @markwilsonit markwilson.co.uk/blog/2013/01/w… #entarch
— Chris Potts (@chrisdpotts) Januar 23, 2013
There was a second Twitter post which caught my attention:
Architecture stops when detailed design begins. #TOGAF #EntArch
— Glen McCallum (@mccallumg) Januar 23, 2013
For both ideas I have the tendency to answer them very similar to Chris Potts: The Architect Designs, as I have also put it in my blog post GLUE Roles and Responsibilities. The [Role] Architect does deliver the [GLUE Discipline] Design. Nevertheless there is an enormous amount of specialized Architecture Titles. And it is in the nature of the discussions between the people who own the title to create clearly defined empires, so that there is preferable no overlap. Reality (for real Enterprise Architecture) is that there is always overlaps. And the good news is that the tension and friction created due to the overlap have a good chance to enforce creation of new (hopefully great) ideas.
So, don’t think you are an [xxx] Architect, but know you are, then you do not have to seek for a perfect definition. (There might be no chance to find the perfect answer, but just a working one. One that works for you only). The key message though is, that it is not a title, but a role. A role which will be fulfilled in any given context, because [Enterprise] Architecture inevitable happens, no matter if the people who perform it are titled in the right way or not.
Wearables and Pervasive Computing: A 2013 Trend to Consider
It’s difficult as a CIO to gauge whether or not to add the latest technology to your portfolio. You don’t want to chase a fad without business value or get left behind. Balancing your technology portfolio is a delicate dance that involves making the right investments at the right times for the right reasons. Today, PwC released its list of 2013 Top 10 Technology Trends for Business. I suspect that many CIOs will see Pervasive […]
If you liked this, you might also like:
#ogChat Summary – Big Data and Security
The Open Group hosted a tweet jam (#ogChat) to discuss Big Data security. In case you missed the conversation, here is a recap of the event. Continue reading →