Creating a Partnership Between the PM and the Architect
Udi has a great post, Money?! Schedule?! But I
Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.
© 2003-2008 Johanna Rothman | Email Johanna | RSS feed | Sign up for AYE newsletter | Workshops | Consulting | Podcasts | Johanna's site
Udi has a great post, Money?! Schedule?! But I
2 Comments so far
Leave a comment
Hello Esther. I like your conclusions here, but I’d push farther. The architect doesn’t actually develop the software, right? And according to this narrative, he doesn’t want to be held accountable to time, schedule, or cost, right?
In that case, I have to ask - What does the architect _do_? What is he (she) responsible for? How is that measured?
My cousin is an architect - he has a degree in architecture, and, like, he designs buildings and stuff. Me, I spend three years in McGraw-Hills construction information group. My conclusion from all that is simple: A lot of what passes for software architecture today is just people who want to be highly compensated and not have much responsibility.
Not, all, just a lot. So when I hear stories like that one, I’m, well, not surprised.
–heusser
By Matt H. on 02.02.07 1:28 pm
oh, and I’m a complete fool, and you are Johanna and not Esther, and we allready had this conversation last march. My mistake. Tabbed browsing is killing me …
By Matt H. on 02.02.07 1:30 pm
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>