Dr. DevOps or: How I Learned to Stop Worrying and Love ITIL
I read this post by Jon Hall today:
Some very good points here.
In my opinion both DevOps and Agile add to a decent service managment environment not detract from it.
Similarly sevice mangment adds to a decent DevOps/Agile environment.
There are plenty of percieved incompatibilities that definatly need to be thought out but more of the issues are the pre concieved notions of what ITSM or Agile are.
My personal pain points are:
In ITSM: CAB is not a uselfull entity if the whole change process is not clear and mature. It can act only to delay change rather than control it.
Once mature and proper process is well developed CAB can dramatically decrease the change of production issues while still allowing a high rate of change.
In gerneal I would recomend an iterative (dare I say it Agile) approach to creating a mature change control process.
In Agile: Agile and Devops is not an excuse not to plan properly. If the entirity of planning for a sprint is Jira cards that say "Impliment feature X" you will certianlly run into road blocks in an ITSM system and for good reason as this kind of minimal planning is far more likley to introduce issues into production.
If however the ITSM and Agile process is well aligend and a relitivly details plan is created in the sprint planning phase change control and other ITSM "Blockers" should be a non issue.
Thoughts and comments?
