<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by IT Revolution Press on Medium]]></title>
        <description><![CDATA[Stories by IT Revolution Press on Medium]]></description>
        <link>https://medium.com/@ITRevBooks?source=rss-9f1c144175a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*0dZPkq1H0zSdJu-0.jpg</url>
            <title>Stories by IT Revolution Press on Medium</title>
            <link>https://medium.com/@ITRevBooks?source=rss-9f1c144175a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 09:43:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ITRevBooks/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DevOps Enterprise Summit Las Vegas 2019 Programming Highlights: What I’m Looking Forward To]]></title>
            <link>https://medium.com/itrevolution/building-excitement-and-expectations-for-devops-enterprise-summit-las-vegas-2019-25b41d996ed0?source=rss-9f1c144175a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/25b41d996ed0</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[gene-kim]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[IT Revolution Press]]></dc:creator>
            <pubDate>Fri, 04 Oct 2019 15:51:55 GMT</pubDate>
            <atom:updated>2019-10-08T14:41:25.164Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acwOKaTltFstY33M2KHFJQ.jpeg" /></figure><h4>by Gene Kim</h4><p>I am so excited about the upcoming <a href="https://events.itrevolution.com/us">DevOps Enterprise Summit Las Vegas</a>. As a <a href="https://events.itrevolution.com/us/about/">programming committee</a>, we seek to make each event better than the last, as measured by how much we learn and how it helps enable the DevOps Enterprise community to achieve their goals.</p><p>As a programming committee, we thought London 2019 was our best conference yet (almost unanimously), which poses a challenge of how we do could possibly do better — but I’ve found over the last several years that this is doable, mostly be being very explicit about what challenges across our community that we want to help to overcome.</p><p>This year, we focused on the following areas, and I think you’ll find that the upcoming conference does an amazing job of addressing them:</p><ul><li>Experience reports of technology leaders presenting with even more senior business leaders</li><li>Overcoming obstacles in security and compliance</li><li>Experience reports and subject matter experts in the areas of data science and data initiatives</li></ul><p>Reviewing this post, I’m finding that the number of amazing stories being presented is so good that it’s incredibly difficult to pick which ones to mention here. But, three speakers really stood out to me, because they’re so different than in previous years:</p><ul><li>Dr. David Almeda is Chief People Officer, Kronos. I was blown away when I saw him present. He talked about about how one of their top strategic goals was to attract and retain great talent — the result was Kronos being named as one of the top 100 best places to work by both Fortune Magazine and Glassdoor, enabling then to support continued growth, innovation and profitability. He’ll be teaching us the value of employee engagement, and how the top levels of leadership view it.</li><li>Dr. Andre Martin is VP and Chief Learning Officer, Google: Until recently, Dr. Martin was Chief Learning Officer at Target, and before that, at NIKE. He will be sharing what his charter was in those roles, and why those organizations created his role in the first place, and how it could advance the mission of the DevOps Enterprise community.</li><li>The Big Four Auditor panel: In this amazing panel, we have four distinguished experts who support the audit practice from each of the Big Four auditors. We will be busting the most commonly heard myths and objections about “why DevOps can’t work here” such as why DevOps can’t be done in regulated industry, why separation of duties prevents DevOps, and many more!<br><strong>Yosef Levine</strong>; Global Audit &amp; Assurance Risk and Controls, Confidentiality, and Privacy leader, Deloitte<br><strong>Michael Wolf</strong>; Managing Director — Modern Delivery Lead, KPMG<br><strong>Matt Bonser</strong>; Director, Digital Risk Solutions, PwC<br><strong>Pierre Fourie</strong>, Advisory Services Senior Manager, Ernst &amp; Young</li><li>(contd) Furthermore, they will be hosting two “Ask An Auditor Anything” workshops, facilitated by Dr. Tapabrata Pal and Sam Guckenheimer. This is an opportunity to anonymously ask questions about the audit process with some of the best experts in the space.</li></ul><p>I attended a smaller version of this session in London, and I thought it was incredible and truly notable. This one promises to be a landmark moment for the DevOps Enterprise community.</p><p>Without a doubt, the programming committee has worked hard to create a high learning experience filled with technology leaders pioneering the business practices that will surely be commonplace within a decade. This, combined with experts from the domains that we’re drawing upon to help achieve our goals-along with exciting networking opportunities each day of the event-has helped us establish an industry forum for exchanging insights and information we need as a community.</p><p>I hope you’ll join us in Las Vegas, and that you’re as delighted by the program as we are! In my career, I have grown to love conferences and have benefited so much from them. And yet, this conference is still my favorite. I never learn as much in such a short period than when I’m at the DevOps Enterprise Summit.</p><blockquote><strong><em>Special offer:</em></strong><em> Pre-order 10 copies (or more) of </em>The Unicorn Project<em> by October 30th and receive $350+ off your next conference registration, plus lots of other bonuses. Details here: </em><a href="https://itrevolution.com/unicorn-offer/"><em>https://itrevolution.com/unicorn-offer/</em></a></blockquote><h4>Thanks for Contributing + Changes from Last Year</h4><p>I want to thank everyone for submitting a proposal to DevOps Enterprise Summit for Vegas 2019. I personally appreciate and recognize the effort required to prepare your submissions. And I know because I still spend a lot of time preparing and submitting proposed abstracts!</p><p>This year was the most difficult selection process for the programming committee ever, especially when so many are friends and people whose work we all respect so highly!</p><p>To explain how we made decisions, I want to frame everything in terms of the conference programming objectives. Broadly speaking, here are the number of talk slots we reserved for each programming objectives:</p><p>One thing that you should notice right away is that every track only has a few slots. Another thing that you are probably unaware of is that we had more speaking submissions than ever before — it blows my mind just thinking about it.</p><h4>Evolving Programming Objectives</h4><p>In addition to the amazing response we received for this year’s call for presentations, we also worked to address some feedback from 2018 that “some talks sounded the same as last year.” So, we reviewed the talks again, and observed that some of the repeat speakers we invited didn’t have a lot of change since the last time they spoke. As a result, we’ve done two things:</p><ol><li>We’ve nearly halved the number of speaker slots for repeat speakers (see stats below) — 45% of repeat speakers (Vegas 2018) / 27% of repeat speakers (Vegas 2019)</li><li>We invited repeat speakers who have a large change to report, or a different perspective to share (e.g., a different co-presenter from another business area), etc.</li></ol><p>In general, our top-level goal every year is to help technology leaders succeed in transforming their organizations- both by increasing the likelihood of their success and accelerating the rate of adoption of DevOps principles and practices by focusing on the following talk tracks and subject areas listed above.</p><p>We aim to fulfill this goal through speaker presentations, both from technology leaders and/or subject matter experts from those domains. We also do this through less structured networking sessions where attendees can find other people who are tackling similar challenges or want to learn more about a particular area of interest.</p><h4>New Experience Reports</h4><p>One of the hallmarks of the <a href="https://events.itrevolution.com/us/">DevOps Enterprise Summit</a> is that our program focuses on spotlighting real world experience reports, straight from the mouths of those who are driving enterprise-scale transformation. As adult learners, and as leaders, there are few, if any, better ways to learn than watching how other people in similar situations to solve their problems.</p><p>Besides enabling learning, experience reports serve another important goal-they help us as leaders negate objections that “DevOps can’t be done here.” I’m happy to say that over the past six years, we’ve assembled a growing library of 250 experience reports from some of the most recognized brands around the world. As a whole, it shows that DevOps principles and patterns are universal across nearly every industry vertical today. Some of the new experience reports I cannot wait to here in October include:</p><ul><li><strong>Heather Mickman</strong> (VP Platform Engineering) and <strong>David Cherryhomes</strong> (VP, IT), UnitedHealth Group: Heather and David will be talking about their amazing work transforming business and technology at UHG, the largest healthcare company in the world, with over 115 million customers. (You will likely remember Heather from her pioneering work at Target, co-presenting with Ross Clanton from 2014–2015 and keynoting by herself in 2016).</li><li><strong>Fernando Cornago</strong> (Senior Director, Platform Engineering) and<strong> Benjamin Grimm</strong> (Senior Director, .COM), Adidas will be presenting about the work they have done to elevate developer productivity at Adidas, including supporting the incredibly important e-commerce initiatives, as well as product design. He will share how they’ve educated top executives and even board members on critical technology concepts, and how they’re making all data easy consumable by everyone across the company.</li><li><strong>Kira Barclay</strong> (Director, Analytics) and <strong>Elizabeth Conzo</strong> (Analytics Leader), John Deere: they will be presenting the amazing work they’ve been doing supporting both enterprise data initiatives, as well as incubating Horizon 3 initiatives and modernizing the software practices in some of the largest product lines at John Deere.</li><li><strong>Ralf Waltram</strong> (VP of IT Delivery) will be talking about the DevOps and Project to Product journey, which as he says, is how BMW is transitioning from project management to product management. In the BMW team’s words, this the “largest change to how business is done at BMW in twenty years.”</li><li><strong>Jim Lloyd</strong>, Chief of the Innovation Branch, Field Operations Directorate / <strong>Melinda Solomon</strong>, Agile Training Lead / Chief, Transformation Delivery Division at USCIS: Will be sharing the continuation of the DevOps journey at the US Citizenship and Immigration services, which was started by former CIO Mark Schwartz. Jim will be talking about specific mission objectives at USCIS, and the business and technology partnership.</li><li><strong>Jaclyn Damiano</strong> — Associate Director, Verizon / Josh Stone — Senior Architect/Evangelist, Verizon: Verizon has holistically undergone massive organizational and business changes in the past year. A voluntary separation package and outsourcing to 3rd parties has changed the makeup of the team and the culture. A corporate reorganization so significant it is defined as “Verizon 2.0”. They will be talking about how to stay the course on digital transformation, cloud migration, and culture change in such a turbulent environment.</li></ul><h4>Continued Experience Reports</h4><p>This year, we will have six companies back to present their continuing experience reports at the conference. Having this pattern of repeat speakers may be a bit unusual, but I personally love that we’re following these courageous leaders along their journey. For me, I liken the experience to having front-row seats to an unfolding documentary of the ongoing transformations that they are leading in their large, complex organization.</p><p>It’s great to know how these stories progress that spans more than one year. How was the story told from the previous year evolve for the organization and the leader? What new obstacles emerged, and how did they overcome them? Is this a path the rest of us want to go down? What are the things worth celebrating as part of this journey and why? For DevOps Enterprise Summit Las Vegas, we have the privilege of welcoming these people back to take the stage:</p><blockquote><strong><em>Special offer:</em></strong><em> Pre-order 10 copies (or more) of </em>The Unicorn Project<em> by October 30th and receive $350+ off your next conference registration, plus lots of other bonuses. Details here: </em><a href="https://itrevolution.com/unicorn-offer/"><em>https://itrevolution.com/unicorn-offer/</em></a></blockquote><h4>Spanning The Business and Technology Divide</h4><p>One of the top challenges we see year over year is ways to get business leadership onboard-and by that, I mean enthusiastic and grateful business partners, who want to tell the world how all their goals and aspirations are finally achieved by working together with their technology counterparts.</p><p>These are often the most difficult talks to find, because they require a technology leader with a great working relationship with their business counterpart, and that they’ve created visible successes. In Las Vegas 2018, we had some fantastic talks along these lines (from Nike, Capital One, Target, The Walt Disney Company and Kaiser Permanente).</p><p>This year, we’ll be featuring even more talks like this (33% more to be exact), showing how technology leaders are partnering with not just business leaders, but also other areas of the business, such as product leadership, security/privacy, legal, project management and so forth. Specifically, we are eager to hear from the CFO and Project Portfolio perspective. Here are a few talks I’m super excited to hear:</p><ul><li><strong>Chris O’Malley</strong> (CEO) and <strong>Joe Aho</strong> (CFO), Compuware: My fireside chat with Chris O’Malley last year was one of the most talked about sessions last year. I’ve invited him back with his CFO, asking them to teach us how to better interact with CFOs, a famously conservative group, and how we can win them over to help DevOps initatives.</li><li><strong>Levi Geinert</strong>, SVP, and Head of Agile Technology Experience, <strong>Werner Loots</strong>, EVP Consumer and Business Banking, U.S. Bank: Levi will be talking about his new role in the Experience Studios, where their goal is to reimagine banking, an effort being driven from the very highest levels of leadership. He and Werner will be speaking about some of their challenges and noteworthy successes, which has created excitement across the organization.</li></ul><h4>Next Generation Operations</h4><p>After hearing that Ops needed more representation at DevOps Enterprise Summit, in 2018 we reserved nearly a quarter of our talks to focus on Ops and Infrastructure challenges, and created a separate subcommittee to focus on this area. While we aren’t going to have as many next generation ops talks this year, it is our third largest talk track behind new experience reports and spanning the tech and business divide.</p><p>What’s amazing is that we learned the elevation of this topic has fundamentally changed the feel of the conference itself. The programming committee has made an effort to help define and clarify what exactly the role of Ops leader is, and how all the technology and organizational changes there have been in how infrastructure is designed, delivered and operated. I’m thrilled to be able to see this presentation this year:</p><h4>Subject Matter Expert Talks</h4><p>All leaders are, for the most part, self-teaching ourselves what we think we need to learn to be successful. Technology leaders in particular have to adapt to a somewhat constant rates of disruption and change happening around us. In the past, we’ve brought experts such as Dr. Christina Maslach (burnout) and Dr. Richard Cook (safety culture) to deliver talks about the domains we want to learn more about to help us reach our desired outcomes. This year we have the following subject matter experts onsite to deliver presentations:</p><ul><li><strong>Dr. Andre Martin</strong>, VP and Chief Learning Officer, Google: Until recently, Dr. Martin was Chief Learning Officer at Target, and before that, at NIKE. He will be sharing what his charter was in those roles, and why those organizations created his role in the first place, and how it could advance the mission of the DevOps Enterprise community.</li><li><strong>Christopher Bergh</strong> is a CEO and Head Chef at DataKitchen: He will be talking about the chronic problems of getting data from where it resides (typically trapped within data warehouses) to where it needs to go (by the teams who need data to make decisions, or manipulate it to make it more useful). Chris had a huge impact on the development of The Unicorn Project, and helped me see the parallel universe of DataOps.</li><li><strong>Dr. Nicole Forsgren</strong>, Head of DORA and <strong>Dr. Dustin Smith</strong>, Human Factors Psychologist and Senior User Experience Researcher, Google.</li></ul><h4>Networking Opportunities, Lean Coffee, Lightning Talks and More!</h4><p>In addition to all the wonderful talk tracks and exciting presentations above, the conference program creates a forum for different ways to “get together and go faster.”</p><p>I’ve said this before, but it is so important for the organizers of the DevOps Enterprise Summit to help attendees achieve their desired outcomes. One of the most special experiences at DevOps Enterprise Summit comes from meaningful 1:1 interactions with your fellow attendees.</p><p>To that end, and together with my friend and IT Revolution advisor, <a href="https://twitter.com/jgallimore?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Jeff Gallimore</a>, we have established different ways for people to learn, ask and answer as many questions as possible-based on experiments and what we learned from London earlier this year. Because the quality of the audience is one aspect that we think separates the DevOps Enterprise Summit from all the rest, the more spontaneous conversations and interactions we can nurture onsite, the better for all.</p><ul><li><strong>DevOps Confessions</strong>: At the beginning of each day, programming committee members will read anonymized stories of confessions from leaders in the DevOps community to learn about the struggles, failures, and near-misses. These are some of the best anecdotes you may ever hear!</li><li><strong>Speakers Corner</strong>: We created a dedicated time and a location to ask the plenary speakers questions that go deeper on the information presented earlier that day.</li><li><strong>Lean Coffee</strong>: Led by <a href="https://twitter.com/dominicad?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Dominica DeGrandis</a>, author of <a href="https://itrevolution.com/book/making-work-visible/"><em>Making Work Visible</em></a> and the foremost expert in Kanban Flow within the IT industry today, attendees can connect with and learn from their peers in a semi-structured format all three days of the conference.</li><li><strong>Birds of a Feather Sessions</strong>: This is more like the DevOpsDays unconference sessions, with less structure than a Lean Coffee format, and these sessions are driven by specific topics that attendees want to discuss and learn about. I thoroughly enjoyed the interactions of these sessions in Las Vegas last year.</li><li><strong>Lightning Talks</strong>: These are rapid-fire, <a href="https://www.youtube.com/watch?v=LJ-ZyZxv64A&amp;list=PLvk9Yh_MWYuzdmhogpwbcCvDqJ4V3beS2">must-see presentations</a> that happen from the main stage after the conference day has concluded. Also, as a bonus, the <a href="https://itrevolution.com/devops-books/">IT Revolution authors</a>’ book signing happens immediately afterward.</li><li><strong>Industry Party</strong>: In addition to sponsor giveaways, great food and drinks, this is when I’ll have the book signing of my newest title, <a href="https://itrevolution.com/the-unicorn-project/"><em>The Unicorn Project</em></a>. The industry party is one of my favorite times during the conference to continue conversations with my fellow attendees and speakers.</li><li><strong>Slack Workspace</strong>: The conference will have a shared Slack workspace for people to interact with speakers, attendees, and sponsors. In the past, this is where people have connected to make plans, search/recruit for job opportunities and more.</li></ul><p>As you can see, there’s a lot that is getting me excited for the conference this year, and I hope to see you there!</p><p>Thanks,<br>Gene</p><p><em>To preview the DevOps Enterprise Summit Las Vegas 2019 event and learn more about the conference, please watch previous </em><a href="https://www.youtube.com/channel/UCkAQCw5_sIZmj2IkSrNy00A/playlists"><em>videos of our presentations</em></a><em>, download the past </em><a href="https://github.com/devopsenterprise"><em>speakers’ slide decks</em></a><em>, and </em><a href="http://events.itrevolution.com/photos/"><em>view photos from all past events</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://itrevolution.com/devops-enterprise-summit-las-vegas-2019-expectations/"><em>https://itrevolution.com</em></a><em> on October 4, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25b41d996ed0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itrevolution/building-excitement-and-expectations-for-devops-enterprise-summit-las-vegas-2019-25b41d996ed0">DevOps Enterprise Summit Las Vegas 2019 Programming Highlights: What I’m Looking Forward To</a> was originally published in <a href="https://medium.com/itrevolution">IT Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gene Kim Q&A with the Authors of Team Topologies]]></title>
            <link>https://medium.com/itrevolution/gene-kim-q-a-with-the-authors-of-team-topologies-31b162edbc29?source=rss-9f1c144175a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/31b162edbc29</guid>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[IT Revolution Press]]></dc:creator>
            <pubDate>Wed, 02 Oct 2019 19:38:54 GMT</pubDate>
            <atom:updated>2019-10-02T19:38:54.387Z</atom:updated>
            <content:encoded><![CDATA[<h4>Gene Kim speaks with <a href="https://twitter.com/matthewpskelton">Matthew Skelton</a> and <a href="https://twitter.com/manupaisable">Manuel Pais</a> about their new book <a href="https://itrevolution.com/book/team-topologies/">Team Topologies</a> — Organizing Business and Technology Teams for Fast Flow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*fkIyYqoG5lBqmj9fYvfjqQ.jpeg" /></figure><p><strong><em>Gene:</em> Every company loves an org chart, but why are they really so misleading</strong></p><p><em>Matthew and Manuel:</em> Org charts are management-focused constructs, meant to funnel lines of reporting from the bottom to the top — the typical hierarchical pyramid. The fundamental problem is extrapolating this construct and assuming it actually represents the lines of communication in the organization, alignment of business goals and decision making power.</p><p>This misinterpretation still happens in most organizations today and leads to known issues of knowledge silos, power grab, “us vs. them” mentality, lack of business alignment, and decisions made by those with a superficial (aggregated) view on the subject.</p><p>What we’re saying with <a href="https://itrevolution.com/book/team-topologies/">Team Topologies</a> is that in today’s world, organizations need to expand their approach to team structures and interactions in an evolutionary way if they want to survive. Empowering people and teams to be the best versions of themselves is key to success in this era.</p><p><strong><em>Gene</em>: How can someone who’s not a manager use this book?</strong></p><p><em>Matthew and Manuel</em>: A good chunk of the material in <em>Team Topologies </em>focuses on behaviors and characteristics of the different types of teams and different team interaction modes (covered in Chapter 5 and Chapter 7). These sections describe, in detail, patterns and behaviors that teams can adopt to be more effective at building and running software, so these are ideal for non-managers to read. We wrote these sections to be particularly useful to developers, testers, business analysts, product owners, DevOps people, SREs, etc. — people within teams who would benefit from clearer team interactions.</p><p>We expect the team patterns in <em>Team Topologies</em> will help team members to detect and correct unhealthy team-to-team interactions, improving how their team works with other teams. In this way, we’re empowering people to improve their work environment through better team interactions and more defined team behaviors.</p><p><strong><em>Gene:</em> How can someone who is a manager use this book to convince their leaders to undertake another re-org?</strong></p><p><em>Matthew and Manuel:</em> A manager can use <em>Team Topologies</em> to explain to their leaders why they should <em>stop</em> doing re-orgs! Part of the paradigm shift in dynamic organizations is understanding that re-orgs can no longer keep up with the pace of innovation in terms of technology, methodologies, and people interactions. Instead of discrete revolutions (e.g. Agile, DevOps, SRE), we need continuous evolution and feedback from team structures and interactions.</p><p>Specifically, they can start by mapping existing teams to the four fundamental topologies, as mentioned in Chapter 5 (pages 104–109) of <em>Team Topologies</em>. What that enables is identifying the gaps between current behaviors, skills, and interactions in the existing teams and those expected in the fundamental types. We find that helps identify and reduce misalignment of priorities and business goals (which slow down flow), as well as increase clarity on who’s responsible for which services and how other teams are supposed to interact with them.</p><p>Once that mapping process has started, you also get a 30,000-foot view of your organization’s delivery and operational capabilities, inter-team dependencies, and intra-team cognitive load. You can then start to set up the organization to acquire missing capabilities, empower autonomous teams, and reduce cognitive load — for example, with a modern platform approach, as described in <em>Team Topologies</em>.</p><p><strong><em>Gene:</em> Why are the interaction modes so important?</strong></p><p><em>Mathew and Manuel</em>: The near-legendary systems thinker Russell Ackoff said, “Problems that arise in organizations are almost always the product of interactions of parts, never the action of a single part.” Organizations are sociotechnical systems, and this is especially true of organizations that build and run business-critical software systems. If you think about it, the main thrust of the entire DevOps movement since 2008 has been to improve how different parts of the organization work together, first looking at Development (Dev) and IT Operations (Ops) but then expanding beyond those groups into other parts of the organization.</p><p>When we (Matthew and Manuel) went into organizations to help them improve the effectiveness of their software delivery, we often saw teams struggling to understand how they should relate to other teams and why. People would be told to “collaborate” without any context or clear outcomes; teams would expect a certain level of service from another team that had no idea that such service was expected of them! The lack of clarity about team interactions was (and is) causing huge amounts of waste and frustration within organizations; this in turn — via Conway’s Law — results in software architecture that is messy and poorly aligned to team responsibilities, making it difficult to evolve and support.</p><p>In <em>Team Topologies</em>, we decided to characterize what we see as the essential three team interactions modes, the only ways in which teams building and running software really need to interact. By adopting the three interaction modes, organizations can help their staff understand why different teams are interacting in different ways at different times, contextualizing the work in hand, and providing a way to detect misplaced boundaries and capabilities.</p><p>Using the three team interaction modes, organizations also can develop a much clearer picture of the likely software architecture that will result from the communication structures in the organization and “course correct” much sooner than in the past by adjusting skills, capabilities, and responsibility boundaries to suit the changing business demands.</p><p><strong><em>Gene:</em> Only four team types? How can that be true?</strong></p><p><em>Matthew and Manuel:</em> We asked ourselves the same question, to be honest! But as we applied the patterns in the <a href="http://devopstopologies.com/">DevOps Topologies</a> (a catalog of contextualized team structures for DevOps) in our consulting work, and also during our research and case studies, we saw these fundamental topologies repeated across the board with different terminology but essentially the same approach. <em>Team Topologies</em> gives them a name and clarifies the expected purpose, responsibilities, and behaviors for each team type. Having a shared language to talk about team organization and interactions can be very powerful to convey challenges to effective software delivery and operations, as well as generate empathy between people across the organization.</p><p>We started with stream-aligned teams, a cross-functional team aligned with a business stream of work that is able to build and run a service independently (let’s say at least 80% of the time). This pattern has been proven to be the most efficient for fast flow without damaging the quality and operability of the delivered services. We don’t need to go any farther than the DOES conferences to find numerous success cases.</p><p>Another emerging pattern are platform teams, but with a focus on DevEx and (internal) customer satisfaction rather than on standardization for the sake of standardization. In other words, the idea of “treating your platform as a product.” Organizations from <a href="https://www.youtube.com/watch?v=Wis_q-RWNLY">Adidas</a> to <a href="https://www.youtube.com/watch?v=Rg5d-_H04WI">BMW</a>, <a href="https://www.youtube.com/watch?v=SeuIty069oI">ITV</a>, and <a href="https://www.youtube.com/watch?v=_DnYSQEUTfo">Capital One</a>, to name a few, have reaped the benefits of enabling stream teams to go faster with self-service platforms and also by helping them upskill their operational capabilities.</p><p>The last two team types (enabling and complicated-subsystem) are less common but also support stream teams by filling in capabilities and/or knowledge gaps, and <a href="https://techbeacon.com/app-dev-testing/forget-monoliths-vs-microservices-cognitive-load-what-matters">reducing their cognitive load</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31b162edbc29" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itrevolution/gene-kim-q-a-with-the-authors-of-team-topologies-31b162edbc29">Gene Kim Q&amp;A with the Authors of Team Topologies</a> was originally published in <a href="https://medium.com/itrevolution">IT Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing The Unicorn Project, Availability of First Excerpt, And The Five Ideals!]]></title>
            <link>https://medium.com/itrevolution/announcing-the-unicorn-project-availability-of-first-excerpt-and-the-five-ideals-aeced1254917?source=rss-9f1c144175a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/aeced1254917</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[IT Revolution Press]]></dc:creator>
            <pubDate>Thu, 26 Sep 2019 16:43:53 GMT</pubDate>
            <atom:updated>2019-09-26T16:48:08.914Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*Xc4Q8wWe7gnO5XUw.jpg" /></figure><p>by <a href="https://twitter.com/RealGeneKim">Gene Kim</a></p><p>I’m so pleased to announce that <a href="https://itrevolution.com/the-unicorn-project/"><em>The Unicorn Project </em></a>will be released in all forms (hardcover, ebook, and audio) on November 26, 2019. I’m so excited that over the next couple of months I’ll be posting at least weekly on topics covered in the book or topics that have intrigued and captivated me over the last 2+ years.</p><p>In this post, I’ll cover the following:</p><ul><li>What is <a href="https://itrevolution.com/book/the-unicorn-project/"><em>The Unicorn Project</em></a> and why should I read it?</li><li>The Five Ideals</li><li>Availability of the <a href="https://itrevolution.com/the-unicorn-project/">first excerpt</a>!</li></ul><h3>What is The Unicorn Project and Why Should I Read It?</h3><p><em>The Unicorn Project</em> retells the story of <a href="https://itrevolution.com/book/the-phoenix-project/">The Phoenix Project</a> from the perspective of development and architecture. It explores the invisible structures that are required to make developers (and all engineers) productive, which is absolutely required for the initiatives they work on to achieve their goals. It is about technical debt and the incredible damage it creates, as well as how we create the opposite conditions — an architecture that enables developers to quickly, independently, and safely develop, test, and deliver value to customers, and where we are continually focused on elevating developer productivity.</p><p>What makes this problem so insidious is that architecture and the systems that developers rely on for their daily work are invisible. Everyone can see features, or the application. Therefore, they are easy to fund. However, far less visible are the APIs and architectures those features rely on, as well as the processes and infrastructure that developers need to get their daily work done.</p><p>This book is also about rebellion and coalition-building, and about how small teams are able to achieve all the amazing outcomes described in <a href="https://itrevolution.com/book/the-phoenix-project/"><em>The Phoenix Project</em></a>, despite seemingly endless resistance from powerful, entrenched functional silos. These are stories about about transformational leadership and courage, which are very much inspired by the heroic journeys I’ve had the privilege of observing and studying for the last seven years within the DevOps enterprise community.</p><p>This book also examines the problems posed by data, and what is required to actually use it to solve our most pressing business problems. Digital disruption requires us to understand our customers, and is greatly aided by data we already have, which we need to manipulate, transform, and safely allow teams to use.</p><p>So much of the genesis of the DevOps movement was to address the huge problems of getting code into production. These days, there is an orthogonal problem of getting data from where it resides (often trapped in data warehouses) to where it can be used by teams to help their organizations win in the marketplace. I’m hoping that this book conclusively demonstrates to all that data is ultimately a software effort, and can be massively helped by DevOps principles and patterns.</p><h3>Some of My Favorite Quotes about The Unicorn Project:</h3><p><em>“Every company going through a digital transformation needs to make this a must-read for all leaders.”</em> — <a href="https://www.linkedin.com/in/courtney-kissler-0930681/">Courtney Kissler</a>, VP Global Technology, NIKE, Inc.</p><p><em>“Gene Kim does a masterful job of showing how a dynamic, discovery-oriented approach to technology transformation can combine the efforts of many to create lasting business advantages for all.”</em> — <a href="https://www.linkedin.com/in/stevespear/">Dr. Steve Spear</a>, author of The High-Velocity Edge, Sr. Lecturer at MIT, and principal of HVE LLC.</p><p><em>“The Unicorn Project is amazing, and I loved it 100 times more than The Phoenix Project….It made me remember every step we’ve gone through at adidas in the last 4 years.”</em> —<a href="https://www.linkedin.com/in/fernando-cornago-763a782/?originalSubdomain=es"> Fernando Cornago</a>, Senior Director Platform Engineering, adidas</p><p><em>“As important as The Phoenix Project was for managing organizational change, The Unicorn Project is for the vast majority of us who actually solve problems. This book provides a vision for software engineers for generations to come.”</em> — <a href="https://www.linkedin.com/in/longstaff/">Dr. Tom Longstaff</a>, Chief Technology Officer, Carnegie Mellon University Software Engineering Institute</p><p><em>“The Unicorn Project is the organizational civil-war novel that every technology and business trailblazer must read.”</em> — <a href="https://www.linkedin.com/in/christophertomalley/">Christopher O’Malley</a>, President and CEO, Compuware</p><p><em>“The Unicorn Project clarifies the what and why of digital transformation.”</em> — J<a href="https://www.linkedin.com/in/jeffreysnover/">effrey Snover</a>, Technical Fellow, Microsoft</p><h3>The Five Ideals (and a Video)</h3><p>In <a href="https://itrevolution.com/book/the-phoenix-project/"><em>The Phoenix Project</em></a>, we used the constructs of the Three Ways and Four Types of Work to frame some of the important concepts in the book. Similarly, in <a href="https://itrevolution.com/book/the-unicorn-project/"><em>The Unicorn Project</em></a>, I use the Five Ideals to frame what I think are the most important problems facing engineering and business today:</p><ul><li><strong>The First Ideal</strong> — Locality and Simplicity</li><li><strong>The Second Ideal</strong> — Focus, Flow, and Joy</li><li><strong>The Third Ideal</strong> — Improvement of Daily Work</li><li><strong>The Fourth Ideal</strong> — Psychological Safety</li><li><strong>The Fifth Ideal</strong> — Customer Focus</li></ul><p>Over the next several weeks as we release more of the excerpts, I’ll talk about each of the ideals, and share several personal stories that convinced me why they are so important.</p><p>(For those of you who can’t wait, you can find a 30-minute video <a href="https://youtu.be/IOmoHCLDsG4?t=2086">here </a>of my Portland DevOpsDays talk on this. Not only was I introduced by the amazing <a href="https://twitter.com/alicegoldfuss">Alice Goldfuss</a>, but it’s the first time I’ve talked about The Five Ideals externally. You can also find my slides <a href="https://www.slideshare.net/realgenekim/the-unicorn-project-and-the-five-ideals">here</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.slideshare.net%2Fslideshow%2Fembed_code%2Fkey%2Fq6sIegaKFZBFV5&amp;url=https%3A%2F%2Fwww.slideshare.net%2Frealgenekim%2Fthe-unicorn-project-and-the-five-ideals%3Fref%3Dhttps%3A%2F%2Fmedium.com%2Fnew-story&amp;image=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2F201909portlanddevopsdaysunicornproject3a-190912205636-thumbnail-4.jpg%3Fcb%3D1568321865&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=slideshare" width="600" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/411af2594223c04bd830078f47e00ae0/href">https://medium.com/media/411af2594223c04bd830078f47e00ae0/href</a></iframe><p><a href="https://www.slideshare.net/realgenekim/the-unicorn-project-and-the-five-ideals"><strong>The Unicorn Project and The Five Ideals</strong></a><strong> </strong>from <a href="https://www.slideshare.net/realgenekim"><strong>Gene Kim</strong></a></p><h3>Download Excerpt #1 of The Unicorn Project</h3><p>Over the next several weeks, we will be releasing excerpts of <em>The Unicorn Project</em>. To download the first 58-page excerpt, click <a href="https://itrevolution.com/the-unicorn-project/">here</a>.</p><h3>Stay Tuned!</h3><p>As I mentioned, I’ll be posting many more articles <a href="https://itrevolution.com/devops-blog/">here</a> (as well as on the IT Revolution <a href="https://www.facebook.com/itrevolutionofficial/">Facebook page</a>) at least weekly on topics relevant to <em>The Unicorn Project</em> — so stay tuned!</p><p>And the next excerpt will be posted in about a week! Please feel free to share what you thought of the book on Twitter or LinkedIn — just @mention me. I’m <a href="https://twitter.com/RealGeneKim">@realgenekim</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aeced1254917" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itrevolution/announcing-the-unicorn-project-availability-of-first-excerpt-and-the-five-ideals-aeced1254917">Announcing The Unicorn Project, Availability of First Excerpt, And The Five Ideals!</a> was originally published in <a href="https://medium.com/itrevolution">IT Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Go Beyond Team Structures for Software Delivery Success]]></title>
            <link>https://medium.com/itrevolution/go-beyond-team-structures-for-software-delivery-success-9bc48ddf099a?source=rss-9f1c144175a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bc48ddf099a</guid>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[IT Revolution Press]]></dc:creator>
            <pubDate>Thu, 12 Sep 2019 20:48:05 GMT</pubDate>
            <atom:updated>2019-09-17T22:45:34.004Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aVRXV2y1jibaWTYj.jpg" /></figure><h4><em>by </em><a href="https://twitter.com/matthewpskelton"><em>Matthew Skelton</em></a><em>, co-author of </em><a href="https://itrevolution.com/book/team-topologies/">Team Topologies</a></h4><h4>Key Takeaways:</h4><ol><li>New team-based organizational designs are proving valuable across the IT industry.</li><li>Adopting new team structures is only part of the picture: it’s the interactions between teams that really counts.</li><li>Since 2013 many organizations have used the DevOps topologies patterns to explore different team models.</li><li>The new book Team Topologies by Matthew Skelton and Manuel Pais addresses important organization dynamics around team-based software delivery.</li></ol><h3>Team-First is the New Normal for Enterprise Software Delivery</h3><p>High-performing organizations have been adopting a team-first approach to software delivery for many years, and this approach is now becoming more widely adopted. The eagerly-anticipated <a href="https://cloud.google.com/devops/state-of-devops/">2019 State of DevOps Report</a> emphasizes the importance of empowering teams to accomplish outcomes that align to organizational goals, noting that such organizations significantly outperform organizations that have not adopted modern practices.</p><p>There is an increasing body of evidence from industry and research to show that the functional silos of the 1990s and 2000s are no longer appropriate for the fast-moving world of modern software delivery. Charles T. Betz, Principal Analyst at Forrester Research, says that the “<a href="https://go.forrester.com/blogs/product-thinking-not-just-for-developers/">integrated, semiautonomous, multi-skilled product team is here to stay. It is the most effective means for discovering and delivering value to customers</a>.”</p><p>The need for new team types and team structures is being driven partly by the need to optimize for the reliable flow of change; handovers between teams of specialists can block flow and cripple delivery performance; instead, many organizations are adopting models that align teams to the streams of change.</p><h3>Patterns for Team-Based Delivery Can Help Significantly</h3><p>These days I spend much of my time helping organizations optimize and evolve their teams for better software delivery. My interest in this space goes back many years: I’ve performed music in bands, choirs, and orchestras since I was at school, and I think I have developed a deep sense of how different groups need to work together to make a bigger whole emerge (whether through music or software).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/0*qpCPzIg8nPZA4uYD.png" /></figure><p>Between 2006 and 2011 I was Technical Director at digital agency in London where we often worked together with other suppliers to deliver large-scale ecommerce systems for global brands and financial services clients. This gave me a practical awareness of how collaboration and service boundaries affect software designs (in good and bad ways).</p><p>In 2013 I first published the <a href="http://devopstopologies.com/">DevOps topologies patterns</a> that have become the <em>de facto</em> industry standard for discussing team-based software delivery for modern enterprises. These patterns (and anti-patterns) explore different ways of arranging collaboration and service boundaries for IT teams and the implications for organizations. Together with Manuel Pais and others, these patterns evolved as a community resource to be used by many forward-thinking organizations around the world, including Netflix, Condé Nast International, Adidas, and Accenture.</p><p>For instance, here is Philip Fisher-Ogden, Director of Engineering at Netflix describing how the topologies patterns have helped Netflix:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/0*eCunQmRvlAMkhCRm.png" /></figure><p>The patterns have also helped global publisher Condé Nast International. Here is Crystal Hirschorn, VP Engineering, describing why they found the patterns useful:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/0*5DcsFCdUvbtMmzAW.png" /></figure><p>The DevOps topologies patterns resonate with people because they help to stimulate conversations about the different kinds of dynamics that different responsibility boundaries and collaboration approaches can bring. They are a great starting point for thinking about modern enterprise software delivery, but what’s missing?</p><h3>Team Interactions and Collaboration Boundaries Matter More than Static Structure</h3><p>When Manuel Pais and I were working with various organizations around the world (China, USA, Europe), we realized that the static team boundaries in the DevOps topologies patterns didn’t tell the whole story. Some organizations had adopted the well-known “<a href="https://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify">Spotify model</a>” but found that software delivery had not really improved. We realized that there are many dimensions around software delivery — not just team structure — that organizations need to address to be successful, including:</p><ul><li>Conway’s Law</li><li>Team cognitive load (see our <a href="https://www.youtube.com/watch?v=haejb5rzKsM&amp;list=LLF4v2VEsYSd1XIodd0YyLYg&amp;index=25">DOES EUR 2019 talk on team cognitive load</a>)</li><li>Team interactions</li><li>Dynamic organization evolution</li></ul><p>In fact, the legend of systems thinking, Russell Ackoff, famously said that:</p><blockquote>“An organization is a system and the performance of a system depends more on how its parts interact than on how they act when taken separately.”<em><br> — Russell Ackoff, Management f-LAWS, 2007</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/206/0*SkXB8tsnTr_FPNP5.jpg" /></figure><p>This is borne out by the experience of many forward-thinking organizations building and running software today. Success lies not simply in creating a new organizational design but in defining clearly how the different teams should interact and collaborate and — crucially — the “why” behind these patterns.</p><p>With our 2019 book <a href="https://medium.com/itrevolution/go-beyond-team-structures-for-software-delivery-success-9bc48ddf099a?sk=cdbd42200455b956fef58749fcbddd52?utm_medium=referral&amp;utm_source=medium&amp;utm_term=ttop-ms-1-medium-9_17-1&amp;utm_content=onsale&amp;utm_campaign=ttop"><em>Team Topologies</em></a><em> </em>we have aimed to move forward the conception of team-based software delivery by explicitly addressing the ways in which teams should interact for effective delivery with a set of patterns that are easy to recognize. This enables us to detect problems and adjust team interactions to meet new market or regulatory challenges quickly, treating the organization as “a complex and adaptive organism,” in the words of organization design expert Naomi Stanford. Organizations around the world are finding the Team Topologies approach very illuminating and useful for improving their software delivery capabilities.</p><p><a href="https://twitter.com/matthewpskelton"><em>Matthew Skelton</em></a><em> and </em><a href="https://twitter.com/manupaisable"><em>Manuel Pais</em></a><em> both run training courses and consulting based on the Team Topologies approach. Find out more at </em><a href="https://teamtopologies.com/"><em>teamtopologies.com</em></a></p><p><em>Originally published at </em><a href="https://itrevolution.com/beyond-team-structures/"><em>itrevolution.com</em></a><em> on September 12, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9bc48ddf099a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itrevolution/go-beyond-team-structures-for-software-delivery-success-9bc48ddf099a">Go Beyond Team Structures for Software Delivery Success</a> was originally published in <a href="https://medium.com/itrevolution">IT Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gene’s Q&A with Mark Schwartz]]></title>
            <link>https://medium.com/itrevolution/genes-q-a-with-mark-schwartz-19f9cfcfad13?source=rss-9f1c144175a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/19f9cfcfad13</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[IT Revolution Press]]></dc:creator>
            <pubDate>Wed, 22 May 2019 01:39:19 GMT</pubDate>
            <atom:updated>2019-05-28T22:47:26.279Z</atom:updated>
            <content:encoded><![CDATA[<figure><a href="https://itrevolution.com/book/war-and-peace-and-it/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-F-nBZJQwk3b7u0bmhdkA.jpeg" /></a><figcaption>War and Peace and IT — a new book by Mark Schwartz</figcaption></figure><h4>Gene Kim speaks with Mark Schwartz about Mark’s new book, <a href="https://itrevolution.com/book/war-and-peace-and-it/"><em>War and Peace and IT</em></a><em> — Business Leadership, Technology, and Success in the Digital Age.</em></h4><blockquote><strong>Gene Kim: </strong>What inspired you to write a <a href="https://itrevolution.com/book/war-and-peace-and-it/">book</a> about IT management for business leaders?</blockquote><p>Mark Schwartz: I meet with executives from over a hundred large enterprises each year. It’s amazing how patterns emerge: so many of them are trying to transform digitally, trying to find new sources of growth and to survive disruption-and yet they are frustrated that they can’t seem to get there. And in virtually all of those cases the root cause is the same: the relationship between “the business” and IT is the problem.</p><p>My previous book, <em>A Seat at the Table </em>, made the case that organizations needed to change the way they incorporated IT into the rest of the enterprise; that working with IT in an arms-length, contractor-type relationship was holding them back from being fully successful. That book was written for senior IT leaders.</p><p>Based on the feedback I received from readers, it became clear to me that I needed to write a book looking at the business-IT relationship from the point of view of non-IT business leaders. That’s exactly what <a href="https://itrevolution.com/book/war-and-peace-and-it/">this new book</a> is.</p><blockquote><strong>GK: </strong>What is the key conclusion you hope business leaders will draw from the book?</blockquote><p>MS: Most importantly, there is a message of hope! New ways of thinking about technology and how it supports the company’s business or the agency’s mission are powerful and effective. They can increase innovation, help companies grow, mitigate risk, improve compliance, get products to market quickly…what else could you ask for? I’m talking about things like the cloud, DevOps, and Lean IT, for example. What the financial markets want, what the board of directors wants, and what the CEO, CFO, CMO, and other senior executives want-it is all “easily” available.</p><p>I say “easily” but what I mean is that it is available once the company thinks a bit differently about how it uses technology, or more importantly, how it works with its technologists. In this book, I try to show why the traditional way of thinking about technology is holding companies back, and what can be done to change it and succeed. Succeed wildly.</p><blockquote><strong>GK: </strong>How can the old management crowd overthrow their own stereotypes about IT “nerds” and learn to work with them instead of against them?</blockquote><p>MS: Well, for one thing, the “old” management crowd is constantly being replaced by a young management crowd, for whom a lot of what I say is instinctive. For another, we’ve all quietly and without realizing it become nerds.</p><p>For decades, the nerds were better at technology than everyone else because they knew enough to turn devices off and back on again to solve problems-now that’s common knowledge. Plenty of senior leaders who think they don’t know anything about technology can talk fluently about how many pixels their camera has, how to get Google to show the right search results, what the cloud is and how much money they’ll save by “migrating” to it, and how to work their Apple Watches. More importantly, they are all consumers of digital services, shopping and banking online.</p><p>And by the way, the nerds are often quite business-savvy. And the nerds have to learn to drop their stereotypes about the “suits” as well.</p><p>The important point is that changing the working relationship with the nerds leads to business success, and everyone likes that. Pick any key business metric you want to improve, and you will see that the ideas and suggestions in this book will improve it.</p><blockquote><strong>GK: </strong>What can IT leaders learn from reading this book? Is it only for business leaders?</blockquote><p>MS: I like to think that it is essential reading for IT leaders as well. The idea is to open a dialogue between IT and other business leaders, and this book frames the conversation in terms that are meaningful to both. Many IT leaders are excited about what they can now accomplish- the business or mission-but struggle to explain their excitement to those outside of IT, but not for lack of trying.</p><p>I argue that IT leaders have wasted lots of effort trying to project ROIs and frame ideas in terms of what they think of as “business value” but which don’t resonate with the CFO or CEO. What the CIO really needs to do is to express business value in relation to the goals and worries of these other executives. Or, to put it differently, the CIO can help the other CXOs all become heroes. That’s what the book is about.</p><blockquote><strong>GK: </strong>Why Napoleon? Why <em>War and Peace</em>?</blockquote><p>MS: When I read <em>War and Peace </em>I was struck by the peculiar and frustrating situation Napoleon had gotten himself into. This is Napoleon-famed for his skills as a military leader-giving orders in the battle of Borodino that no one is following, for perfectly good reasons. How does that happen? Well, it hit me that Napoleon’s problem had fascinating parallels with organizations that find themselves unable to transform to meet the demands of change and disruption. I won’t give away the story here, but that’s what started my train of thought.</p><p>Once I saw the parallel, every page I turned in <em>War and Peace </em>(and there are lots of pages) brought a new revelation. Napoleon-outside of the military context-was an amazing transformational leader. He brought France the metric system and the Napoleonic code, ended the Inquisition and the Holy Roman Empire, and of course made the felt bicorn hat fashionable. What finally did him in-and I don’t mention it in the book-was his lack of agility. His army took Moscow-the capital of Russia-but Napoleon couldn’t figure out what to do next. Had he won the war or what? The Russians had abandoned Moscow. There was no one to surrender to him. This was the first time that had ever happened to him-the Russians had changed the rules and disrupted warfare-and he didn’t know what to do next. In his indecision, he kept his troops in Moscow for too long and then, strangely, decided to retreat to France…in the middle of the Russian winter!</p><p>If there is one thing you should learn from <a href="https://itrevolution.com/book/war-and-peace-and-it/">my book</a>: do not lead your troops through Russia in the middle of winter.</p><p><em>Originally published at </em><a href="https://itrevolution.com/qa-mark-schwartz-gene-kim-2/"><em>https://itrevolution.com</em></a><em> on May 22, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19f9cfcfad13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itrevolution/genes-q-a-with-mark-schwartz-19f9cfcfad13">Gene’s Q&amp;A with Mark Schwartz</a> was originally published in <a href="https://medium.com/itrevolution">IT Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project To Product: From Stories To Scenius]]></title>
            <link>https://medium.com/itrevolution/project-to-product-from-stories-to-scenius-51c1371bb332?source=rss-9f1c144175a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/51c1371bb332</guid>
            <category><![CDATA[books-and-authors]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[enterprise-technology]]></category>
            <dc:creator><![CDATA[IT Revolution Press]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 22:05:08 GMT</pubDate>
            <atom:updated>2018-12-04T22:08:21.949Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwh6BihdcVIVGvkZ1JZH8Q.jpeg" /></figure><h3>Project to Product: From Stories to Scenius</h3><h4><em>Guest blog post by Mik Kersten</em></h4><p>We learn through stories — either through our own or through those passed on by others that we admire. When I first read <a href="https://itrevolution.com/book/the-phoenix-project/"><em>The</em> <em>Phoenix Project</em></a>, I was amazed at how much technological wisdom could be passed on in story form. That story, perhaps more than any other, motivated people to find a new perspective on the current problems that plague enterprise IT, and to seek a better way.</p><p>I saw the publication of <em>The</em> <em>Phoenix Project</em> as a flare shot high into the sky, and those who took enough time to look up see knew that it meant they had to act. I didn’t fully understand the direction of the flare until I heard Gene Kim state, on the main stage of DevOps Enterprise Summit 2016 in San Francisco, that we had both the imperative and the ability to improve the lives of one million software practitioners worldwide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*EA8AjmWEXWjNu2JZepzCXw.jpeg" /><figcaption>Mik Kersten, Author of Project to Product</figcaption></figure><p>Like many others who saw the flare, I was motivated. And I realized then that I had learned something unique in my work with open source and with <em>Fortune</em> 500 organizations. It was those learnings that I wanted to contribute to the community. With this inspiration in mind, I approached Gene at the CA World conference a couple of weeks later. Gracious as always, he took the time to sit with me at the back of the exhibit hall and hear out my perspective even though we didn’t know each other.</p><p>I showed him some prototype visualizations that I had created to illustrate the effect that value streams have on software architecture over months and years. We then started geeking out on how programming language constructs defined software architecture, and how different languages could result in very different future value stream flows. For example, languages that had stronger type checking could mean much more work and many more conversations required to add a feature than a dynamic language. We even quipped that a new metric, called the “lunch factor” was needed to determine how tangled an architecture was, as measured by the number of people you needed to take out to lunch in order to make a change. This was where we found our mutual fascination in the intersection of programming, architecture, and software delivery value streams.</p><p>At the end of that conversation I got excited enough that I told Gene I wanted to document the various value stream integration patterns I had witnessed in organizations that were able to break the mold. I shared with him that one of the most influential books in my career as a developer was <a href="https://www.amazon.ca/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612"><em>Design Patterns </em>by Erich Gamma et al</a>. I wanted to create a similarly simple catalog of all the integration patterns that I had encountered, and give each a small story on how it could help support the Three Ways of DevOps — flow, feedback, and continual learning. Gene was positive about the idea and encouraged me to write a skeleton book proposal. When he read it, he emailed the IT Revolution Press editor, CC’ing me, and put the following line in his email.</p><p><em>“This is going to be an incredible and kick-butt book for every DevOps leader…guaranteed to be in every MBA curriculum in 10 years.” — Gene Kim, 2016</em></p><p>At that point, I was sure that Gene had misunderstood what I was planning on writing. I was intending to write a patterns catalog with a few stories embedded, not a proper book. I deliberated whether I should point this out to him or not, but instead chose to play out the scenario where Gene had heard what I said and just interpreted it very differently than me. I went on to better understand his perspective by reading almost all the books from IT Revolution Press. At that point I realized I wanted to do everything I could to contribute to the scenius that Gene helped foster.</p><p>“<em>Scenius stands for the intelligence and the intuition of a whole cultural scene. It is the communal form of the concept of the genius.” — Brian Eno</em></p><p>At this year’s DevOps Enterprise Summit Las Vegas conference, Gene introduced the concept of scenius to the audience. IT Revolution Press have done an amazing thing by nurturing and publishing books that have become the milestones on the journey of our scenius. I am honored to have been given the opportunity to try and produce one more of those milestones. In that process, I have learned just how open, far reaching, and fast moving the scenius that Gene willed into being through the DevOps Enterprise community is. For example, I have seen individual comments and tweets make it into multiple plenary talks in a matter of days. In other words, speakers not only pay attention to other scenius members, they also incorporate the broader communities’ insights into their talks. A new experience, report, or idea can influence the thinking of the entire community as soon as it is blogged. We are working in such a frenzied time that our collective ability to learn is what will direct our community, as well as the success of our organizations.</p><p>At this year’s DevOps Enterprise Summit conference, Gene stated that it’s no longer about the 1 million software practitioners. It is now about the approximately 40 million people involved in an ever-growing number of specializations across all software value streams. For us to work and collaborate effectively, we need a common language. We can no longer have the jargon of one discipline muddy communication with another. We need to make the Three Ways of DevOps span all the way from a support ticket to the boardroom. My goal for <a href="https://itrevolution.com/book/project-to-product/"><em>Project to Product</em></a> is to add to our scenius a common language and framework that helps us meet Gene’s goal of elevating our impact to improve the happiness and productivity of 40 million IT workers worldwide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/210/0*bOg4U4HTlWjd55x9.jpg" /><figcaption>Book Cover: Project to Product</figcaption></figure><p>While I took Gene’s “MBA curriculum” goal as a lofty and aspirational one, I’m happy to note that in spite of not being released yet, <em>Project to Product </em>is in now ranking in the top 20 new releases for textbooks under the “Business &amp; Finance&gt;Management” category on Amazon.</p><p>While I am pretty sure that it is not a textbook, I am hopeful that it will help us as a stepping stone on this journey. If you find it inspirational, please remember that what matters most is how you contribute to the scenius, whether publicly or through the influence that you make on your team or in your organization. IT Revolution is providing us with the playbooks. I hope that <em>Project to Product </em>provides you with a whole new play to maximize your impact in 2019 and beyond.</p><p><em>Originally published on </em><a href="https://itrevolution.com/project-product-stories-scenius/"><em>itrevolution.com</em></a><em> on November 19, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51c1371bb332" width="1" height="1" alt=""><hr><p><a href="https://medium.com/itrevolution/project-to-product-from-stories-to-scenius-51c1371bb332">Project To Product: From Stories To Scenius</a> was originally published in <a href="https://medium.com/itrevolution">IT Revolution</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>