<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><b class=""><span style="font-size: 14px;" class="">Don’t Miss Out on Two Exceptional Architecture-centric workshop offerings by Mark Richards coming to Austin!</span></b></div><div class=""><br class=""></div><div class="">Training Offering #1: Software Architecture Workshop - Austin</div><div class="">Dates: March 20-22, 2017</div><div class="">Location: Austin Marriott South</div><div class="">URL: <a href="https://www.nofluffjuststuff.com/n/training/2017/03/20/software_architecture_training" class="">https://www.nofluffjuststuff.com/n/training/2017/03/20/software_architecture_training</a></div><div class="">Instructor: Mark Richards</div><div class=""><br class=""></div><div class="">Early Bird Rate: $2,750 thru 2/17, after $3,000</div><div class="">JUG Discount: Use code: usergroup100 for a $100 off</div><div class="">***********************************************************************************************************</div><div class=""><div class="">Training Offering #2: Enterprise Architecture Workshop - Austin</div><div class="">Dates: March 23-24, 2017</div><div class="">Location: Austin Marriott South</div><div class="">URL: <a href="https://www.nofluffjuststuff.com/n/training/2017/03/23/enterprise_architecture_training" class="">https://www.nofluffjuststuff.com/n/training/2017/03/23/enterprise_architecture_training</a></div><div class="">Instructor: Mark Richards</div><div class=""><br class=""></div><div class="">Early Bird Rate: $1,950 thru 2/17, after $2,150</div><div class="">JUG Discount: Use code: usergroup100 for a $100 off</div></div><div class=""><br class=""></div><div class=""><h2 style="box-sizing: border-box; line-height: 40px; color: rgb(32, 71, 137); margin: 0px 0px 20px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" class=""><span style="font-size: 14px; font-weight: normal;" class="">Software Architecture Workshop Course Outline</span></font></h2><p style="box-sizing: border-box; margin: 0px 0px 10px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Training will be held 9AM - 5PM each day.</font></p><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">DAY 1</font></h3><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Introduction</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Agenda and course logistics</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Attendee introductions</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Expectations of a software architect</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Architectural Thinking</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Managing architecture knowledge</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture vs. design</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Balancing hands-on coding and architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Identifying architecture characteristics</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Analyzing architecture tradeoffs</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Working with architecture teams</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture katas (exercises)</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Architecture Patterns</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Microservices architecture pattern</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Service-oriented architecture pattern</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Service-based architecture pattern</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">DAY 2</font></h3><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Architecture Patterns (cont.)</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Layered architecture pattern</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Event-driven architecture pattern</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Microkernel architecture pattern</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Pipeline architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Space-based architecture pattern</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Component-based thinking</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Component responsibility models</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Identifying components and services</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Component granularity</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Component coupling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Compoent cohesion</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture katas (exercises)</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Documenting and Presenting Architecture</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Diagramming software architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Documenting software architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Presenting software architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture Katas (exercises)</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">DAY 3</font></h3><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Reactive Architecture</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Creating self-healing systems</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Responsive patterns</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Resilient patterns</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Elastic patterns</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture katas (exercises)</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Architecture Techniques and Soft Skills</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture decisions</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture refactoring</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Making teams effective</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Negotiation skills (exercises)</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Leadership skills</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Summary and Wrap-up</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">The future of software architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture certification</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Developing your career path</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Next steps</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Course Logistics</font></h3><p style="box-sizing: border-box; margin: 0px 0px 10px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class=""><span style="box-sizing: border-box; font-weight: 700;" class="">Prerequisites:</span> developers wanting to take the next step to architect or new architects wanting to validate and hone their architecture skills <br style="box-sizing: border-box;" class=""><span style="box-sizing: border-box; font-weight: 700;" class="">Laptops:</span> as this is a hands-on course, attendees will need a laptop with some drawing tool such as PowerPoint, Keynote, Visio, OmniGraffle, etc.</font></p><div class=""><font face="Tahoma" size="1" class=""><br class=""></font></div></div><div class=""><font face="Tahoma" size="1" class=""><br class=""></font></div><div class=""><h2 style="box-sizing: border-box; line-height: 40px; color: rgb(32, 71, 137); margin: 0px 0px 20px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" class=""><span style="font-size: 14px; font-weight: normal;" class="">Enterprise Architecture Workshop Course Outline</span></font></h2><p style="box-sizing: border-box; margin: 0px 0px 10px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Training will be held 9AM - 5PM each day.</font></p><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Introduction</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Enterprise architecture context</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Why do you need EA?</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">EA process overview</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Value-driven enterprise architecture</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Enterprise initiatives</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Structure and segmentation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Enterprise decisions</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Expectations of an enterprise architect</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Approaches</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Model-based approach</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Initiative-based approach</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Transforming EA: Pragmatic approaches</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Issues with traditional approaches</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Strategies and Standards</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Selecting the right strategy</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Governing enterprise standards</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Prescriptive strategy</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Classic alternatives strategy</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Distributed strategy</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Durable interface strategy</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Strategy and governance</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Kata: Selecting the right strategy</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Enterprise Modeling</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Purpose and goals</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Domain partitioning</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Representational consistency</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Work process modeling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">System modeling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Data information modeling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Technology and infrastructure modeling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Automation modeling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Model synergy and synchronization</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Lean approaches to modeling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">ArchiMate standard overview</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Modeling examples and scenarios</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Kata: Leveraging models within the enterprise</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Enterprise Frameworks</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Purpose and goals</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">History and evolution of frameworks</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Advantages of using frameworks</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Disadvantages of frameworks</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Framework capabilities</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Framework types</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Zachman Framework overview</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">TOGAF overview</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">FEA overview</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Framework comparison</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Leveraging frameworks</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Transformation Techniques</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Enterprise cloud strategies</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Enterprise evolution</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Strategy and standards evaluation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Leveraging a data bus for transformation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Leveraging SOA</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Using an API for Transformation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Using an integration hub for transformation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Building enterprise services</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Protocol decoupling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Hub federation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Contract decoupling</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">System migration refactoring techniques</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">System adaptation refactoring techniques</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Platform transformation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Application consolidation</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture migration</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Roadmaps</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Transformation types</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Context-based roadmaps</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Model-based roadmaps</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Roadmap iteration models</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Roadmap project profile models</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Roadmap prioritization models</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Creating an effective EA roadmap</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Roadmap model synchronization</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Communication</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Communication pitfalls and warning signs</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Core EA communication techniques</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Communicating models</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Communicating decisions</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Creating a Modern EA Practice</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Effective team structures</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Breaking down barriers</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Strategy and team structure</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">EA team ownership</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Creating an agile EA team</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Techniques for effective architecture review boards</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Skills required for an enterprise architect</font></li><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">EA Career path</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Summary and Wrap-up</font></h3><ul style="box-sizing: border-box; margin: 0px 0px 30px 30px; padding: 0px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><li style="box-sizing: border-box;" class=""><font face="Tahoma" size="1" class="">Architecture resources</font></li></ul><h3 style="box-sizing: border-box; font-weight: normal; line-height: 1.1; color: rgb(51, 51, 51); margin-top: 0px; margin-bottom: 5px; orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class="">Course Logistics</font></h3><p style="box-sizing: border-box; margin: 0px 0px 10px; color: rgb(51, 51, 51); orphans: 2; widows: 2; background-color: rgb(241, 241, 241);" class=""><font face="Tahoma" size="1" class=""><span style="box-sizing: border-box; font-weight: 700;" class="">Prerequisites:</span> architects looking to become enterprise architects or enterprise architects looking for more ways to become effective</font></p></div><div class=""><font face="Tahoma" size="1" class=""><br class=""></font></div></body></html>