Architectural Practice

Home/Tag:Architectural Practice

Form, Structure and Function – Architecture is NOT Emergent

I have recently been studying the implications of Agile on enterprise and technology architecture. As a part of that I was looking through traditional architects relationship to other team members (structural engineers, construction, plumbers, electricians, etc). This has always been a passion of mine as a student of professions but this time I was looking

Design By Committee

Can a team of experienced, empowered developers successfully design the architecture of a product? Sure. Can a team of experienced, empowered developers successfully design the architecture of a product without a unified vision of how the architecture should be structured to accomplish its purpose? Probably not. Can a team of experienced, empowered developers successfully design

Finding the Balance

One of my earliest posts on Form Follows Function, "There is no right way (though there are plenty of wrong ones)", dealt with the subject of trade-offs. Whether dealing with the architecture of a solution or the architecture of an enterprise, there will be competing forces at work. Resolving these conflicts in an optimal manner

Beware Premature Certainty – Embracing Ambiguous Requirements

Many see ambiguity as antithetical to software requirements. However, as Ruth Malan has observed: Pick your battles with ambiguity careful. She is a wily foe. Not to be dominated. Rather invited to reveal the clarities we can act on. Make decisions with the understanding that we need to watchful, for our assumptions will, sooner or