Oh neat, our team does this but we call it “WTF Wednesday.” Usually the most senior engineer digs back into our incident log and tries to reproduce it in our dev environment, and we live-solve with him playing the role of the customer.
It is the same thing. In our case it’s not attached to the seniority. The person ending their shifts replays its incident when there has been one, with the person who is taking the pager after them. We are deeper in the infrastructure so we don’t have customers but we roleplay stakeholders (lead/head, principals, developer). My favorite is the person who has experienced something wrong but it is only this person and bad luck :P
Yeah, I think the goal is to eventually make it irrespective of seniority, but right now he’s the only one with 15+ years of institutional knowledge on the application, so he’s trying to pass on as much as he can to reduce our bus factor.
Oh neat, our team does this but we call it “WTF Wednesday.” Usually the most senior engineer digs back into our incident log and tries to reproduce it in our dev environment, and we live-solve with him playing the role of the customer.
It is the same thing. In our case it’s not attached to the seniority. The person ending their shifts replays its incident when there has been one, with the person who is taking the pager after them. We are deeper in the infrastructure so we don’t have customers but we roleplay stakeholders (lead/head, principals, developer). My favorite is the person who has experienced something wrong but it is only this person and bad luck :P
Yeah, I think the goal is to eventually make it irrespective of seniority, but right now he’s the only one with 15+ years of institutional knowledge on the application, so he’s trying to pass on as much as he can to reduce our bus factor.