gfxhome.ws

What comes to mind when you think about incident postmortems in the tech space? If you picture a catastrophic incident, a scramble to pinpoint the root cause, and some sort of fix, you're not alone; this was an established way of dealing with security crises for years. But since the buildup of small, unresolved problems-both in your code and with your team-can end up causing bigger issues than any one showstopper, this manner of investigation isn't productive. In this course, Ernest Mueller shows how to approach incident investigations the DevOps way, explaining how to conduct a formal, blameless postmortem. Discover how to clearly communicate an incident's scope, pinpoint the proper corrective actions, continuously improve your resiliency using incremental retrospectives, and more.
Topics include:
Resilience engineering
Communicating the scope and impact of an incident
Determining which incident metrics are helpful
Facilitating the postmortem meeting
Leading a group postmortem analysis
Controlling cognitive bias
Identifying contributing factors
Determining corrective actions
How incremental retrospectives complement postmortems
More Info

https://www.lynda.com/Developer-tutorials/DevOps-Foundations-Effective-Postmortems/2818124-2.html

Site BBcode/HTML Code:

Direct link:
Forum BBcode:
HTML Code: