The Organic EA method
The Organic EA methodology is developed based on the model in the last section. It follow road map which :1. The planning,
2. The Initial EA for holistic.
3. The Agile EA to enable agility and simplicity.
4. The Operational EA via segment architecture for modernization.
It suggest the initial EA for the purpose of holistic and operate EA via Operational EA to adapt the constant changing Enterprise.
After the initial EA, the major effort of EA is shift to Segment Architecture which is a sub-set of EA to address the dynamic change of business. For EA to be practical, the notional enterprise architecture is only elaborated in the area of business rather than design the entire enterprise in a big-bang approach base on the architects ideology. Segment Architecture is incremental and continuous. On contrary to the holistic and notional target enterprise architecture , segment architecture is executable which support gap analysis, transition plan and modernization.
Planning phase :
1. Buy-in from senior management
2. Obtain EA management resources
3. Establish Management Structure
4. Establish EA infrastructure to leverage on automation.
5. Initiate EA management processes
Initial EA
1. Prepare the EA map to see the big picture and know the enterprise.
2. Facilitate EA collaboration.
3. Apply architecture principle to analyze Business Architecture.
4. Adopt basic EA standards, building blocks and common resources.
5. High level target solution architecture
6. Continue to evolve governance and compliance processes.
7. Deliver EA value to initiate EA culture.
EA operation is incremental and continuous
1. Continue to maintain EA standards
2. Annual IT strategic planning close performance gap.
3. Identify segment architecture to ellaborate enterprise target architecture and consolidate common resources.
4. Capital investment review
5. Initiate projects.
6. Project compliance review
7. Conduct EA self assessment
8. Continue to Improve governance and compliance processes
9. Make transition from stovepipe culture to EA culture. .
Notional Schedule
^ TOP
The planning phase
he HACEA planning is the effort to prepare for HACEA initiative.Planning for
4.5 EA management structure
Figure 4 illustrates a notional program organization to manage, control, and monitor EA activity and progress. The organization shows the desired functional roles, interrelationships, and lines of communication. The organization structure should facilitate and advance the performance of EA roles and responsibilities. The roles of the EAESC, Technical Review Committee (TRC), and the EA Program Management Office are unique to the introduction of the EA process. Other roles, such as Quality Assurance (QA), Configuration Management (CM), Risk Management (RM), Security, and Evaluation are customary IT support roles. These roles are expanded to explicitly include EA-related responsibilities.
EA roles should be evaluated based on the size of the organization, the complexity of the business and architecture, and other factors to effectively determine the correlation of roles assigned to personnel. In a large organization with complex business processes, an individual may be responsible for one specific role. In smaller Agencies or organizations, an individual may be assigned several roles and responsibilities.
Figure 1. Notional EA Organization
Read More → ^ TOP
See the true whole and preserve institutional knowledge
Enterprise Architecture is not only about see the big picture but also preserve the institutional knowledge to know the detail.1.0 The sensation of Jigsaw puzzle
The playerzblog says:
A puzzle is an enigma which tests ingenuity and creativity of the solver. A simple puzzle requiers the player to place together the objects in the game, the puzzle pieces, in a specific way, a logical manner, to come up to the whole image, the desired shape, picture or solution. Puzzles are usually a form on fun, of entertainment, bu they can represent also serious logistical, statistical or math problems.
The Enterprise Topology is a complicate jigsaw puzzle without the picture on the cover and without the pieces in the box. It is an effort to see the unseen by rendering the picture-in-mind to an explicit picture.
1.1 A puzzle without the pieces
Unlike to a jigsaw puzzle which comes with all the pieces in the box, the Enterprise knowledge reside deeply in each individual. Some knowledge can be describe by words, some knowledge can only be describe by picture and some knowledge are subconscious. Knowledge transfer from each individual to Enterprise Topology is the initial challenge.
1.2 A puzzle without a picture on the cover
Enterprise is logical and invisible, each individual only touch one part of the enterprise. The only way to see the big picture is put the pieces together via reconciliation instead of insist on their righteousness.
^ TOP
Summary of What is HACEA?
The following figure summrize the What HACEA is by:HACEA definition
HACEA example
What is not EA?
^ TOP
The strategy to overcome the challenge of buy-in from stakeholders
Buy-in is not only by the senior management. It must be every one.After hardwork on designing the Enteprise Architecture form an ivory tower, the architects find out buy-in from stakeholder is not granteed. As a result, Most of EA artifact have become a shelfware for show and tell with limited practical use. Most of EA approach suggest the buy-in form senior management, the HACEA suggest that EA is a total participation and buy-in is not only from the senior managment but also from every one for EA to become a culture of the information age.
HACEA overcome the challenge of buy-in from the stakeholders based on the following approach.
1. Leverage on communication professionals.
2. Explicit with architecture drawings
3. Building consensus with political processes.
4. Provide value continuously
The following articles describe each strategy. For online reading convenience, each article is only partially displayed. Please click the read_more for the full article.
^ TOP