Section 1
EA is the Enterprise Architecture, covers the basis elements to build program together. EA is “a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a holistic approach at all times, for the successful development and execution of strategy. EA applies architecture principles and practices to guide organisations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilise the various aspects of an enterprise to identify, motivate, and achieve these changes.” (2013). All the departments including technology, finance, HR, maintenance and operation cannot be separated from the whole education enterprise. It’s a whole, cannot be singled out. EEA aims to bridge the gap between management decision stakeholders and operational team.
My current organization, WAB (Western Academy of Beijing) has a long term 5 year ecosystem plan which include the school education plan and the technology plan together. I interviewed the elementary school principal, who strongly support the education plan should involve technology plan together, instead of separating them out. It’s because technology is everywhere in education, including academics (they have powerschool, tiger video, 1:1 iPad and 1:1 iMac, blogs, etc.), transportation, lunch, finance, HR, etc. So they cannot separate technology from the whole education plan. The whole education plan at WAB has 10 different fields that support all facets in school such as attendance, technology, bus, finance, teaching and learning, etc. EA helps us to see all the fields together, instead of separating them into small pieces. Therefore, developing the enterprise architecture is not a solitary activity and the enterprise architects need to recognize the interoperability between their frameworks and the rest of the business.
It’s critical to involve leaders from non-technical parts of an organization with technology future planning. Because the CEAF claimed “collaboration with business architects, analysts and other business SMEs is extremely important to planning the future state BA”. (CEAF, 2013)
Take WAB as an example. The school currently is working on the future state plan (5 year long term plan) which includes technology future planning, but beyond it. When I interviewed the elementary school principal and the head of IT, they confirmed it’s important that non-technical leaders including the senior strategic team including the director of the operation who is in charge of all the hardware budget and the deputy head of the school, as well as the three principals from elementary, middle and high school work together to consider the technology future planning.
The reason that we must involve BA, teachers, other department managers and all stakeholders is because BA future planning requires an incremental approach such as each line of business and each bunnies capability) and a series of complex steps such as “process categorisation and characteration.” “maturity assessment and operating model of current process”, “opportunities and solutions.” Involving all the BA so that alternate options will be analysed and join the future planning. (CEAF, 2013).
References:
Federation of EA Professional Organizations, Common Perspectives on Enterprise Architecture (http://feapo.org/wp-content/uploads/2013/11/Common-Perspectives-on-Enterprise-Architecture-v15.pdf), Architecture and Governance Magazine, Issue 9-4, November 2013.
My current organization, WAB (Western Academy of Beijing) has a long term 5 year ecosystem plan which include the school education plan and the technology plan together. I interviewed the elementary school principal, who strongly support the education plan should involve technology plan together, instead of separating them out. It’s because technology is everywhere in education, including academics (they have powerschool, tiger video, 1:1 iPad and 1:1 iMac, blogs, etc.), transportation, lunch, finance, HR, etc. So they cannot separate technology from the whole education plan. The whole education plan at WAB has 10 different fields that support all facets in school such as attendance, technology, bus, finance, teaching and learning, etc. EA helps us to see all the fields together, instead of separating them into small pieces. Therefore, developing the enterprise architecture is not a solitary activity and the enterprise architects need to recognize the interoperability between their frameworks and the rest of the business.
It’s critical to involve leaders from non-technical parts of an organization with technology future planning. Because the CEAF claimed “collaboration with business architects, analysts and other business SMEs is extremely important to planning the future state BA”. (CEAF, 2013)
Take WAB as an example. The school currently is working on the future state plan (5 year long term plan) which includes technology future planning, but beyond it. When I interviewed the elementary school principal and the head of IT, they confirmed it’s important that non-technical leaders including the senior strategic team including the director of the operation who is in charge of all the hardware budget and the deputy head of the school, as well as the three principals from elementary, middle and high school work together to consider the technology future planning.
The reason that we must involve BA, teachers, other department managers and all stakeholders is because BA future planning requires an incremental approach such as each line of business and each bunnies capability) and a series of complex steps such as “process categorisation and characteration.” “maturity assessment and operating model of current process”, “opportunities and solutions.” Involving all the BA so that alternate options will be analysed and join the future planning. (CEAF, 2013).
References:
Federation of EA Professional Organizations, Common Perspectives on Enterprise Architecture (http://feapo.org/wp-content/uploads/2013/11/Common-Perspectives-on-Enterprise-Architecture-v15.pdf), Architecture and Governance Magazine, Issue 9-4, November 2013.
Home
About
Contact
About
Contact