Add a comment

 

Re: The frustrated architect

In my role as an architect I wouldn't consider writing any 250 page doc a good use of my time - that's too much traditional BA or PM for me. I see my role as coordinating the efforts of others so that they deliver appropriate docs, if necessary, & more importantly ensuring that discussions have taken place so everyone is more or less on the same page. I would also consider high-level design of any proposed system, or changes, to ensure they fit within the enterprise's strategic platform which includes all other software systems under the dept's control. Detailing requirements (different from a project board's functional spec) would only be done within a product backlog. The more I use them the more I become convinced of their efficacy. This then feeds back up to the business customer for their buy-in. The developers then get involved with the business customer to define product backlog items into tasks that they complete. If you have good senior developers they should adhere to architectural guidelines instinctively & they should also be empowered to review code to increase a dev team's sense of ownership & responsibility. As an architect I'd ensure this was happening. Finally, at the code level, if there is something new &/or particularly tricky I would get involved with prototyping/solving it. Obviously there are many touch-points along this route, but the key parts for me are: communication, strategy & design.

Re: The frustrated architect


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).