When transformation stalls, don't blame your process. Look for strengths and weaknesses in these key areas
"When the Agile Manifesto was signed, software mostly shipped in shrinkwrap. Deployment rarely needed to be solved - it usually involved a single machine with an approved maintenance window. In many cases, operational best practice mostly meant restarting misbehaving machines or processes, which often solved the problem.
Now we've reached a point where perpetual availability is a near necessity, and we take for granted that services will always be available. The practices that provide that reliability evolved with incredible pressure to deliver faster, at greater scale, with zero service disruption..."
Read More ...