BROADCASTS.com

What\u2019s the \u201cbusiness\u201d side of enterprise architecture? And how does EA\u2019ing 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\u2019s fit into The Business.

\n
• Rorschaching \u201cEnterprise Architect\u201d (EA)
\n
• The bad parts of EA - governance
\n
• \u201cNeo-classical DevOps\u201d
\n
• Matt Walburn - AWS, Pivotal, Target.
\n
• DIY Whitepaper
\n
• Understanding how the business works, the customers (internal and external), what IT is in place.
\n
• What\u2019s the \u201coperating model\u201d for figuring out what IT does: deciding on the plan, finance, HR, translating things to developers.
\n
• Taking out COTS and desktop management - however, commoditizing by going SaaS and IaaS is likely important.
\n
• Figuring out how the business works. Experiences their customers work with that are supported by IT, e.g., eCommerce, mobile device, call-center.
\n
• Figuring out the stick figures and the lines to boxes - user-centric design and thinking.\n\n
  \n
  • Agile, value-streams.
  \n
\n
• Outcomes/What is \u201cstrategy\u201d?
\n
• Outcomes - result (monetary, usually) you want. How you\u2019ll achieve it (e.g., sell through mobile apps)\u2026 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.)\n\n
  \n
  • The value of TOGAF and ITIL side-note.
  \n
  • How to ferret them out - sit in people with a room and walk back the business, a bunch of questions. \u201cBoardio.\u201d
  \n
  • How to \u201cmodel\u201d/document them - taxonomy.
  \n
  • How do these workflows/outcomes align to what the business is doing.
  \n
  • Finding duplication that\u2019s wasteful - if we want faster cycle-times, we want to democratize data access (more transparent, well-known data sources, etc.)\u2026 not burdened with re-creating. Not so much (or only) an \u201cIT service\u201d that\u2019s 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.
  \n
\n
• Define future vision, aka, \u201cwhat do we [in IT] do now?\u201d\n\n
  \n
  • First step, how decoupled is the business from IT
  \n
\n

Special Guest: Matt Walburn.