Posts

DOES 2015

#DOES 2015 was great.  The speakers did a excellent job of talking about more than DevOps but how they are growing their DevOps through their company.  Capital One was awesome.  They showed a video of their internal engineering conference.  Disney brought a great message of embedding DevOps across their organization with a Star Wars theme.  They were actually a late add to the schedule and rocked it.  The PowerShell guy brought a great message of never giving up and timing for culture changing ideas at Microsoft.  Netflix had another great culture talk.  I really think they may be the best DevOps culture in IT. It is just inspiring to see how large enterprises are spreading DevOps across their IT.  They all have similar stories. 1.  They started with a small team or group. 2. They got senior leadership buy in. 3. They focused on the people.  They had summits, internal DevOps days, Dojos, training and what ever it takes to sprea...

Why DevOps is not a team.

I really want people to stop talking about DevOps but I really want people to keep asking questions about DevOps.   This does not make sense right? The problem is DevOps is getting a bad name in lots of places because people don't understand it.  DevOps is not CI, CD, Infra as Code, Cloud, Agile, Lean.....  DevOps is a culture of continuous improvement and scalable IT. We really should talk about DevOps from a leadership level and talk about automation separately.  Leaders need to remove obstacles, manual tasks, and improve processes all while demonstrating people and teams working together.  These things will naturally allow people to innovate and grow towards automation. You can do automation anywhere and you should do automation.  A company could be a large enterprise with silos of people that don't trust each other with competing goals but even those can do automation like CI and Chef.  They likely are doing it at a silo level and everyone do...

Polarizing DevOps - Work in the business or work on the business

Traditional IT is failing in the enterprise because people are asked to do too much and they can't scale.  Why does a DevOps culture want small full stack teams that are highly collaborative, because it can scale and succeeds.  If you need to do more, you optimize with automation, become more efficient, you adjust scope or you add more resources where it makes sense for the business need. Silos do not scale.  On the surface you think it does and many IT leaders believe it does but scaling does not happen when you have competing goals and deliverable.  You just react to everything and mostly fail in one way or many.  The team misses deadlines, create issues, or have unhappy employees who are just waiting to move to a DevOps culture. DevOps cultures should be polarized.  You either enable people to do the job or you are part of the team.  You will fail if you are in the middle.  If you work in a silo that tries to be technical, business and proj...

Lean Culture Change

We all know culture is a huge part of DevOps.  What we don't know is how to change it.  The easy answer is change culture just like you would "eat an elephant",  one bite at a time.  What this does not tell you is where it start.  Do you start with the thigh, leg, tail or even the head?  This is where you should look at culture change just like any other lean process improvement.  Here are some examples: Focus on the value to the customer This will help you sale why DevOps is important to the company.  There are plenty of information and statistics of how DevOps is changing the industry.  Do your research and be prepared when a decision is made that is anti-DevOps.  Try to right the ship and stir it a little closer to DevOps.  Keep iterating through these opportunities over time. Respect and Engage People Culture change and job change is scary.  You will meet people who hate you.  You have to be a leader that c...

You still have not read Phoenix Project

I started at a new company and the people that I interviewed with had read the Phoenix Project.  That was exciting and I could relate to their goals.  After a few weeks of working there it was clear, they were the only ones that had read it.  You should already see the red flags going off about what I got myself into. I have made presentations to everyone from senior leaders to individual contributors.  The last slide in every presentation is a picture of the Phoenix Project and Web Operations.  I will talk about Web Operations in the future.  Every time I get to this slide, I see people just hang their heads. (Maybe it is just because I present badly)  Some of the people have heard how good it is but just have not made it a priority to read. I told my team it is mandatory to read it and I think any IT company should make it mandatory.  I bought 4 copies this week on Amazon to bring to work and start farming them out.  If you want to star...

DevOps Enterprise Culture Thoughts

How do you get DevOps going in an Enterprise?  The same way you eat an elephant but you have to keep reminding your self of two things: 1.  I am hungry. 2.  I may never finish eating. You are hungry or you would not be eating.  DevOps passion is something you have to be starving to embark on.  If you don't really want to own the message, the transformation or believe in it, just stop and do little things as you can.   If you want to own it and you know you know the org will not change, even a little, then leave.  The market is too good for people that want to do DevOps to sit and starve with an Org that is dying. The DevOps journey is never ending and you have to keep reminding yourself of that.  You will have plenty of people that get in your way. Tools will sometimes crush your spirit.  Process will sometimes seem crazy.  You just have to remember, you may never finish evangelizing DevOps.   I can't stress enough, if you ...

Should you leave your current company?

I recently left my company and it definitely made me think about when is it time to move on.  Here are some of my thoughts: Make sure your personal life is ready for it.  Don't just see dollar signs or a new shiny object.  Look at how it will impact you, your family, friends, your social circles and your everyday life.  You would be surprised how much you depend on your coworkers as friends and way of getting through the grind when it is going tough. I recommend leaving if you are going through several months of being unsatisfied.  If you are not growing as much as you are giving to the company, it might be time to move on.  You should be a leader and that means innovating and growing people and processes.  If you are at a point where the company can't grow like your passion pushes you, then there is nothing you can do.  This is especially important around DevOps.   Don't leave just for money.  Unless someone is going to double you...