I talk a little bit about managing your open source usage: security isn’t really a big deal if you put in place policy and tools, pick thriving communities, and the value of giving developers choice. Read more in our recent survey on the topic.
Sep 13 - How to Measure Developer Productivity with Metrics and More Coming up soon I'll be moderating a panel about developer metrics. We'll have three actual practitioners, so what I'm looking forward to is how they actually apply and don't apply the common DevOps-y metrics, how they put them in place, and how they use them to make the human situation better. Register for it and watch for free! Also, if you miss the actual date, you can watch the replay.
Here'sa short write-up of the developer toil survey the Tanzu Labs people use to find ways to improve developer experience. If you like it, be sure to checkout the white paper we published on the topic, which includes a starter set of survey questions.
https://www.youtube.com/watch?v=tD5KXh36Svg&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=4 Overly ambitious aspirations often fail. Scale back your digital transformation dreams to starts small, learn, grow, repeat. Transcript 06 - Big Bang Releases The sixth reason why changing, how you do software at large organizations usually fails: doing way too much at once, the big bang release. Oftentimes, when you're changing, how you do software at a large organization, you wanna have a big successful release. You've got a lot to change hundreds, if not thousands of teams, and you're investing a lot of time and money and attention from a corporate perspective.
https://www.youtube.com/watch?v=eMyeHiUzH3E&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=4 Don’t have real CI/CD in place? Check out the Tanzu Application Platform. Transcript 05 - No CI/CD 14 reasons why your digital transformation strategy probably will go poorly: the fifth reason. You probably don't have true continuous integration and continuous deployment in place. What this means is that you're not only automating the way that you build your software, that you test your software, that you even make the images or the package of the software to be deployed continuous integration.
https://www.youtube.com/watch?v=9x069fTpdi0&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=5 Platform Engineering, platform as a product, and so forth. If you’re standing up kubernetes or any cloud stuff for developers, you probably need to change how you think about operations in general. Shift from service delivery to product management. Read more about setting up a platform engineering team. Transcript 14 reasons why your digital transformation initiatives to get better at software may be slowing down. Number four. Often what you do when you're fixing up how you do software in a large organization you're putting a platform in place.
https://www.youtube.com/watch?v=qr1w4Dp5tSA&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=6 Figure out where to get started with a developer toil audit. Transcript 14 reasons why your digital transformation is stalling in a large organization: number three. If you're looking to improve the way that you do your custom software in a large organization, you likely have a huge amount of what people call tech debt or legacy software. These are the systems you're currently using that have brought you all the success and revenue that you have, and now they're too old and they really can't be changed.
https://www.youtube.com/watch?v=FIN2lVklWlc&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=7 Read more in my free book. Transcript 02 - Security 14 reasons digital ,transformation fails in large organizations: number two security. There's many things your security staff is gonna wanna do when it comes to making sure the software you build and run is secure. One, they're gonna need to build up a risk profile to understand the new technology you're using the deployment frequency, all the types of risks that can occur.
https://www.youtube.com/watch?v=b8s9E3LNe_k&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=8 Read more in my free book. Transcript 14 reasons why it's hard to change the way you do software in large organizations, number one. Compliance basically means that you're following legal and self-imposed policy and guidelines: the ways that you're doing things and not doing things. Governance. A compliance person can't come in and check every single hour of something that's happening. So your software developers and product managers and operations people have to document that they've followed the rules.
[embed]https://www.youtube.com/watch?v=6VrpE992O68&list=PLAdzTan_eSPRNuA52_34wh5VTBC-0Rz7U&index=9[/embed] Transcript One of the things executives often forget when they’re transforming, how the organization does software is to transform how they do their job. What I’ve found is they tend to sometimes have the same sort of meetings and they don’t really change the way that they think about how they’re empowering their staff to be more mindful of being involved and having responsibility with their products. The other thing to pay attention to is making sure you’re actually transforming the way your organization is formed.