{"id":20956,"date":"2019-11-07T10:43:11","date_gmt":"2019-11-07T16:43:11","guid":{"rendered":"https:\/\/blog.planview.com\/reflections-from-devops-enterprise-summit-2019-day-three-recap\/"},"modified":"2019-11-07T10:43:11","modified_gmt":"2019-11-07T16:43:11","slug":"reflections-from-devops-enterprise-summit-2019-day-three-recap","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/reflections-from-devops-enterprise-summit-2019-day-three-recap\/","title":{"rendered":"Reflections from DevOps Enterprise Summit 2019 + Day Three Recap"},"content":{"rendered":"
\n
\"Reflections<\/div>\n<\/figure>\n

It’s been just over a week since this year’s <\/span>DevOps Enterprise Summit 2019<\/span><\/a> in Las Vegas came to a close. And while we’re happy to be away from the artificial air that’s continuously pumped out at The Cosmopolitan, we will miss the breath of fresh air that many attendees and speakers brought to the DevOps discussion.  <\/span><\/p>\n

The third and final day of the conference saw our CEO and founder, Dr. Mik Kersten, return to the stage a year on from launching his Amazon best-selling book <\/span>Project to Product<\/span><\/i><\/a> and the pioneering <\/span>Flow Framework™<\/span><\/a>. Mik picked up the thread once again to share his and Tasktop’s experience of working with Fortune 100 organizations to help them transition to a product-centric operating model.<\/span><\/p>\n

<\/p>\n

“I’ve traveled the world asking business executives how do they measure the value of software delivery,” began Mik. “Typically I’m greeted by blank stares. I also ask them do they know where their bottlenecks are and receive the same response. I understand that language gap; when I started talking story points to our CFO, Simon Bodymore, I think he thought I was crazy and momentarily regretted joining Tasktop!”<\/span><\/p>\n

As Mik highlighted what needs to be done to improve conversations between IT and the business—a common language, broadening understanding across both sides, defining what value is and how it flows—he tackled the evergreen challenge of measurement, a major theme of DOES 2019. “When you find new ways to measure, you find new ways to innovate. Proxy metrics, like tracking activities instead of outcomes, coupled with treating IT as cost centre, will kill your transformation.”<\/span><\/p>\n

<\/p>\n

After using a story about a big U.S. bank to illustrate how billions can be squandered on transformation without reaping or measuring the benefits, Mik asked the audience to consider why they’re building software delivery in the first place. “Production is all about what customers are pulling, not what you’re producing. How you can help them pull what they want faster? And by that, we don’t mean lead time from when a Jira task is opened and closed, we mean the <\/span>customer’s<\/span><\/i> view of delivery from request to delivery. That’s all that matters.”<\/span><\/p>\n

Thinking like your customers is not a groundbreaking concept in itself, but in a complex practice like software delivery, it helps cut through the fog — especially at scale. “From a customer point of view, they just want more features and fast. It’s what makes them like your company’s mobile experience rather than your competitors. But that’s not the only thing that flows and impacts delivery…”(Learn more about what flows across your software delivery value streams<\/a>). <\/span><\/p>\n

Expanding on how defects impact product quality, risk work undermines customer trust, and tech debt impacts the ability to accelerate delivery of the key flow items, Mik drew on Tasktop’s experience on applying the Flow Framework™. By connecting toolchains, automating and visualizing how the key four work items flow across defined product value streams, Tasktop was able to generate flow metrics (through our new Viz product<\/a>) to measure performance from the customer’s perspective and make data-driven decisions to improve business outcomes.<\/span><\/p>\n

<\/p>\n

“When we identified that velocity was down for one product, we did exactly what I just told you we shouldn’t do. We increased manpower for that value stream, increasing our Flow Load. That led to velocity actually going down. But thanks to our visibility into our flow, we could see that problem and make a decision to address the bottleneck.” You can read more about Tasktop’s work with flow metrics and the development of Tastkop Viz, in Mik’s blog below (we’ll also update the blog with the video of the presentation once it’s available). <\/span><\/p>\n

https:\/\/blog.tasktop.com\/blog\/tasktop-viz-limited-release-announced-flow-metrics-made-easy\/<\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n