EA Road map Thoughts

I do now have a fair understanding of how a current state architecture and a future state architecture should consist of.  Next, we need to identify gaps. This is achieved by defining the linkage between current and future EA components. This way, any capability that the enterprise is lacking in order to perform at the desired level will be clearly shown. A road map should be developed to close these gaps and move to the desired future state. Let’s see how Mr. John Doe of Blog Two has handled this matter.

 “I had to learn from my previous mistake and build an EA road map that appeals to its audience. In other words, a road map that they can relate to, leverage and adopt” John Doe told me.  John has invested enough time in understanding his key stakeholders and what matters to them most. He used this understanding to define what should the road map address (scope), its depth and its focus. It is important to note that the audience of the EA Road map is any stakeholder who is involved in administering and/or implementing the EA program.

“This road map is supposed to guide investment decisions” said John Doe, “therefore, I was guided by three things, the strategy, the future state and disruptive technologies out there”  To develop a road map one should have a very broad look that goes beyond the enterprise and reach to the larger ecosystem. Big Data, Digital business and Internet of things (IOT) has started to affect a lot of industries. For example, you won’t be able to compete in the Healthcare industry soon without leveraging IOT and Big Data.

“To ensure the road map remains useful and valuable” said John Doe “I have defined business outcome metrics to assess projects and initiatives proposed in the road map”. This has helped John Doe and the enterprise schedule reviews and check on the progress of the road map.

In addition to what I have learnt from John, the road map also need to define the activities & time frames for implementing the proposed changes in business and technology in light of dependencies, priorities and constraints.

That’s all for now!