Session
Minimum Viable Response Plan
with Jason Hand
A minimum viable product (MVP) allows you to obtain rapid feedback, and implement continuous and iterative improvements. When you put an MVP into production, however, you need to take the next step and make sure that you can respond effectively when problems inevitably arise. You need a minimum viable response plan. One that allows you to keep your MVP operational without burdening your team.
In this talk, we'll discuss the full lifecycle of an incident, what it means to be robust versus resilient when building a response plan. And we'll help you determine who is on-call when, and for which kinds of problems. We'll also talk about notifications, escalations, and how to enable learning from each problem your service encounters. This will give you the basis of a minimum viable response plan, so you and your team have a baseline to start and continuously improve up.
A minimum viable product (MVP) allows you to obtain rapid feedback, and implement continuous and iterative improvements. When you put an MVP into production, however, you need to take the next step and make sure that you can respond effectively when problems inevitably arise. You need a minimum viable response plan. One that allows you to keep your MVP operational without burdening your team.
In this talk, we'll discuss the full lifecycle of an incident, what it means to be robust versus resilient when building a response plan. And we'll help you determine who is on-call when, and for which kinds of problems. We'll also talk about notifications, escalations, and how to enable learning from each problem your service encounters. This will give you the basis of a minimum viable response plan, so you and your team have a baseline to start and continuously improve up.
Have feedback? Submit an issue here.