This week readings is one of the interesting topics for me “Gap Analysis”. In the previous blogs I wrote about the current and the future state levels in the Enterprise Architecture. The whole important part of setting up the right current and future state documentation and expectation is to perform gap analysis anytime and close the gap as pointed out by the garner article.
I believe role of Enterprise Architects is paramount in this aspect where they have to perform all the key analysis and come up with recommendations that can help the organization close the gap between the “as-is” and “to-be” state in simple terms. From the reading they four key aspects of gap analysis I tried to list here as follows:
- Identify and classify gaps
- Analyze gaps
- Develop recommendations
- Prioritize recommendations
First starting step for the Enterprise architects would be to describe all the major components involved with the help of various artifacts. In the next stage they analyze and come with migration planning and handling the change requirements based on the requirements vision of the organization. The final stage is to deliver the planning documents and reduce the actual gap and improve the stability of EA.
The above figure illustrates identifying key factors for change and the action plan list creation. The chapters in the book also discussed about the importance of recommendations from the Enterprise Architects as major criteria for the business planning and strategy setup. Enterprise architects in my opinion play a critical role in performing the gap analysis and designing recommendations.
Leave a Reply