http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html I've spoken to, interviewed and screened a lot of CVs/resumes from senior developers and architects recently and there are a lot of baton hand-offs going on. One of the great things about small or agile teams is that the same people capturing the ... en Simon Brown Mon, 14 May 2007 17:15:07 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html#comment1179162907676 I agree, IT Architects (whatever they call themselves) need to be involved all the way through. Unfortunately clients are not always willing to pay for an expensive architect to be involved to delivery:<br /> <i>"You've got an architecture now, why do you need an architect?"</i> say they.<br /> In these sorts of things, it is often interesting to look at the (similar, but more mature) construction industry. My impression is that architect there is <b>not</b> involved during build? Anyone know?<br /> Tom Tom Grey http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html#comments http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html#comment1179162907676 Mon, 14 May 2007 17:15:07 GMT http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html#comment1179162786666 Simon, your observations correspond with mine regarding <a href="http://opensourcecto.blogspot.com/2007/05/should-architects-code.html">whether or not architects should code</a>. While we do need to spend some time in the ivory tower once in a while, we also need to keep in touch with the organization. wpbarr http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html#comments http://www.codingthearchitecture.com/2007/05/14/the_hand_off.html#comment1179162786666 Mon, 14 May 2007 17:13:06 GMT