Re: Architects outside the teams
- In article <4922493B.8040101@...>,
George Dinwiddie <lists@...> wrote:
> Patrick Debois wrote:Not a monthly party (great idea!) but when I was director of
> > My experience is when architects stay too long architect, the
> > possibility exists that they stop innovating.
> > They might repeat themselves all the time and if they are dedicated
> > architect, they often lack the feedback of 'real' day to day issues.
> > A dedicate group IMHO would amplify this notion and or elite thinking.
> > While it is crucial they keep on feeling the pulse of the projects.
> > I also saw the opposite, all agile teams working happily together, less
> > concerned with the global interaction but optimizing things in 'their'
> > project.
> > How about rotating , architects from team to team.
> How about a monthly party where all the teams meet over food and drink
> and discuss what they've been doing. If someone needs what someone else
> has built, they can work out the details.
architecture I would coordinate reuse.
When a team needed a feature/module it would build it to suit its needs.
As other teams needed similar/identical functionality they would use
what the first team built and enhance to suit its needs.
Thus we had an ever expanding collection of known-to-be reusable code.
Worked very very well.