Our goal is to help individuals and teams become DevOps Masters.
Check out the news stories about DevOps we tweeted:
6 things to think about when you are writing your communications with other teams. We explain why it's just as important to explain why you are communicating as what you are doing. Remember a little time spent preparing a message can save you days, weeks or months of time trying to get everyone to understand.
Part of any successful campaign to win people over to doing things in a DevOps style usually requires some sort of promise of it being a better way. So how do you prove you are seeing benefits as you start to implement your plan? How do you quantify all the unlogged hours you put in doing things manually after you have just automated it. Sure you and maybe your boss will notice you have reduced your hours down to 80 hours a week, but what about the people at the top? The ones who ultimately need convinced to let you keep spending time on it?
That's right don't even attempt to do DevOps without Change/Incident Management. Not because you won't be successful in at least small ways. Not because people won't appreciate you automating your companies one hundred and fifty servers in five minutes instead of five days. But because you won't be able to prove any benefit of DevOps to Management. That means they won't appreciate it, value it, or the most important part FUND it......