Salesforce Architecture framework, Martin Kona

Information about Salesforce Architecture framework, Martin Kona

Published on August 28, 2019

Author: CzechDreamin

Source: slideshare.net

Content

1. Salesforce Architecture framework by Martin Kona

2. #CD19 ● 12x Salesforce certified App & System Architect ● 2x CPQ certified (Apttus & Bit2Win) ● TOGAF 9.2 Foundation and Certified levels ● Karaoke singer

3. #CD19 ● Salesforce is usually implemented without any vision, roadmap or governance ● Customer is left with vague documentation/decision audit ● Green field projects are being delivered in lightning speed, but the technical debt is raising exponentially. It’s impossible to make simple changes in the future Why I think this is important

4. #CD19 ● The Open Group Architecture Framework ● It is complex and generic framework Enterprise architecture methodology that offers a high-level framework for enterprise software development ● It is not a silver bullet ● It is open, google it! ● I can’t even introduce it in 50 minutes! And I’m not trained to do so  ● In our case, we will focus on Architecture Development Methodology #ADM Have you heard about TOGAF?

5. #CD19 ● The result of continuous contributions from a large number of architecture practitioners ● It’s a project lifecycle ● Is iterative over the whole process, between phases and within phases What is ADM?

6. #CD19 ● Identify business scenarios ● Identify stakeholders and business goals ● Define architectural principles Example: 80/20 rule, control technical diversity, data is an asset ● Establish architectural repository ● Generate first-cut high level description of baseline and target environments The Architecture Vision is essentially the architect's "elevator pitch“. A: Architecture vision phase

7. #CD19 ● Iterate within three phases B, C and D ● Every phase should define following: 1. Describe Baseline Architecture 2. Develop Target Architecture 3. Analyze the gaps 4. Select relevant architecture viewpoints ● Repeating the cycle makes perfectly sense with Salesforce project, since OOTB or managed packages might drive or change the business processes. Architecture Development Iteration

8. #CD19 Gap analysis

9. #CD19 ● View is developed from the architecture viewpoint, which addresses stakeholder’s concerns Views and Viewpoints

10. #CD19 ● Define the actors using Salesforce and ideal license choices ● Refine business scenarios into business requirements ● Which business processes will be implemented or influenced by Salesforce? ● What is the org strategy? B: Business Architecture phase

11. #CD19 ● What is our data architecture? ● What is our sharing architecture? ● What Lightning Apps are we implementing? ● What is our application roadmap? Are we planning to purchase managed package or implement it by ourselves? C: Information Systems Architectures phase

12. #CD19 ● Design integration architecture (who is master of what, data flow, API) ● Define coding standards and architecture/patterns for custom development governed by code reviews ● Design environments strategy ● Identify technical risks and how to mitigate them D: Technology Architecture phase

13. #CD19 ● Iterate within two phases E and F ● Outcome of the iteration is to gain buy-in to a portfolio of solution opportunities ● Another outcome is Migration plan from baseline to target Transition Planning iteration

14. #CD19 ● Agile or Waterfall? => Wagile ● Schedule and estimate implementation roadmap ● Identify resource risks (do they know Salesforce? ) ● What is our release strategy? E: Opportunities and Solutions phase

15. #CD19 ● Identify project dependencies (mainly integration services) ● What is our deployment strategy? Change set or IDE+MetadataAPI or Copado/Gearset? ● What is our test strategy? Apex positive & negative tests policy, manual/automated (Provar, Selenium)? ● What is our DATA conversion plan? F: Migration planning phase

16. #CD19 ● Governance is defined as the processes that ensure the effective and efficient use of IT in enabling an organization to achieve its goals. ● Iterate within two phases G and H ● Initial iteration’s goal is to mobilize governance and change management process ● Subsequent iterations carry out the periodic reviews of changes to resolve issues and ensure compliance Architecture Governance iteration

17. #CD19 ● Which teams are involved on the project and their impact? ● Establish effective Center of Excellence ● Establish Architecture Review Board to adhere to our architectural design and standards ● Define process to make decisions if something should be configuration or custom development ● What is our system administration model? G: Implementation Governance phase

18. #CD19 ● How to manage changes? ● What should be categorized as hotfix? ● How to handle hotfix? Exception deployment rules? H: Architecture Change Management phase

19. #CD19 ● Do your own research on IT frameworks ● Adapt them to your own project situation ● Governance on release process and deployments is always underestimated ● Even if no one from project is interested in architecture framework, use the phases as a personal checklist, document it and make it transparent. Others might follow. Key takeaways

20. #CD19 Q&A

21. Thank you!

#cd19 presentations

Czechitas, Ondřej Čejka
28. 08. 2019
0 views

Czechitas, Ondřej Čejka

Related presentations


Other presentations created by CzechDreamin

Czechitas, Ondřej Čejka
28. 08. 2019
0 views

Czechitas, Ondřej Čejka