Skip to main content

Where have I been?

I have been away for a while for a few reasons.  One reason, I forgot I even had this blog. :)  I was shocked to see I actually got some comments on some early post.  Thanks, to those who did comment.

Another reason is that I went from software development into operations again.  I could say that I was too busy fighting fires to keep up this blog and practice.  If I am honest and I look back that would not be true.  I could have taken this blog to another level while I was in ops, if I could have seen the bigger picture.

As I got more and more frustrated with the operations team lack of improvement and more frustrated with how development treated operations, I realized this process was just broken.  I really had no solutions.   I would tell operations to just take their beating and we can figure it out later.  Ops kept pushing back on Dev.  Dev stayed longer and longer on projects.  Dev struggled with the turn around on ops deployments and requests.  Ops struggle with transitions.  Ops struggled with dev going around ops to get things done.  How can this work?  Honestly it works only because the client has low expectations and doesn't really know it could be better.

Then, just in a random passing I heard about something called "DevOps".   (Wish I had heard about this years back but that was not my path to this passion)

This blog is going to be my thoughts and information as I stop focusing on Development or Operations and focus on DevOps.

Comments

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.  

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/

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...