Agile Release Management By @Plutora | @DevOpsSummit [#DevOps]

Over on the other side of the fence IT ops are screaming at the various portfolio dev teams for releasing highly risky functionality way too frequently but since the Agile dev adoption production has only had a couple of low priority P4 incidents caused by bad code releases. Things must be looking good with the new dev process but then a few months down the track BAM a P1 incident the Monday morning after a agile delivered release is deployed. Highly important business functionality is broken in one of the downstream systems. It's all hands to the pump and both IT dev and IT Ops team are getting frustrated with each other trying to resolve the incident holding back blame on which side of the fence caused the incident. A few hours later all fixed and the communication goes out to the business that prod incident is resolved.

read more