Showing posts with label James McGovern. Show all posts
Showing posts with label James McGovern. Show all posts
Tuesday, January 20, 2009
2009 Focus for EA
In a recent article by James McGovern, he pointed out that companies are focusing too much on the processes and loosing the human aspect of the enterprise. He also believes that IT processes are not truly saving businesses money, and is certainly not getting more efficient. Do you believe this is true for EA? Do enterprises need to focus more on the human aspects of EA?
Monday, January 12, 2009
Worst practices of Enterprise Architects
James McGovern recently posted a list of the ten worst practices of enterprise architects. Here are his top 5:
1. Instead of focusing on perception management, concentrate on becoming a skilled negotiator. We need to strike balance between technical complexity and business needs. Don't just change perception, focus on reality.
2. Spread the wealth. Enterprise architects who are the single source of knowledge on a given topic within an enterprise is dangerous. We all need to plan for when we all get thrown under the bus and the best way to do this is to make all decisions transparent and all communications open.
3. Governance is not about financial controls but is all about a behavior model. Command and control doesn't work, neither does design by committee. Remember that the best architectures are realized by self-organizing teams.
4. Don't be afraid to ask for help. Enterprise architecture is not about posturing and hand waving. It is important to understand your limitations and ask for help when you don't have a clue.
5. Think like a developer. Way too many architects throw daggers at developers, yet we haven't thought about what it is like to walk in their shoes. By using minimalist architecture approaches such as keeping things simple, you increase the odds that the code will be as high quality as the architecture.
For the complete list, click here. Were there any practices you noticed missing from the list?
1. Instead of focusing on perception management, concentrate on becoming a skilled negotiator. We need to strike balance between technical complexity and business needs. Don't just change perception, focus on reality.
2. Spread the wealth. Enterprise architects who are the single source of knowledge on a given topic within an enterprise is dangerous. We all need to plan for when we all get thrown under the bus and the best way to do this is to make all decisions transparent and all communications open.
3. Governance is not about financial controls but is all about a behavior model. Command and control doesn't work, neither does design by committee. Remember that the best architectures are realized by self-organizing teams.
4. Don't be afraid to ask for help. Enterprise architecture is not about posturing and hand waving. It is important to understand your limitations and ask for help when you don't have a clue.
5. Think like a developer. Way too many architects throw daggers at developers, yet we haven't thought about what it is like to walk in their shoes. By using minimalist architecture approaches such as keeping things simple, you increase the odds that the code will be as high quality as the architecture.
For the complete list, click here. Were there any practices you noticed missing from the list?
Subscribe to:
Comments (Atom)
