tag:blogger.com,1999:blog-36221074.post246692093099630822..comments2020-01-25T02:09:58.700-08:00Comments on Enterprise Technology: No Excuse for not having Enterprise ArchitectureBalahttp://www.blogger.com/profile/11247511314684547070noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-36221074.post-56402283169018558562009-06-24T10:58:41.879-07:002009-06-24T10:58:41.879-07:00Project management offices (typically called PO fo...Project management offices (typically called PO for Project Office) do not have the scope - they run projects, planning tasks and tracking activity for discrete projects, or, if run at the functional organization level, like IT, for coordinating IT. <br /><br />Projects are like GL chart of account updates, or procure-to-pay. These fit in the realm of the project office, as well as the enterprise TECHNOLOGY architect. They do NOT fall directly under EA or Program office responsibility. <br /><br />The real analogous position to EA is the PROGRAM management office (typically called the PMO). Programs are things like finance, or supply chain, or field operations. In the defense industry, a program is a fighter jet, or a tank development and production. They are made up of hundreds or thousands of projects, and dozens of functional organizations, just like the scope of the ENTERPRISE (not technology) architect. <br /><br />The PROGRAM office has responsibility to plan resources (budget and staff) across functional boundaries, and in line with the overall corporate strategy, just as the enterprise architect has responsibility to coordinate business initiative content over the entire enterprise, in every functional organization, just as organizational design has responsibility for coordinating the cross-functional processes that make the business operate.kirkhttps://www.blogger.com/profile/03191816419847994968noreply@blogger.com