Enjoying this segment? Subscribe to our Youtube channel and follow us on LinkedIn to be the first to gain access to all our content, including free training videos just like this one: [ Ссылка ]

Trying to get started in DevOps but don't know how? Maybe this can help: [ Ссылка ]

Want even more support? Schedule a FREE consultation with Zohara and learn how to revamp your resume: [ Ссылка ]

-----

Transcript:

Are you tired of your development team missing their goals and delivery deadlines?
Do you struggle to increase speed without compromising the security of your system?
Is your company wasting resources fixing defects that could have been avoided?

-----

I'm Bob Aiello, a coffee addict, a world renowned CM/ALM/DevOps author, architect, trainer, and coach. My daughter wants me to say that I received an IEEE Standards Medallion for leading the effort to write the IEEE industry standard for DevOps, after envisioning the need to take a more disciplined approach than what has become unfortunately all-too-common. I help organizations like yours implement best practices, so that they can speed up their software delivery pipeline, while staying safe.
In this video, I guide you through establishing lean IT controls so that you can accelerate your systems and applications delivery, saving your company time and money.

-----

Race car drivers aren’t the only ones who like to go fast, so it’s not surprising that people so frequently ask me how to shorten their application delivery pipeline. Here’s what I have to say on the matter:
When I am in the trenches the three causes for delay that I most often see are poor communication, lack of collaboration, and cutting corners in order to make the deadline.
Teams frequently fail to share their technical knowledge with one another. Then, when they encounter a setback, rather than work towards a solution, many people focus on proving that they didn’t cause the problem. Haste often leads to unnecessary mistakes and technical debt. In other words, they rely on quick fixes, which inevitably require extra work later.
Fortunately, industry experts can walk you through how you can avoid those common missteps.

-----

The keys to success are making it compelling to communicate effectively, company culture to share knowledge, and expected that teams are held accountable for finding solutions, rather than excuses.

-----

Many technology professionals specialize in specific and complex technical areas from network engineering to database administration. They can be so focused on their comfort zone that they fail to share their knowledge with others. DevOps requires that the team not only share what they know, but use it to find complete solutions to setbacks. The increased communication not only ensures that the immediate problem is solved, but also inherently enables team members to learn from each other’s expertise. By focusing on both the process and the desired business outcome, DevOps turns what could have been technical debt into a high-performance cross-functional team.
The proof is in the pudding, so if you’re wondering if you and your team are communicating, collaborating, and keeping each other accountable enough or not, then a great first step is to assess your existing practices and compare them to industry best practices. Because mistakes are easy to make, industry experts have developed standards and frameworks to guide you on the journey to establishing secure and reliable code. Engineers who embrace these proven methods help their organizations achieve velocity, and when audited, they can show exactly how they did it.

-----

Thank you for listening to or watching Part 1 of our Delving into DevOps mini-series. When we come back we'll explore why DevSecOps is so controversial.

I’m Bob Aiello. For more content like this, you can find me on AielloConsulting.com.

свернуть