Skip to main content

What's New in DevOps

It has been a while since I have posted on this blog.  There is a great reason why.  Life has gotten in the way and some job changes drew me away but not my heart.  I have been promoting devops and driving home the principles at a new company.  We are making great progress, moving to Scrum and automation of software.  With that said, we have a long way to go with culture, infrastructure and process optimization. 

Then, I recently went to a DevOpsDays and felt sad.  Our promoters have the DevOps message down for the Donkeys and Executives.   I feel like we aren't supporting the Horses that are trying to become Unicorns.   The ones that are trying to mature their Scrum practices at the enterprise level.  How about those that want to automate compliance but just can't afford another tool?  How do we prove DevOps and Scum works for our executives?  How do we do Enterprise DevOps metrics?  This are example questions but how do small companies act like Unicorns, with small budgets? 

Then I ask, "What is New in DevOps?"  Not enough is my answer.   

Comments

Post a Comment

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  
Post a Comment
Read more

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/
3 comments
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...
3 comments
Read more