From: 	Joseph D Armstrong[SMTP:jdarmstr@us.ibm.com]


I have been working in an architect role at IBM for the last 3 years.
While I am not familiar with the Agile processes, your description of the
workshop intrigues me as that is exactly the environment that I
continuously face.  I work in the server group at IBM and in particular in
what we call the Service Processor.  It is an embedded system that tests,
initializes and monitors the hardware of the low, mid-range and high-end
IBM servers.  Overall, the organization I work in has roughly 300
developers.

Typically the architects here are involved very early on a new project.
There is some "architecting" done.  However, not all software components
can be rewritten so there is always a fair amount of carry over from past
designs.  The architects role during this has been to assist new
development to create better designs as well as provide a smooth port of
existing code and fit the two together.

As a project matures in development and is eventually shipped the architect
typically becomes less and less involved except during those times that
problems arise or new features are required.  Since the area I work in is
very closely tied to the hardware and the product life can be ten or twenty
years there is constant change as new hardware is introduced and new
features are added to existing products.  Thus, the architect is
continuously involved in past projects.

In the last few years we have pushed to become involved earlier in product
development to the point where we are now working with the hardware teams
during system design and even chip design.  While this has helped immensely
in building a more integrated system it also stretches the architect
through a longer period of product time.

My personal view is that the architect must be involved as early as
possible in the product design.  At least for the server products that I
work on the software is very dependent on hardware and having the software
architects and hardware architects work together is important.

At the same time I also share your same view that the architect's job does
not end as soon as the initial design is complete and approved.  There are
really two reasons for this: Most designs today go through an iterative
approach.  That is, the design changes as it is implemented and integrated
with other components.  Particularly as new requirements are added to a
product all through the development cycle.  The architect must be involved
to keep the spirit of the original architecture alive.

Secondly, with constantly evolving software on existing products the
architect must be involved to maintain the integrity of the system design.
The architect carries the big picture and is often consulted about the best
way to integrate a new function and in our case to provide an initial
sizing of resource expense for new functionality.

Through all these it is important to work closely with the design and
implementation team.  There are many details that, at least in my work, the
architect cannot possibly know.  We gather information as much as we
provide information.  We mediate compromise between component owners for
the best solution in interfaces and functional balancing.  It is a
multipurpose job.


Joe Armstrong
ESW Architect
Phone: 507-253-1393  T/L 553-1393
Fax: 507-253-2870
e-mail: jdarmstr@us.ibm.com