The role of the Software Architect in successful projects

A lunchtime briefing at the Jersey branch of the BCS

Admittedly the "Coding the Architecture" audience for this is probably kind of small (hi Dave!), but I'm presenting a session at the Jersey BCS in a few weeks entitled "The role of the Software Architect in successful projects".

The IT industry has a love/hate relationship with the Software Architect role, with many organisations dismissing it because of their negative experiences of architects that dictate from ivory towers and aren't engaged with the actual task of building working software. This reputation is damaging the IT industry and inhibiting project success.

Things need to change. This session looks at some of the reasons why software projects fail and how a hands-on software architect can be invaluable in addressing these issues to drive the project to a successful conclusion. Software architects are here to help, not to hinder.

The session is aimed at anyone undertaking software development projects; including developers, architects and IT managers. It will take place on Thursday the 13th of November 2008, 12:00 in the Ouless Room at Jersey Museum. E-mail at to reserve your place.

p.s. if this sounds familiar, it's because it is

About the author

Simon is an independent consultant specializing in software architecture, and the author of Software Architecture for Developers (a developer-friendly guide to software architecture, technical leadership and the balance with agility). He’s also the creator of the C4 software architecture model and the founder of Structurizr, which is a collection of open source and commercial tooling to help software teams visualise, document and explore their software architecture.

You can find Simon on Twitter at @simonbrown ... see for information about his speaking schedule, videos from past conferences and software architecture training.

Re: The role of the Software Architect in successful projects

what a great summary. Hebrew has a saying: Tafasta Merube Lo Tafasta. Which means: if you try to catch everything, you will catch nothing. An architect must always code something in his project, and never succumb to the need to manage everything. By coding something, you can get the feel to the code, understand the daily hurdles your developers have to tackle, and get off the ivory tower. that's why I like the name of the blog so much.

Add a comment Send a TrackBack