In my last few posts I wrote about my experience in a DevOps role. It was not something to write home about, but it could definitely produce a few good diary entries, if that’s your sort of thing.
DevOps sounds like a great idea, just like Agile and NoSQL. There is no one thing that fits perfectly, if at all. That being said, they are great tools that are effective when used properly, just like any other tool. I’d like to list a few things that I think should be part of a defined DevOps job. I also don’t think DevOps should be a role on its own, which I’ll dive into after the list.
That’s right, there is no list. I love the idea that there should be someone that handles both development and operations tasks, but in reality it just causes knowledge to be stuck in the few people. I believe that this blog post describes it best - it’s not just simply described, but it’s also not totally the wild west. To paraphrase the article, DevOps can be thought of as an extension to Agile. That is to say we should be considering operational issues as part of a sprint, so that we allocate time to the team to update servers, script things that need scripting, and update infrastructure if it needs to be done. Most importantly is that these tasks must be taken on as a team.
As with anything I’m sure there will be people that disagree with these points, so whatever works for you and your team is the best choice. Having a dedicated DevOps person was not the best choice for my particular project but it might be for yours.
No comments:
Post a Comment