Think Enterprise First
Todd Biske on why scope is where project management and enterprise architecture come into conflict.
Enterprise Architecture
Heal the Eternal Disconnect Between Project Managers and Enterprise Architects!
Heal the Eternal Disconnect Between Project Managers and Enterprise Architects!:
Excellent rumination on the relationship between project management and enterprise architecture. From,
@elbanoitca
Design is scope. The budget is a fence that will make good…
Design is scope.
The budget is a fence that will make good neighbours of project management and architecture.
The more design (scoping) you do before the budget the better.
The less design (changing scope) you do after the budget the better.
The Open Group SOA Governance Framework Becomes an International Standard
The Open Group has moved the technology industry forward yet again with its second international standard on SOA.The Open Group SOA Governance Framework is now an International Standard, having passed its six month ratification vote in ISO and IEC. This…
Challenge the Status Quo and Advance Business through Cloud Computing
In my previous post, I talked about how Enterprise Architects can (and should) drive cloud strategy and planning. Today, I would like us to take a look at a larger issue for EAs, CIOs, and anyone invested in IT strategy…
Enterprise as story: a cafe example
How can we use a vision or story as the anchor for an organisation’s business and enterprise? How do we link that story to decisions and actions in everyday business? This is a theme that came up in a great…
Definition as EA anti-pattern?
If you’re an enterprise-architect and you haven’t yet come across Ric Phillips‘ wonderful EA Patterns blog, go over there right now: you’re in for a treat! To mix metaphors somewhat, I’d have to say it’s a national-treasure for the trade.…
Enterprise Architecture state and causes (iii)
While the customers and stakeholders are not complaining, little can be done. This is the main reason for the lethargy of EA.
Architecture-by-definition is an anti-pattern. The goal of a…
Architecture-by-definition is an anti-pattern.
The goal of a definition is to remove noise.
You add another layer of noise when your definitions are model-specific sub-definitions for commonly understood terms. For example: service, product, capability, or system.
Special definitions introduce an additional cognitive load that easily outweighs the benefits of a more sophisticated model.
Between the boxes
What happens when people get too fixated on the ‘boxes’ in our models and frameworks? And what can we do about it in enterprise-architecture? This one’s actually a follow-on to the previous post about ‘It depends…‘, but it starts with…
“It depends…”
What’s the one phrase that enterprise-architects use time after time, and that drives almost everyone else crazy? Well, it depends… “It depends.” Yeah, we know it prob’ly depends, but just gimme the answer, willya? Frustration indeed… Going back to a…
How anti-clients happen (and what to do about it)
Are there any anti-clients for you in your enterprise? Who are they? How did they turn so actively against you? And what can you do about it, and them, in the design and implementation of your enterprise-architecture? Who are anti-clients? To…