Risk Registers Testers Will Actually Update

Risk registers fail when they become compliance theater. In ISTQB-Inspired Strategy Bootcamp we cap active risks at twelve per release train and require an owner plus expiry. If nobody touches a row for two cycles, it drops — harsh, but it keeps the document alive. We tie each risk to a test idea, not a thousand cases. That linkage helps product partners see why you want time for data setup or environment parity. The article walks through a sample register for a fictional payments change, with honest scoring that admits unknowns. Finally, we discuss retrospectives: registers should feed back into training backlog. If the same risk appears thrice, it is curricular, not personal failure.