Skip to main content

We have always done DevOps, right?

I was talking to some people from old dev teams.  We did unit testing and CI way back in 2005.  We did deployment packages and did iterative development.  We did DevOps right?


Comparing what we did back then to some of the solutions these same guys deliver today, Hell Yea we did DevOps. 


So how do you do fundamental DevOps back then and not do it today?  It is because things like ITIL, SILOs and separations of concerns made you lose your mind.  All these same guys have gone from architects to managers and they have to worry about audits and best practices.


We really lost track of what made our teams great back then.  One bad incident leads to a PMR saying dev can't touch prod.  Then, management started creating silos which made everyone lose sight of the goals that DevOps emphasizes.  Customer Happiness.


Let's really get back to the original question, did we do DevOps.  Not really.  We had large deployments.  We did not automate acceptance testing.  We did not do push button deployments.  We never had deployments without impacting customers.  It probably took a couple days to get code to customers, at best.  We were way ahead of our time but we never went far enough.   Once we separated dev from support, we got further away. 


With all that said, these teams back then were a great foundation for me and I was blessed to work on these teams.



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