TL;DR: Patience and Persistence. Start with the smallest possible thing.
First: Good luck on what will be a long, and rewarding journey!
In the case of both DevOps and agile, you're talking about significant cultural changes in your organisation. The first expectation you should set for yourself is that it will be a slow, arduous and very incremental road. Don't expect to be DevOps super heroes over a weekend, unrealistic expectation will make you sad :(.
I come from a position of significant bias on this (the organisation I work for is very well known for facilitating exactly the change you're looking for), but it can be very helpful to engage experienced, external parties to help your organisation make the right moves on what is a very long and foggy journey. Not a sales pitch, I promise ;).
In general, you're going to want to start with the smallest thing. In the case of agile, it's very common for organisations and teams to just start with holding regular retrospectives. Once a fortnight or so, to look at what's helping and hurting them. From these retrospectives you may discover things like "we don't know who's working on what at any given time", "it takes us too long to decide on what to build", "it takes too long for us to release new features once devs are finished with them". These are all actionable issues that can be remedied with a variety of practices.
I guess the key here is: Don't just do what a book/podcast/resource says to do. Do the things that you demonstrably need to do based on data you collect from within your organisation. That's what it's all about. See an issue or a change, and respond to it. Implementing solutions for problems that don't exist yet is a fools game.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
TL;DR: Patience and Persistence. Start with the smallest possible thing.
First: Good luck on what will be a long, and rewarding journey!
In the case of both DevOps and agile, you're talking about significant cultural changes in your organisation. The first expectation you should set for yourself is that it will be a slow, arduous and very incremental road. Don't expect to be DevOps super heroes over a weekend, unrealistic expectation will make you sad :(.
I come from a position of significant bias on this (the organisation I work for is very well known for facilitating exactly the change you're looking for), but it can be very helpful to engage experienced, external parties to help your organisation make the right moves on what is a very long and foggy journey. Not a sales pitch, I promise ;).
In general, you're going to want to start with the smallest thing. In the case of agile, it's very common for organisations and teams to just start with holding regular retrospectives. Once a fortnight or so, to look at what's helping and hurting them. From these retrospectives you may discover things like "we don't know who's working on what at any given time", "it takes us too long to decide on what to build", "it takes too long for us to release new features once devs are finished with them". These are all actionable issues that can be remedied with a variety of practices.
I guess the key here is: Don't just do what a book/podcast/resource says to do. Do the things that you demonstrably need to do based on data you collect from within your organisation. That's what it's all about. See an issue or a change, and respond to it. Implementing solutions for problems that don't exist yet is a fools game.