What should an Architect do in Delivery?

This is a fundamental question asked by many of colleagues that I worked with and people in my mentor network.

In my definitions, Architecture is a well layed out principles, patterns and constraints of a software solution or a product. Delivery is a process and/or mechanism governing the implementation.

Which are clearly two different & distinct entities. Processes & mechanisms in delivery has nothing do with principles or patterns used in architecture. (Unless some one want to "architect the delivery" :) which is a different ball game all together)

Then what should an architect do in delivery?

Here is my view point, an architect have to wear different caps in delivery, but he/she can still be an architect.

Here are those delivery caps,

• Guide the team & govern the implementation so that architecture principles are not compromised.
• Consume & control the change to +ve limits of architecture.
• Be a coach and influence practices so that end solution delivered is not fragile.

But how far can he/she be a "true" architect in delivery? answer to this, I feel, is depends on individual preferences & strengths. In my opinion only architects can do this job better, no one else.