Enterprise IT Architect

pAs an Enterprise IT Architect, you play a crucial role in defining, supporting and governing strategic transformations. /ppDuring the shaping of the target operating model with management (C-level), you bring in those elements of the IT Strategy which might influence the outcome of this exercise. You take the lead in determining the relevant technology investment horizon based on the differentiation nature of the business and IT functions to be delivered. /ph3We change it /h3pAfter developing the strategic framework and the target operating model, you will define the To Be target of the business and application functions, together with the Enterprise Business Architect. Subsequently, you will define the projects and their relationships required to deliver the To Be architecture. /ppYou don't do this alone, but collaborate closely with the other members of your core team, consisting of the following roles: /pulliTransformation manager / Roadmap coordinator /liliBusiness representative /liliEnterprise Business architect /liliChange manager /liliRepresentative of the IT Organization /li /ulpIn this way we guarantee a balanced roadmap which takes sufficient account of the various important aspects such as business priority, change readiness of the organization, architectural optimization, risks, resource availability, dependencies, costs, revenues, timing... In the program team there is NO hierarchy: everyone looks at the proposals based on their expertise and the goal is to have the team members challenge each other to come up with the best solution for the organization. /ph3We govern it /h3pOnce the roadmap is ready and approved, you will remain responsible for its implementation. Together with the core team you will start projects that will realize parts of the roadmap architecture. In concrete terms, this is done by handing over to the mirror role at project level: the IT solution architects are your mirror role at project level. /ppNext, you will continue to follow up on the projects (from an Enterprise IT Architecture perspective) by organizing communities and setting up reviews. /ppDuring the implementation phase, significant adjustments may still need to be made to the architecture: e.g. based on feedback from the projects, changing market conditions and/or the annual review of the roadmap. /ppFinally, during the process, you will monitor the dependencies of your roadmap with the other strategic roadmaps of the organization. /p h3Why choose Myreas? /h3pbOur origin: the EA context of the Colruyt Group /b /ppThe Colruyt Group is the only "Architecture-driven" company in Belgium and maybe even in Europe. Decisions are not made by those who hit the table the hardest, they are made by an architectural process and architectural boards The management takes all decisions based on an architectural foundation and rationale. /ppC-Level is being given EA training to learn “Architecturese” (the language of EA’s) /ppC-level must explain and defend the architectural recommendations to the Colruyt Group Architecture board (CEO, COO, CIO, Head of Bus. Arch, Head of IT Arch) in order to demonstrate their full commitment /ppbOur extensive toolset /b /ppOur methodology for applying Enterprise Architecture is firmly rooted in TOGAF and ArchiMate, which we’ve been putting to work relentlessly keeping what worked well, tossing what didn’t and adding what was missing. /ppThe result is an extensive toolset fit for the purpose of applying Enterprise Architecture. This toolset encompasses Strategy definition, Enterprise Business, Application and Technology Architecture, Transformation Portfolio Management and specific deepdives in Architectural Notation, Tooling and governance. /ppAs said, we took a lot of inspiration from TOGAF and ArchiMate, but we enriched our methodology with other tools and techniques such as the Target Operating Model framework (from Ross Weill) or Pace Layering (from Gartner) to name just two. /ppbOur collaboration between business and IT /b /ppThe Enterprise Architects are always staffed in "duo" (an Enterprise IT Architect and an Enterprise Business Architect). Together they collect the high-level architectural requirements, translate these into different options and make recommendations to the management. Enterprise Architects are staffed in duo because each discipline has its own focus (Business or IT) and by challenging each other. they arrive at the best proposal. In addition, there are EA governance structures at Corporate Level, Capability Level and Program Level. /ph3The mindset of a start-up /h3pbA start-up /b /ppMyreas is a small niche company, with a flat structure and a minimum of company rules. Myreas staff are shaping their own company and all colleagues are invited to help: “We will define our future together”. /ppDiscover our most important soft skills /ppbSingle focus on EA /b /ppMost EA companies start with EA, but due to customer demand and the fact that TOP EAs are so hard to find