Matt Walburn's guest appearances

Matt Walburn

Pivotal Podcasts

Software Defined Interviews

Tanzu Talk

Coté Show Variety Podcast

Josh Long

John Mitchell

Rachel Stephens

Rita Manachi

Cora Iberkleid

Paula Kennedy

Len Hardy

Gary P. White

Ben Laplanche

Hannah Foxwell

Joanna Beltowska

Kenny Bastani

Sina Sojoodi

Bryon Kroger

Usha Ramachandran

OwlTail

What’s the “business” side of enterprise architecture? And how does EA’ing start mapping to DevOps, cloud-native, and all the new stuff? In part one of this discussion, I talk with Matt Walburn about how EA’s fit into The Business. Rough Outline  Rorschaching “Enterprise Architect” (EA) The bad parts of EA - governance “Neo-classical DevOps” Matt Walburn - AWS, Pivotal, Target. DIY Whitepaper Understanding how the business works, the customers (internal and external), what IT is in place. What’s the “operating model” for figuring out what IT does: deciding on the plan, finance, HR, translating things to developers. Taking out COTS and desktop management - however, commoditizing by going SaaS and IaaS is likely important. Figuring out how the business works. Experiences their customers work with that are supported by IT, e.g., eCommerce, mobile device, call-center. Figuring out the stick figures and the lines to boxes - user-centric design and thinking. Agile, value-streams.  Outcomes/What is “strategy”? Outcomes - result (monetary, usually) you want. How you’ll achieve it (e.g., sell through mobile apps)… working backwards to the things required (in eCommerce, I need to show a catalog of products, get them to pay for it, ship it, handle returns, etc.) The value of TOGAF and ITIL side-note. How to ferret them out - sit in people with a room and walk back the business, a bunch of questions. “Boardio.” How to “model”/document them - taxonomy. How do these workflows/outcomes align to what the business is doing. Finding duplication that’s wasteful - if we want faster cycle-times, we want to democratize data access (more transparent, well-known data sources, etc.)… not burdened with re-creating. Not so much (or only) an “IT service” that’s duplicated, but sort of logical pools of data. Cost-removal is fine, but also removing conflicts and dealing with conflicts, and removing time-to-understand how all these different things work.  Define future vision, aka, “what do we [in IT] do now?” First step, how decoupled is the business from IT  Special Guest: Matt Walburn.

What’s the “business” side of enterprise architecture? And how does EA’ing start mapping to DevOps, cloud-native, and all the new stuff? In part one of this discussion, I talk with <a href="https://twitter.com/mattwalburn" rel="nofollow" target="_blank">Matt Walburn</a> about how EA’s fit into The Business. <h1>Rough Outline</h1> <ul> <li>Rorschaching “Enterprise Architect” (EA)</li> <li>The bad parts of EA - governance</li> <li>“Neo-classical DevOps”</li> <li><a href="https://twitter.com/mattwalburn" rel="nofollow" target="_blank">Matt Walburn</a> - AWS, Pivotal, Target.</li> <li><a href="https://content.pivotal.io/white-papers/the-upside-down-economics-of-building-your-own-platform" rel="nofollow" target="_blank">DIY Whitepaper</a></li> <li>Understanding how the business works, the customers (internal and external), what IT is in place.</li> <li>What’s the “operating model” for figuring out what IT does: deciding on the plan, finance, HR, translating things to developers.</li> <li>Taking out COTS and desktop management - however, commoditizing by going SaaS and IaaS is likely important.</li> <li>Figuring out how the business works. Experiences their customers work with that are supported by IT, e.g., eCommerce, mobile device, call-center.</li> <li>Figuring out the stick figures and the lines to boxes - user-centric design and thinking. <ul> <li>Agile, value-streams.</li> </ul></li> <li>Outcomes/What is “strategy”?</li> <li>Outcomes - result (monetary, usually) you want. How you’ll achieve it (e.g., sell through mobile apps)… working backwards to the things required (in eCommerce, I need to show a catalog of products, get them to pay for it, ship it, handle returns, etc.) <ul> <li>The value of TOGAF and ITIL side-note.</li> <li>How to ferret them out - sit in people with a room and walk back the business, a bunch of questions. “Boardio.”</li> <li>How to “model”/document them - taxonomy.</li> <li>How do these workflows/outcomes align to what the business is doing.</li> <li>Finding duplication that’s wasteful - if we want faster cycle-times, we want to democratize data access (more transparent, well-known data sources, etc.)… not burdened with re-creating. Not so much (or only) an “IT service” that’s duplicated, but sort of logical pools of data. Cost-removal is fine, but also removing conflicts and dealing with conflicts, and removing time-to-understand how all these different things work.</li> </ul></li> <li>Define future vision, aka, “what do we [in IT] do now?” <ul> <li>First step, how decoupled is the business from IT</li> </ul></li> </ul>Special Guest: Matt Walburn.

Episode 36: North-bound Enterprise Architecture with Matt Walburn - that business/IT alignment dance

Backed up into a corner, developers will start coding. It's little wonder then that as large organizations have been faced with modernizing their approach to software - all that "digital transformation" - developers in years past have been focusing on building their own platforms. Our guest this week, Matt Walburn, worked on one such project. He joins us this week to talk about the lure of the DIY platform and why, now that options like Pivotal Cloud Foundry are available, it's usually a poor use of organization time. Not only do you need to build the full platform with all the features from the development phase to running in production, but you have to maintain it as well. As Matt says, this will run you several millions of dollars in staff salary alone. And then, after all that, you still have to write all those applications you originally set out to make.See full show notes at http://pivotal.io/podcast

Backed up into a corner, developers will start coding. It's little wonder then that as large organizations have been faced with modernizing their approach to software - all that "digital transformation" - developers in years past have been focusing on building their own platforms. Our guest this week, Matt Walburn, worked on one such project. He joins us this week to talk about the lure of the DIY platform and why, now that options like Pivotal Cloud Foundry are available, it's usually a poor use of organization time. Not only do you need to build the full platform with all the features from the development phase to running in production, but you have to maintain it as well. As Matt says, this will run you several millions of dollars in staff salary alone. And then, after all that, you still have to write all those applications you originally set out to make. See full show notes at <a href="http://pivotal.io/podcast" rel="nofollow" target="_blank">http://pivotal.io/podcast</a>

034: Building DIY platforms: now you've got two problems, with Matt Walburn

Backed up into a corner, developers will start coding. It's little wonder then that as large organizations have been faced with modernizing their approach to software - all that "digital transformation" - developers in years past have been focusing on building their own platforms. Our guest this week, Matt Walburn, worked on one such project. He joins us this week to talk about the lure of the DIY platform and why, now that options like Pivotal Cloud Foundry are available, it's usually a poor use of organization time. Not only do you need to build the full platform with all the features from the development phase to running in production, but you have to maintain it as well. As Matt says, this will run you several millions of dollars in staff salary alone. And then, after all that, you still have to write all those applications you originally set out to make. See full show notes at <a href="http://pivotal.io/podcast" rel="nofollow" target="_blank">http://pivotal.io/podcast</a>

Episode 21: 034: Building DIY platforms: now you’ve got two problems, with Matt Walburn