Anne Thomas Manes wrote: > Dan Creswell wrote: > > Are you suggesting that IT should be pitching to its own business? That > would be more like a consulting arrangement than an in-house unit to > unit thing? Interesting implications for future need for in-house IT? > > Yes, I am. Every IT project should have a business case. Every
But is the business case produced by IT or the business itself? I can imagine the business formulating business cases and IT tendering in response, but that's the reverse of the above, I think? > organization has a backlog. How do you define priorities to projects? > You must idenitfy the business need and weigh it against all the other > looming projects. > > (2) I think it's way beyond most human beings to have such a global > view of their business that they can build such a roadmap. And how long > would it take for the view to be out of date and the roadmap need > re-doing with the associated knock ons? > > But this is an enterprise architect's job. The EA frameworks are tools Sure, I accept it's their job - what I'm getting at is that I'm not sure how achievable the targets of such a job are. It all sounds fine in theory............... > to help the EA obtain and maintain this global view of the business. The > roadmap must be a living document, and EAs must constantly reassess the > situation. > > Anne > > On 6/22/06, *Dan Creswell* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > > Anne Thomas Manes wrote: > > You're sounding pretty cynical, Dan. > > > > Probably - I've been in the industry 20 years and seen these cycles > over > and over. In the end, it always comes down to humans, politics and > whether or not you know how to employ good business practices. > > > > Todd's spot on. You can't just complain about the situation and > expect > > thing to get better. If IT wants to be more aligned with the > business, > > Indeed you can't just complain so lets flip the IT thing around - if > business wants to get the most out of it's IT it needs to maybe try > building some bridges too. For me it's all about dialogue and > co-operation with shared goals and as you say that's cultural and goes > way beyond SOA IMHO. > > Both sides must build bridges and figure out together what needs to be > done to be successful. > > > > then IT has to start developing solid business cases to justify new > > investment. And -- as you say -- they have to focus on solving > business > > issues, not on technology. > > > > Are you suggesting that IT should be pitching to its own business? That > would be more like a consulting arrangement than an in-house unit to > unit thing? Interesting implications for future need for in-house IT? > > > > But how can you effect this type of change without taking an > enterprise > > perspective? As I said in my post, the role of the enterprise > architect > > is to document where you are today, determine where you need to > go, and > > define a roadmap to get there. EA frameworks help them do this. > > > > Sure but the enterprise architect has to be empowered to do this and > have a nice global view to make it all work: > > (1) Most people would have a hard time figuring out just how to empower > such an architect. Heck I suspect in many organizations you'll find > that a lot of people who should be in contact with the architect don't > even know they exist. > > (2) I think it's way beyond most human beings to have such a global > view of their business that they can build such a roadmap. And how long > would it take for the view to be out of date and the roadmap need > re-doing with the associated knock ons? > > > Anne > > > > Dan. > > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Yahoo! Groups gets a make over. See the new email design. http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
