In this talk, you’ll hear about three types of metrics that organizations are using to get better at building and running software. You know, those organizations that are doing the “digital transformation” thing so that they can run their business with software that isn’t ancient and lame. BE LIKE A TECH COMPANY.
We all know development and operations metrics like lead time, error budgets, and mean time to repair. But we don’t focus on business metrics enough. And least of all, we don’t talk about internal, organization, or “culture” metrics enough. This talk gives an overview of 15 metrics across three types: technical metrics, business metrics, and culture metrics. If we look at the end-to-end process of software creation, usage, and work as an system to be programmed and refined, we need metrics across that entire system. This talk will help get you started.
This talk is based on real world case studies and is written up in my two books Monolithic Transformation and The Business Bottleneck. There’s also a summary article here.
The panel I put together and moderated for this year’s SpringOne. It turned out really well. Here’s the abstract:
When you’re trying to improve how your organization does software, how do you change what managers and executives do? We hear a lot about how developers and operators change, the composition of product teams, and always about Kubernetes. But there’s very little conversation about transforming management. This panel of managers will discuss what managers’ and executives’ roles new and old look like, managing managers, and how individual managers can manage their careers when their role changes.
The panelests: Neville George, Manager at Comcast; Jon Osborn, IT Executive at Bell Tracy, Ltd.; Jana Werner, Head of Transformation at Tesco Bank
This presentation explains why getting better at software is important and can help improve your business. It presents the product model of software development, in contrast to the typical project model. It then describes three common barriers to change and how some organizations overcome them. There are three case studies of real-world, large organizations used throughout as well to illustrate the major ideas.
Check out this recording of a recent talk of mine. Here’s the abstract:
Many Government organizations are getting better at software development, deployment and management by using techniques like DevOps, agile development, and product management. Cloud native technologies are making organizations’ software supply chains more efficient and reliable. Our substantial experience with open-source technology and continuous deployment approaches, offers a powerful accelerator for contact tracing and integrated citizen response solutions. Improvement is fragile, and scaling up in large organizations is difficult. This talk will discuss bottlenecks, challenges, and how Government agencies and organizations are succeeding.
Here’s a recording of one of my talks. It’s on what the operations team does when running in a platform, DevOps-y, whatever style:
Developers don’t need “services” from ops, they need products: continuously innovated platforms that evolve weekly. Once ops toil is removed, ops can focus on their customers’ – development – needs. Using stories & tactics from the real-world, this talk helps launch a platform-as-a-product strategy.
Most ops groups can’t give developers what they need. Ops is limited by traditional service delivery mindset and tools. Stability & reliability are now table-stakes when you’re releasing software daily. What developers need now from ops is innovation. Operations has rarely takes this innovation-driven, product approach to providing services, & instead focuses on delivering to specification & limiting SLAs. As with development, ops creates value with continuous operations, product managing their platforms and releasing frequently.
This talk covers how ops groups are transforming from a service delivery mindset a platform-as-a-product approach. With examples from Discover Financial Services, Rabobank, the US Air Force, & others the talk covers the concept, technologies & tools commonly used, & ops tactics needed to kick-off a platform-as-a-product strategy.
The cliché we all recite is that technology isn’t the problem, culture is. Put another way: if the hardware and software are fine and fresh, it must be the meatware that smells. Come hear several de-funking recipes from the world’s largest companies whose meat now smells proper.
I answered a few attendee questions in the webinar, and answered the rest in a Twitter thread afterwards.
In the cloud, DevOps, agile, whatever is hot and new era, the role of enterprise architects is rarely addressed. There’s probably plenty useful for them to do still. I’ve been trying to figure out what those things are recently.
Earlier this month I did a webinar with Nick at 451. He does a great job summarizing all the digital hoopla going around and I finish up with, predictably, why and how Pivotal can help out there, along with a few customer examples. Check it out!
Observations on how large organizations successfully go through Digital transformation.
When it comes to digital transformation, despite vast resources, large organizations are 40% less likely to be high performing organizations than smaller ones.
If you’re like me and you prefer the internet over meat-sacks, for more Pivotal material like free books and two months of free PaaS, check out my Pivotal page. Also, for some discounts to various conferences – including a few DevOpsDays – check out my discount code page.
I’m often asked to come speak on, well, the topic of “tell us about the new, interesting stuff out there that makes software development better…but don’t be pitching me anything.” This is my most recent cut at that kind of talk.
In this podcast with Michael Coté, who works at Pivotal in technical marketing, he and The New Stack founder Alex Williams talk about current production systems and development environments for building applications. According to Coté, Pivotal describes these new systems and environments as “cloud native.”
Over the course of this interview, Coté discusses best practices and illustrates three requirements for cloud native development and deployment: utilizing the patterns of microservices architecture, implementing a DevOps approach, and striving for continuous delivery as the primary vehicle for software delivery.
Check out my brief (~15 minutes) discussion with Alex Williams at The New Stack about how we’re thinking about the architecture of Pivotal Cloud Foundry. In addition to giving an overview of what Pivotal Cloud Foundry is and the cloud management and PaaS capabilities it has, I go over a way of thinking about the layered architecture (and why you’d care) that Andrew has been talking about recently.