Subscribe: A Day in the Life of an Enterprise Architect: Tackling Issues in Technology Architecture
Added By: Feedage Forager Feedage Grade A rated
Language: English
architect  change  code  company website  company  cut code  developer  manager  months  page  problem  production system  production  website 
Rate this Feed
Rating: 2.4 starRating: 2.4 starRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: A Day in the Life of an Enterprise Architect: Tackling Issues in Technology Architecture

A Day in the Life of an Enterprise Architect: Tackling Issues in Technology Architecture

Follow one Enterprise Architect with a wide variety of experience in various IT roles, including Computer Developer, Database Designer, Project Manager, and Technical Architect, as he shares unique insights on technology architecture, investment, and oper

Published: Fri, 15 Dec 2017 17:05:05 +0000


And then the problems started

Wed, 25 Jul 2007 08:23:40 GMT

The weekly change meeting came and went. Unfortunately our developers one-page udpate to the company's website didn't make the agenda since they ran out of time to review and approve the change. But it made next weeks meeting... The change review board didn't think the change warranted much consideration which was a relief for the developer. They scheduled the change for the weekend after next since this weekend they had some urgent updates to do and the risk of so much change was too great f

Change for the better

Thu, 19 Jul 2007 10:58:38 GMT

Almost done now, the end is in sight. Our intrepid developer has spent nearly five months now trying to make a one-page delivery to the company's website. He has a two-page form from the Systems Implementation team, however, and it seems to be asking for stuff he hasn't got. Well, he was asked for technology details and disk space, this was no problem. Two Directors signatures were a little of a problem though, because his boss had just left for a weeks vacation break, and two other Dir

Variety is the spice of life?

Wed, 18 Jul 2007 09:01:53 GMT

So, as an aside to my little story about the developer's frustration, I was thinking about how we could improve on the efficiency of the development model, to get to a better place... If our developer doesn't want to do all these different jobs on the way to productionising his code, the jobs such as Project Manager, Business Analyst, Architect, Designer, Auditor, Administrator etc, then we need to specialise and stream the work. Imagine for a moment, a world where the developer does his

Ha Ha, you must be joking

Mon, 16 Jul 2007 10:27:33 GMT

Our frustrated developer has been waiting over four months now to get his one-pager onto the Company's website, and he still can't see the light at end of the tunnel, if the light actually exists at all (In religious terms he's moved from firm believer into agnostic). Today he received an email with an enormous form attached that provides details to the Systems implementation team so that they can put his one-pager into production. They wanted to know: 1. Technologies involved and vers

Let's get this thing in

Thu, 12 Jul 2007 09:02:00 GMT

Our brave and exceedingly patient developer has been trying to put his new Internet Page on the Company's Website for 4 months now, and finally last week he got to write the code. He did it, just as he said he would, all complete and tested in one day by his own fair hand on his desktop machine. He's ready to go, let's see it up on the site then... He rings the Service Delivery Team, the last bastion of defense of the Data Centre and asks to get his code "promoted" onto the Production System.

Let's cut the code.....

Wed, 11 Jul 2007 08:47:11 GMT

Finally, our very patient developer has got the go-ahead from the Architect to cut the code. This is the culmination of 3.5 months of patient waiting, discussing and analysing and a veritable mountain of documentation. His original estimate of one days development work is about to happen, and he's raring to go.... Except, by now priorities have changed. He's deep into a long-running recurrent problem with the Production System, and his manager won't let him go until it's finished. He's alr

Is this legal?

Mon, 09 Jul 2007 09:32:28 GMT

This is a little off-topic for my blog, but I couldn't resist asking basic legal questions here, what can I record and playback privately without incurring the wrath of the Recording Industry Stasi? His original estimate of one days development work is about to happen, and he's raring to go.... Except, by now priorities have changed. He's deep into a long-running recurrent problem with the Production System, and his manager won't let him go until it's finished. He's already been at it for

And so to Design

Thu, 05 Jul 2007 16:20:30 GMT

As regular readers of this blog will know, our developer has been patiently waiting for his chance to cut code for his one-page addition to the companies Internet Site, and the going is decidely tough. We introduced the subject of why changes take so long to implement in our big corporates in "Seven steps (or more) to success", started our magical journey in " Tighter than sardines

Wed, 04 Jul 2007 07:52:41 GMT

A recent report by Symantec highlighted that within two years 66% of our Data Centres are going to run out of space. Whilst I would readily admit that it is good news for the IT Industry as a whole that that our services are in increasing demand, it's bad news in that despite the enormous strides we've made in technology, we don't seem to be keeping pace with demand. What's going wrong? Well I think it's simple, we need faster machin

Analyse, analyse....

Thu, 28 Jun 2007 09:25:26 GMT

The Definition phase of a Systems Development Life Cycle, sometimes called the Analysis phase, is really a requirements analysis, a phase where we can really understand what we are trying to do for our business customer. Yes, I know that we already known what we need to do, after all our developer has talked to the business customer and written it down on his notepad. And, that Business Analyst that they kidnapped from the other project has already written it down in the Initiation Document.

Whoa, you're going too fast

Tue, 26 Jun 2007 10:22:53 GMT

So, as I said in my last blog, I'd like to look at all the things that make our 1 day development task turn into a 1 year deployment project. Today I'll turn my attention to the first step in the System Development Lifecycle, that of Initiation. Some people would say that Initiation is where we have identified a need for technology to solve a business problem. I'd say rather that everything is a need, but it's really a question of business priority. So, the developer has some feedback from

Seven steps (or more) to success

Mon, 25 Jun 2007 08:17:07 GMT

I was asked last week to help some colleagues estimate the work involved in building some web pages and business logic as part of our latest and greatest project. As a developer myself (Yes, I keep my hand in), I have never ceased to be amazed at the length of time our wonderful corporate bodies take to do even the simplest of things. Actually, "the simplest of things" is the single most inefficient thing you can do today, but more of that later. To give you a little focus I told the

You don't have to be a Hemingway

Fri, 22 Jun 2007 05:28:31 GMT

OK, let's get this documentation thing straight; you don't want to do it, right? Of course you don't, it's not within your nature, it's not what you embarked on a career in IT for. The fundamental truth is, you don't want to produce documents becuase you never wanted to be a writer in the first place. Writing is an art form, it's a creative art, and the desire to create in this way is either in you or it isn't. But it shouldn't be this way. Documentation in the IT sense should not be an

Picture this (with apologies to Blondie)

Thu, 21 Jun 2007 04:20:58 GMT

Communication of ideas in this high-speed, attention-deficient world is one of our greatest challenges and, although we have this wonderful Internet with its millions of sites and gazillions of consumers of information, we still can't communicate well. In IT the most powerful tool we have is not the written word but the picture. You know this, you know that we rush to PowerPoint or Visio or to paint the picture. The picture works because it's the way our m

So, what does EA do for us?

Wed, 20 Jun 2007 03:59:34 GMT

So, we've made sure that we've delivered, the solution is into production and the Business have patted us on the back. And best of all, those Enterprise Architects didnt get in our way. What do we have then? Well, we've probably got more boxes, more heat, more power usage, and less space in the Data Centre. We've also got more maitenance overhead (Business-As-Usual maintenance, just keeping system ticking over, accounts for 75%-85% of major corporations total IT spend). We've also got m