Reminder: Day 2 is starting now – opening remarks and then plenary talks! Join the conversation in #ask-the-speaker-plenary.

lá maith @jpetoff moin @cleng great talk!

⭐ Excited to welcome @sanjeev.sharma and @john.comas who will be presenting, The Art of Platform Engineering ⭐

Watching @sanjeev.sharma and @john.comas

The statement about how it’s not self-service if you need to get a dozen approvals to do it rings so true!

Story of our lives… process trumps technology every day

Timely session @sanjeev.sharma, @john.comas - as most of the enterprises are figuring out Platform as Product , Platform Engineering. Thank you for sharing Truist work here, much appreciated.

Continuous Compliance - that's 2C's right there

Continuous, Continuous, Continuous, Continuous and... :drum_with_drumsticks: Continuous

Continuous Continuity

Could'a been IDTMC

Never silo your DBAs 🙂 (I always that it is the other way)

What are some resources to learn about implementing CD practices with database changes?

5 point DevOps STAR

DBAs! I love the Phoenix Project deployment story: “uh oh, we’re 1 hour into a 9 hour database migration, that should have taken 15 minutes!“” 😆

Standardization of Tools!!! I am fine with this as long as I have my tools in that list! 😃

@sanjeev.sharma - question- What functions covered in "Platform Engineering" and "Platform DevOps Automation" - did I miss that poinit?

Standardizing tools to about a 100 instead of a 1000... I'm game... but one toolset to rule them all is a perpetual modernization every 10 years... just like before DevOps.

@lbmkrishna Platform Engineering covers the whole stack, so to speak - the slide I showed earlier. DevOps Platform is the App delivery pipeline part of it

As we move from Dev to Ops, our tools narrow... - sounds like a 5-lane highway narrowing down to 2

@john.comas This is so fantastic — understanding the nature / consequences of changes.

@ganga.narayanan Or like the TVA pruning variants (sorry, Loki reference)

@john.comas This story about ecommerce order management system is one of the best I’ve ever heard!!! I LOVE THIS!! 😆

@john.comas LMAO

FREE STUFF

DevOps comes with Free Stuff!!!

OUCH!

@sanjeev.sharma - I will be keen to understanding more about the "GRC" part of it both - Platform Engineering and DevOps Platform Automation. What tools/automation put in place to satisfy those requirements?

Customer orders product; customer cancels orders; order cancellations get stuck in queue; orders fulfilled and sent to customer, but never charged for it. Very bad business model. HAHA! I LOVE IT, @john.comas!

Danger of slow feedback loops; wow, that should go into a future edition of Phoenix Project. We’ll call it the Comas disaster. 🙂 @john.comas

“Build the platforms not for the bank we’re now, but the bank we’re planning to be.” — @sanjeev.sharma

@lbmkrishna The GRC toolset is still immature - every tool has their own implementation of how to do GRC. We need to get to standardized policy-as-code

I love the TVA analogy! Pruning the timeline. 😂

it's good unless you are a Variant 😉

Amazing test automation at Truist @sanjeev.sharma @john.comas

I still see that Excel rules the GRC space - @sanjeev.sharma,I agree we need to get better

@rothdm Variants! 😆 this morning, I watched the presentation that @emoshmosh gave at GitLab conference last year — I think the birth of the amazing DevX story was initially due to a heavily modified GitLab instance, created by an enterprising dev team. 🙂

Excel and PowerPoint rule too many spaces 🙂

How large is the team building and supporting the platform itself?

We have to go to live dashboards over excel spreadsheets

@brianspo Still early stages of composing the individual services into a true platform

Thank you so much, @sanjeev.sharma and @john.comas – would you be willing to give us an update next year at DevOps Enterprise? As you said, it’s not every day that a top 10 bank appears out of nowhere!! 🙂 😆

Great presentation @sanjeev.sharma and @john.comas

Thanks for sharing. I really enjoyed see your platform journey.

Thanks @genek and @tapabrata.pal

More updates to come next year, Hint, hint @genek

✨ Get ready to hear from @jeremy.castle.lvh0 and @ryan.chambers.rse9 from State Farm, presenting Governance, Compliance, and Risk in the SDLC Can Be a Fun Event! ✨

Woot! Thank you, @sanjeev.sharma!!

@sanjeev.sharma Quite interesting, may not be able to provide you with this help, as having done it relartively ambrionic maner till now, but interested in connecting as normally at the begining of starting something similar

Great topic following GRC & SDLC cc - @sanjeev.sharma, @tapabrata.pal

Governance, Compliance, SDLC... this must be a fun talk

Thanks @sanjeev.sharma

Thanks @sanjeev.sharma for your presentation

Would love to connect @christian.lefevre - @sd_architect on Twitter or sanjeev.sharma(at)http://truist.com

Thank you @sanjeev.sharma @john.comas!  Loved the presentation! btw about #3 - I found it a combination of mandates + "build it and they will come" .. very relatable!

“the tons of technology here at State Farm” — 2900 technologists! — @jeremy.castle.lvh0 @ryan.chambers.rse9

Teams named "Delivery Experience" are very common these days. Love it

We've been fortunate to have State Farm invest in our area.

That’s great to see another team with Delivery in the name! We are Delivery Engineering here at Columbia. 🙂

One of my products in the suite is actually called Delivery Engineering too 🙂

They focus mainly on topics like GitOps these days

Yes! Automated Governance!

@jeremy.castle.lvh0 @ryan.chambers.rse9 if you get time please join today's bof on audit compliance

is that 25 clock hours or 25 working hours?

Clock hours

wow

This is really great stuff, @jeremy.castle.lvh0 and @ryan.chambers.rse9!

Thank you! We are excited to see what we can do with this framework next year and see how we can bring our InfoSec and Risk partners along to automate our governance.

@jeremy.castle.lvh0 - How large is the delivery excellence team and how does it measure in comparison to the size of the org you’re building these solutions for?

Good question. We are about 60 people (including leadership). We have about 7000 IT folks at State Farm. About 3000 of those are in developer/data/infrastructure roles.

We mainly support the 2000 developers.

Great talk - thank you!

Great presentation @jeremy.castle.lvh0 @ryan.chambers.rse9

Thanks @jeremy.castle.lvh0 and @ryan.chambers.rse9

Very informative! Excellent example for everyone!

Thank you @jeremy.castle.lvh0 and @ryan.chambers.rse9!

Great presentation! I'm curious to know how this framework helps with external audits of your release process? Does it make the audit smoother or is it hard explaining to auditors what's happening and how its addressing risk in the process?

@jtabron That's a really good question. We haven't moved into the mode for our Auditors to start using it. They have looked at our GitOps flow and have been very happy with how they can now look at a single flow to find all the steps in the approval for a change (Testing, Sign off, validation, etc.).

We still have some work to do to sell this to our Risk/Auditing folks

Thank you. In this framework, can a developer deploy code to production that wasn't tested or peer reviewed? You may have touched on this but I may have missed it.

They cannot. We have hard controls in place that stop that from happening. So there needs to be an sign off by a member of leadership before changes can be pushed into production. This framework will allow us to also verify the test artifacts and quality of the change in the future.

Nice! Thanks!

@jeremy.castle.lvh0 @ryan.chambers.rse9 do you think it would have been as feasible to do this if you were using something other than GitLab for your pipelines? e.g. tight integration between your version control system and your CI system, with approval capabilities baked in, etc?

I don't think so. We spent several years positioning out critical web platforms to only allow deployments using pipelines. This gave us an easy choke point to start firing off events. We had also started wrapping our developer tools in CLI's as well, so that became a natural event point as well.

😎 Back from the break, we welcome @jorge.castro,who will share: ENSUCKLOPEDIA OF DevUps - An improvised glossary to help us for understanding of What DevOps should not be or become!!! 😎

Always appreciate an IT Crowd reference

@jorge.castro is changing the presentation game. This is awesome.

Thank you for your kind words team : )

Sith ChatOps Analyst Love it ha ha

I do hope you enjoy the talk and have fun #continuousfun

CICDCF -- expanded pipeline.

"Shitty manual stuff" - @jorge.castro you are my hero

a superstar basically.

20 years EXP and all DevOps Certs, And PHD in DevOps and be personable..

"Ops losing responsibility" ha

This is hilarious and oddly helpful

seems like missing a section on Blame Shifting.... : ) it is not DevOps it is the old ways and the failure to adopt.... 🙂

Only problem is I can't tell what the actual advise is in between all the satire

Game Approach == like Squid Game - you lose you die...

Thank you!!

Thanks!

@jorge.castro great job.. made me happy

thank you for make us think on this !

i think it's important to look at all the counterpoints to these ways of working as well. This was insightful

I guess I am up next for Track 1...

I had not seen the periodic table of devops tools before. Interesting. https://digital.ai/periodic-table-of-devops-tools

Thank you all team, I do appreciate your words. At the end, something that I want to foster is about DevOps is about people also so besides CI CD CT CM and CStuff lets also practice Continuous Fun : )

@robert.printz new elements being discovered every day..

⭐ And now, we welcome our friend, @mr.denver.martin who will share: Tales From the DevOps Loop: 4 Teams Approach to 1 Common DevOps Framework ⭐

HI Everyone, Just one of my many Tales from Implementing DevOps at 3 different companies with different size team..

Thank you very much all. Hi team, I think I have some of your in my Linkedin but I would like to have you all so we can keep the learning and sharing experience after the event, I will be honored if you can add me https://www.linkedin.com/in/jorgeluiscastrotoribio/ Thank you and keep safe : )

You are going to rock @mr.denver.martin

@mr.denver.martin How big of an organization was this? Was this a small team as a part of a larger org inside of a larger org?

Company was 1K - 4K employees.

The Ops teams for Network and Platform were small compared to the other teams...

Apps Support was a lot larger, the Dev Teams were ever larger..

I am excited to hear about how you were able to change these command and control/task assignment leaders' approaches

Unfortunately, they were not able adopt new ways of working, they had to be encouraged to find a better fit outside the company...

I’m curious to know how security interfaced with these teams

InfoSec had been the Team of NO, but during this time they became partners and work to figure out how fix what we had and were involved later as partners at the beginning of new works... so it improved over time - due to Leaders asking them to join and they even attended BPMs later and gave great input.

I hope to make Tales from the DevOps Loop a series... so I can make a note to add InfoSec notes in a future talk...

that would be really cool

I am also open to partnering with other implementers to do talks with...

I can also provide the template from Team 4 for promoting the learning of new technologies and show the company was supporting their upskill.

Our team is looking for tips and tricks for running effective blameless post mortems. Any thoughts on what works to get people focused on the problem vs the people involved?

Thank you!!

Thanks for sharing your examples!

yeah, that was a major win for us,,, it was hard to keep it blameless, more than willing to share how we did that... I will also note to do a deeper dive in future Tale video...

📣 Shout out to our next speakers, @rajat.sud and @donalmeida2 here to present, Got Score? Scaling DevOps Adoption 📣

Thank you @mr.denver.martin A great example of real world adoption into a sceptical organisation. Certainly provides a blueprint for others to follow

My favorite topic

Hello everybody.. Rajat and I am here to support the Track 1 conversation

Excited to be here...

@donalmeida2 How many people work in your DevOps Center of Excellence?

10 Robert.

We're actually quite a lean team, supporting as many as 300+ engineers

Would the members of DevOps CE come from with in the company or were they hired from outside and a new net add?

I live for the day when DevOps is not Unicorn but a Thoroughbred herd.

Gamification. 👍 Were there any teams that had trust issues about it?

It could be good to give extra points if they share knowledge and help another team...

How did you collect the info?

Good approach to help get buy in...

Do you let them buy Company Swag with Points?

Do you think the scoring may de-incentivize teams without a competitive spirit or that may feel they aren't empowered to change?

Did the scoring / adoption approach yield observations on the capabilities offered/used themselves? For example, maybe gaps or impediments for specific technology platforms?

Wondering if you've thought about how this approach contrasts with recommendations in "Sooner, Safer, Happier" to not measure activity, or "how DevOps or Agile" are you, vs. basing paths based on context of each team and their impediments, and measured by outcomes?

yes. we had working sessions with the teams to improve their scores

@ryanewtaylor what if you approached it like a combined points approach like fundraisers where the combined teams points everyone wins something like 1/2 day off or something...

Thanks for presenting @rajat.sud and @donalmeida2

thank you

@rajat.sud thanks for sharing, i hay a few questions: 1) what has been the success of having an adoption score rating? 2) what kind of measurements do you for pipeline usage, capabilities, practices? 3) is this measurement is complementary to having a maturity level that focuses more On practices and tool usage? 4) can you Share with us the type of questionnaire you do to get these scores?

@eleonravinez thanks for the questions. Hope these responses shed more light 1. Scoring has been quite well-received. It provides an actionable piece of information that can be trended. 2. We have as many as 15 measurements right now - from build automation and stability, deployment automation and stability across environments, Securitization, Code Quality, test automation, etc. 3. The measurements when aggregated to the product or portfolio did facilitate questions about maturity - the tools usage was part of that - but the key is that it facilitated conversations about team practices 4. We graduated from questionnaires to automatically eliciting this data from the usage of our tools, and then applying applying some calculations (per our methodology) and updating in real time

Reminder: The plenary sessions are starting again in 5 minutes. Start making your way back to your browser and join us in #ask-the-speaker-plenary to interact live with the speakers and other attendees. https://devopsenterprise.slack.com/files/UATE4LJ94/F01D34MC2KS/image.png