DevOps uses a capability model, not a maturity model • Hacker News Board

Re: DevOps uses a capability model, not a maturity model

#111

Post by KingOfCoders » Sat, Apr 08, 2023, 12:07 PM UTC

seidoger wrote: post #89

mjr00 wrote: post #44

Earlier quoted context omitted.

> DevOps as a movement died when it started being used as a job title. In my experience, it quickly stopped being a philosophy for Dev and Ops teams to work on working better together and just because a new name for System Administrator. The "DevOps" job title can arguably just be a sysadmin, but I do think the main ideals of the movement are just so tightly ingrained in software now that we don't even notice. It's e…

> It's easy to forget that 10-15 years ago, the most common dev/ops model was "toss it over the fence" 15 years ago it was often still I without the C, integration that wasn't continuous. Code freeze 1 month before release, put all the bits of code together, everything breaks, try to fix it.

And with the bad (compared to Git) merging capabilities of SVN, last minute merges of feature branches (hurray branchless!) for a release cadidtate to hand over to QA were a nightmare.

Re: DevOps uses a capability model, not a maturity model

#112

Post by stevefenton » Tue, Apr 11, 2023, 7:15 AM UTC

benjaminwootton wrote: post #98

getoffmyyawn wrote: post #42

DevOps as a movement died when it started being used as a job title. In my experience, it quickly stopped being a philosophy for Dev and Ops teams to work on working better together and just because a new name for System Administrator. Before the popularity of the term "DevOps" it was always true that any System Administrator worth hiring knew how to script for automation (the job title for people who didn't was Syst…

What do you call the people who: - Use Terraform to build infrastructure as code - Get involve in containerising applications - Run and operate Kubernetes - Spend a lot of time on CI/CD - Improve the development experience - Implement service discovery - Build and run developer platforms - (To a lesser extent) Build and run cloud environments including Serverless components This seems like a new set of responsibiliti…

You may like Platform Engineering even more as there's a lot of crossover with what you mention. A key difference from your list is that you enable teams to build and run their own applications, so they remain responsible throughout. You would provide a simpler way for them to do it, so they could self-serve.

Re: DevOps uses a capability model, not a maturity model

#113

Post by stevefenton » Tue, Apr 11, 2023, 7:17 AM UTC

ussrlongbow wrote: post #85

Chico75 wrote: post #40

Earlier quoted context omitted.

I would encourage you to read the book "Accelerate" which was at the source of the DORA metrics, as it clearly advocate for a capability model, not a maturity one.

Do you have book ISBN? Thanks!

Accelerate: The science of Lean Software and DevOps

Nicole Forsgren, PhD, Jez Humble, Gene Kim

IT Revolution

ISBN 978-1-942788-33-1

Re: DevOps uses a capability model, not a maturity model

#114

Post by stevefenton » Tue, Apr 11, 2023, 7:24 AM UTC

pictur wrote: post #59

Working with the logic that the author talks about can cause terrible situations for large companies. If you create a culture based on trying new things in companies that are in constant business development, you must create a culture that will take responsibility for it. otherwise, you'll have environments where answers to "hey why isn't this working" questions can't be found.

It's fair to say that culture eats everything else alive. It's also the hardest thing to change. I've worked in a few places where we felt helpless to impact the culture and creating a culture-bubble (i.e. to the extent of the technical teams, but no further) didn't help impact business outcomes, even where it made our lives a better. Maybe that was enough to make the culture-bubble worthwhile.

Re: DevOps uses a capability model, not a maturity model

#115

Post by stevefenton » Tue, Apr 11, 2023, 7:26 AM UTC

tra3 wrote: post #82

opentokix wrote: post #33

DORA Metrics is not a good place to start. This blog post is sales pitchf or whatever they are selling.

Curious to hear your thoughts. What's a good place? I'd argue that if your releases take forever, or lead times are huge they are worth improving first. What would you look at first?

I'd start with small batches. Quite a lot of the benefits come out of just doing fewer things between each release.