Organizations often have many IT projects each year involving lots of people creating, using, changing and replacing IT artefacts.
To manage day to day transformation, enterprises adopt Project Management best practices and tools to manage goals and resources used to produce such IT artifacts. They also adopt ITIL best practices and CMDB systems to handle changes in such artifacts in production environments.
However, at the level of IT landscape there is a lack of a global and aggregated view of the impact of all projects, not only to ensure their assumptions are correct and to identify project dependencies, but also to be able to answer questions such as:
- I need to do the design and planning a project to start in 3 months’ time. Based on the on-going project´s pipeline, what will be the IT landscape look like in 3 months’ time?
- What will be the impact of a delay or changes in one project on the remaining projects?
- What will be the distribution of effort, cost and risk along the year associated with different project pipeline scheduling?
With EAMS, organizations can address these questions, both from the perspective of IT architects, where IT blueprints change according to the completion of each project, as well as for IT managers through their dashboards.
In EAMS, all architectural views have a time slider associated, marked with the moments in time, in which there were projects that produced a change in that architectural view. When the handle moves along the slider, and crosses a mark, the name of the project that led to change appears on the left and the content of the architectural view changes.
In the figure below one shows the evolution of a layered blueprint according to handle position in time. In the bottom we zoom out the time slider showing the time handle (circle) and corresponding project (ellipse) that changed the IT landscape from AS-IS situation to the TO-BE-Stage-01 situation.
EAMS also computes analytical information regarding the displayed changes. In the figure bellow, we present the corresponding evolution of the maintenance cost.
EAMS allows the analysis of the impact of alternate project scenarios, at the different levels: business impact, project dependencies, cost, risk and effort over time.
But the IT transformation also implies the ability to analyze different scenarios. EAMS allows the creation of Architectural Scenarios both by the addition of new architectural elements as by the amendment to the existing elements. EAMS supports the simultaneous loading of several scenarios allowing the analysis of dependencies between them.