Regardless of how well your org might have adopted DevOps culture and practices, your dev teams are likely spending a majority of their time planning for creating new things, adding features to existing products, or "replatforming" to take advantage of contemporary approaches. All these activities are centered around the "as intended" state of your systems. Consequently, you get surprised and frustrated when things don’t go well in production. How do you balance between the "as intended" and "as it is" (production) states? What does the "as it is" has to offer? Why and how to turn production surprises into opportunities? Join this session to find answers.


Outline/Structure of the Talk


Learning Outcome

Learning from incidents

Target Audience

Developers, Technical leads and Architects

schedule Submitted 1 year ago