Reply to: Architects

[Notascooby]

So basically there is a high level Enterprise Architect, who may not have much (or any) technical knowledge but has detailed knowledge of the business at a high level and has the ability to transfer business objectives into usable requirements. Under them is the Solution Architect who usually pulls together multiple Technical (of what ever name, Application, Network, Infrastructure, Secuirty etc) Architects who have detailed knowledge of their specific technology.

So in that respect an EA is sort of a career progression for Business Analysts? Technical Architects are the old fashioned SME for which ever technology they work with and Solution Architects have a bit of both?

In the past I have thought about what the next skill I should learn, not to move away from my area of work but to better understand those I work with so maybe TOGAF might be a good bet as well as SCRUM Master to get an idea of the Design and Development phase of the SDLC

As Roy Walker would say...."It's good but not quite right - 5 seconds, here we go"

The BA would become a Business Architect - he could become an EA, which should be mainly about direction setting, patterns and governance but as mentioned "enterprise" banded around instead of "senior".

So you've started off describing a Business Architect.

As for the SA - you'll find they come from all walks of life, so some will be stronger in certain areas. i.e. I know cock all about tin and very little about networks but I'm strong on applications coming from a development background.

The SA is usually the PM's righthand man/woman - he coordinates the design deliverables and pushes it through the governance process. The bigger the org, the further removed the SA from the coal face (in general) and the more likely that all the architects piss off to an ivory tower and lose sight on what their primary aim is - delivery and concentrate more on making project jump through a miriad of hoops and protract the delivery timelines.

Unfortunately this control is also what is necessary within big organisations to prevent the proliferation of duplicate and unsupported technolgies and piss poor design.

[SimonMac]

So basically there is a high level Enterprise Architect, who may not have much (or any) technical knowledge but has detailed knowledge of the business at a high level and has the ability to transfer business objectives into usable requirements. Under them is the Solution Architect who usually pulls together multiple Technical (of what ever name, Application, Network, Infrastructure, Secuirty etc) Architects who have detailed knowledge of their specific technology.

So in that respect an EA is sort of a career progression for Business Analysts? Technical Architects are the old fashioned SME for which ever technology they work with and Solution Architects have a bit of both?

In the past I have thought about what the next skill I should learn, not to move away from my area of work but to better understand those I work with so maybe TOGAF might be a good bet as well as SCRUM Master to get an idea of the Design and Development phase of the SDLC

[Mich the Tester]

A confession!

[Platypus]

Is 'architect' what you become if you're too thick to be a developer and too feckless to be a tester?

[Mich the Tester]

A similar fate has befallen the recruitment industry. Every f***ing job title in recruitment has the word "talent" attached to it

And all these years I thought I was a 'human resource'.

[Notascooby]

No chance SueEllen, I've been carefully orchestrating the source of these project cockups due to the aforementioned to the management over the last few years.

His time is almost up before he's cast unto the wilderness.

Well done - most become PMs, some by doing a short stint at being a BA (not properly, glorified secretary role - i.e. ask questions, write down answers - no value add) then decide they're ready to PM as they got M$ Project installed.

[hyperD]

If he arse licks enough won't he get promoted to proper management?

No chance SueEllen, I've been carefully orchestrating the source of these project cockups due to the aforementioned to the management over the last few years.

His time is almost up before he's cast unto the wilderness.

[bobspud]

Where I work has just sacked all the architecture team. "You can all do your own architecture".

Makes alot of sense - everything will run alot smoother.

Ha ha ha...

That's what they think until they look to the documentation in a year or so and realise that No two designs have the same content and standards vary...

Architecture is a poncy fart arsing gaff for most companies but that's because they are not doing it properly.

At the point that an architect cannot roll their sleeves up and show an engineer how it's done properly, they should probably go and be a business analyst or lobotomised.

Enterprise Architects define the business view and the ABB's
Then the solution and technical architects should use those views and artefacts to take the visions from logical to physical designs. They then show the engineers how they want to have the software or hardware built.

I have been writing documentation and designing systems since 2001 but it took years to balance the weight and content properly.

[shaunbhoy]

Every f***ing job title in recruitment has the word "talent" attached to it

Fook me!! An oyxmoronic epidemic!!

[Gentile]

A similar fate has befallen the recruitment industry. Every f***ing job title in recruitment has the word "talent" attached to it

I thought you were the Chief Talent Architect, Dodgy?

[DodgyAgent]

A similar fate has befallen the recruitment industry. Every f***ing job title in recruitment has the word "talent" attached to it

[SueEllen]

As is often with this dichotomy of talents, he has no personal, empathy or leadership skills whatsoever. He makes the Rain Man look like Clarence Birdseye.

And he has absolutely no current developer skills whatsoever.

Technically, he's ****ed when they eventually boot him out for being such an incompetent arsewipe.

If he arse licks enough won't he get promoted to proper management?

[hyperD]

Team leader is what a thick developer becomes then hopefully they just fk off.

Yeah, there's one of these at the clientco: a failed developer that's getting on a bit so via the "dead man's shoes" principle has been promoted to run the team.

As is often with this dichotomy of talents, he has no personal, empathy or leadership skills whatsoever. He makes the Rain Man look like Clarence Birdseye.

And he has absolutely no current developer skills whatsoever.

Technically, he's ****ed when they eventually boot him out for being such an incompetent arsewipe.

[louie]

A software/data Architect designs at a higher level usually on larger systems, it is a real role and pays tulip loads.

[Notascooby]

Is 'architect' what you become if you're too thick to be a developer and too feckless to be a tester?

Very few architects could be a good tester - too easily bored. I do write fantastic test plans and scripts though. Most of which confuse the hell out of testers, not so much test managers.

Team leader is what a thick developer becomes then hopefully they just fk off.