EA Activities

 Step by Step Instruction to Create EA

1. Create Guidelines
• Risk management guidelines. Can use the below tools to manage risks - https://www.lucidchart.com/pages/templates/generic-framework-for-risk-management
• Risk register template - https://www.lucidchart.com/pages/templates/risk-register
• Risk breakdown - https://www.lucidchart.com/pages/templates/risk-breakdown-structure
• Risk impact scale - https://www.lucidchart.com/pages/templates/risk-impact-scale
• Develop Architectural Principles: 4 areas of principles 
• 
• Create Arch Repo- Organise the artefacts created in each phase to the common repo
• Define the scope of the enterprise architecture. This should include the boundaries of the organization, the systems and processes that will be covered by the architecture, and any relevant constraints or limitations
• Do the maturity analysis of the organisation 
2. Meeting with executives to find out the business goals, vision, roadmap and KPI
3. Meeting with Business teams and architects to get a detailed view of each business department's business goals & roadmaps to achieve the executive KPI and discuss the current business capabilities.
4. Meeting with the technology/application team to find the current technology landscape and technology DevOps capabilities in the company.
5. Create the current state of the organisation
• Create an organisational view. Refer - https://pubs.opengroup.org/togaf-standard/business-architecture/organization-mapping.html
• A stateholder map can be created in the form of https://www.lucidchart.com/pages/templates/stakeholder-map-example
• Challenges in managing stakeholders - https://www.lucidchart.com/blog/how-to-manage-common-stakeholder-issues-and-challenges
• Create RACI Chart - https://www.lucidchart.com/pages/templates/raci-chart
• Create a business capability view. Refer - https://www.lucidchart.com/blog/a-quick-guide-to-business-capability-maps . Refer - https://online.visual-paradigm.com/knowledge/business-design/what-is-enterprise-archtiecture-diagram/ or using https://www.lucidchart.com/pages/templates/functional-decomposition-example. 
• 
  
  
• Can contains business process flow diagrams - https://www.lucidchart.com/pages/templates/current-vs-future-state-flowchart
• Create Application Architecture view
• Create application architecture view. e.g. - https://www.lucidchart.com/pages/templates/application-architecture-example
• Create integration architecture view e.g. https://www.lucidchart.com/pages/templates/integration-architecture-example
• Create deployment diagram - https://www.lucidchart.com/pages/templates/uml-deployment-diagram-example
• Create DevOps Arch diagram - https://www.lucidchart.com/pages/templates/dev-ops-toolchain-and-process-flow-example
• https://www.lucidchart.com/pages/templates/ci-cd-toolchain-example
• Create Data Architecture that contains the following
• Dataflow diagram - https://www.lucidchart.com/pages/templates/data-flow-diagram-level-1
• https://www.lucidchart.com/pages/templates/data-flow-diagram-level-2
• https://www.lucidchart.com/pages/templates/data-flow-diagram-physical-example
• K12 Data model - https://www.lucidchart.com/pages/templates/education-data-architecture-eda-k-12-data-model
• Create dependency and risk management view - https://www.lucidchart.com/pages/templates/dependency-graph
• Create the Technology Architecture diagrams that contain the following
• Hosting - https://www.lucidchart.com/pages/templates/web-application-hosting-diagram-example
6. Create the desired state of the organisation. Follow to create the same list of diagrams from current state step 5 above.
• Do the tech stack evaluation if the desired state require new technology stacks. Refer https://www.lucidchart.com/blog/how-to-choose-the-right-technology-stack-for-software-architecture
• Refer https://www.tiobe.com/tiobe-index/ for new trends
7. Do the Gap Analysis using the following 
• SWOT(Strngth, Weekness,Opportunity, Threat) - https://www.lucidchart.com/pages/templates/swot-analysis-example
• PESTLE(Political, Economical, Sociological, Technological,Legal, Environmental) - identify threats and opportunities by examining  the factors
• 
  
  
• Identify the cause and effect of problems in the current/future state via using fishbone(Ishikawa) diagram - https://www.lucidchart.com/pages/templates/cause-and-effect-diagram-example
• Can use mckinsesy's 7S framework to determine whether a company is meeting expectations, and it actualizes the shared values of an organization https://www.lucidchart.com/blog/mckinsey-7s-model
8. Create Operational & Development Value Stream as part of SAFe
• Create Operational Value stream. Map down all values to the target customer and create seperate operational value stream for each values. Refer https://www.scaledagileframework.com/identify-value-streams-and-arts/ for the steps to create the value stream
• Create Development value stream
• Lean Budgeting(Funding value streams not projects) for the Development value stream. Refer - https://www.scaledagileframework.com/lean-budgets/
• 
• Create value stream KPI - https://www.scaledagileframework.com/value-stream-kpis-2/
• Identify areas of inefficiency and waste in your value stream, and use the SAFe framework to implement improvements and streamline the processes
• Establish agile governance processes to ensure that your organization is able to deliver value efficiently and effectively, using the SAFe framework as a guide
9. Do the prioritization, create optimal sequence 
10. Create the EA Roadmap - Refer https://www.scaledagileframework.com/roadmap/
• Should mostly contains the following documents as well
• Enterprise architecture plan: This document outlines the overall strategy and direction for the enterprise architecture, including the goals and objectives, scope, timeline, and stakeholders.
• Architecture roadmap: This document provides a high-level overview of the planned changes and improvements to the enterprise architecture over time
• Reference architecture: This document defines the common elements and standards that will be used across the enterprise architecture, including the technology stack, data models, and design patterns
• Capability map: This document provides a visual representation of the organization's capabilities, showing how they relate to each other and to the business goals
• Solution architecture: This document provides a detailed description of a specific solution or system within the enterprise architecture, including its components, interfaces, and dependencies
• Refer - https://pragmaticarchitect.wordpress.com/2013/07/01/how-to-build-a-roadmap-prioritize-part-i/
• https://pragmaticarchitect.wordpress.com/2013/07/29/how-to-build-a-roadmap-sequence/
• https://conexiam.com/togaf-adm-phase-e-build-the-architecture-roadmap/
11. Monitor and maintain the enterprise architecture. This involves regularly reviewing and updating the architecture to ensure that it remains relevant and effective over time.  Get feed back from the solution team and if there are any gaps put it back in the SAFe back logs

During the realisation, use SAFe to do the PI(Program Iteration) Planning - https://www.lucidchart.com/pages/templates/sa-fe-pi-planning
Risk management in SAFe is done via the ROAM(Resolve, Own, Accept, and Mitigate) board

Reference: https://gitlab.com/redhatdemocentral/portfolio-architecture-examples