Architects generally concern themselves with change: a system that’s never going to change in functionality, scope, scale, or environment may not actually need an architect. Many organizations want to change. For instance, facing pressure from digital disruptors, large incumbent companies are looking to become more agile, more customer-centric, and more “digital.”
Do architects have a role in such transformations? All signs point to yes: large organizations behave not unlike large technical systems, and organizational changes have to go hand in hand with technical changes, anyhow.
Join Gregor Hohpe to find out how architects can use what they know about technical systems to help refactor organizations.
Gregor Hohpe is a technical director in Google Cloud’s office of the CTO, where he maximizes the benefit customers derive from a cloud-based IT model by combining organizational, software delivery, and IT infrastructure transformation. Riding the “architect elevator” from the engine room to the penthouse, he connects corporate strategy with technical implementation by making complex topics engaging and approachable without compromising technical accuracy. Previously, Gregor was chief architect at Allianz, one of world’s largest insurance companies, where he established accelerated innovation and complexity and cost reduction as architecture goals, oversaw a global data center consolidation, and deployed the first on-premises cloud and software delivery platform. Gregor is a coauthor of the seminal book Enterprise Integration Patterns, widely cited as the reference vocabulary for asynchronous messaging solutions. His book 37 Things One Architect Knows about IT Transformation tells stories from the trenches of IT transformation, while his articles have been featured in Best Software Writing by Joel Spolsky and 97 Things Every Software Architect Should Know. He’s an active member of the IEEE Software advisory board.
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com