Generally, DevOps is awesome since it’s an end-to-end process, promotes cultural changes, and suggests tools for automaton. But, there are cases when it delivers less value or can be a pain to follow. Here are some of the examples when DevOps can be very challenging:
– If there won’t be frequent *releases/deployments*, then implementing DevOps can be more expensive than the value it would deliver.
– DevOps teams usually have the mentality “we build it, we run it”. If *deployments will be managed by a 3rd party* or a vendor then we are using Agile for development, but not the full DevOps.
– Organizations with *no leadership buy-in and lack of budget (time & money) for ensuring continuous learning*
– Some *heavily regulated organizations with strict compliance practices, audits (especially external)* and a heavy focus on documentation can find DevOps to be a burden.
– Some other factors which make DevOps more challenging or less feasible to implement are: *ITIL, silos, strict and lengthy change management process, lack of approval for using the appropriate DevOps oriented tools*