DevOps is never done "right"

-

 This article is a good summary of things to consider on your DevOps journey.  We should just be careful to say what is right or wrong for any organization.  

13 Clues to good devops


Comments

Post a Comment

Popular posts from this blog

Manage IT by Johanna Rothman

-
I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/
Read more

How AI is Transforming DevSecOps: A New Era of Secure, Agile Software Delivery

-
 As software delivery accelerates and attack surfaces grow, traditional DevSecOps practices are being pushed to their limits. The integration of artificial intelligence (AI) into DevSecOps workflows is not just a trend—it’s a strategic imperative. AI is driving a seismic shift in how we manage code quality, automate security, respond to threats, and enable secure innovation at scale. In this post, we’ll explore the key ways AI is improving DevSecOps and why forward-thinking organizations are embedding it deeply into their pipelines. 1. Proactive Threat Detection and Response In modern CI/CD pipelines, code moves fast—sometimes too fast for human eyes to catch every vulnerability or misconfiguration. AI helps shift security left and right by: Analyzing code and dependencies with natural language processing and ML to detect hidden vulnerabilities, insecure APIs, or anomalous changes during commits. Real-time anomaly detection in production environments using AI-powered o...
Read more

Matrix Organizations are bad for Software Dev

-
Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...
Read more