Over at CIO, they've got a great article for the managers of enterprise architects. Is one new to your company? They suggest following these simple rules:
1. Establish clear goals and expectations before day one.
2. Introduce the EA to the key players at a single meeting, no later than day two.
3. Run blocker for your EA.
4. Don't expect your EA to drive the business.
5. Your EA is not just the über-tech-geek.
Thursday, February 5, 2009
Wednesday, February 4, 2009
Understanding Your Enterprise Architect: A Guide for Managers
If you're a manager of an Enterprise Architect or if your manager could use a little push in the right direction, JP Morgenthal's piece in CIO offers some tips to keep the peace and the productivity flowing.
1. Establish clear goals and expectations before day one.
2. Introduce the EA to the key players at a single meeting, no later than day two.
3. Run blocker for your EA.
4. Don't expect your EA to drive the business.
5. Your EA is not just the über-tech-geek.
For the rest of his article, click here.
1. Establish clear goals and expectations before day one.
2. Introduce the EA to the key players at a single meeting, no later than day two.
3. Run blocker for your EA.
4. Don't expect your EA to drive the business.
5. Your EA is not just the über-tech-geek.
For the rest of his article, click here.
Labels:
changing EA climate,
CIO,
EA news,
Evolve network,
JP Morgenthal,
managing EA
Monday, February 2, 2009
SOA needs supporting architecture
Dan Rosanova recently wrote a post at CIO about how many companies often adapt SOA because it is what many companies are interested in when starting architeture. However, he notes that while SOA is a good thing, it may not perform to its higest potential if there aren't other architectural software structures in place to support it. Read the full article here.
Subscribe to:
Posts (Atom)