An incident response guideline documents how to assess, manage, communicate about, and recover from technical or nontechnical emergencies. section 10.3.3
A practical guideline should:
- Notify the lead developer and relevant stakeholders immediately. section 10.3.3
- Assess severity and scope, identify critical systems, and consider risks and available resources. section 10.3.3
- Assign responsibilities according to team members’ expertise and availability. section 10.3.3
- Document decisions and their rationale, then reassess the response as new information arrives. section 10.3.3
When an organization shuts down
A shutdown can create both practical and emotional disruption. Gathering resources, coordinating with the project manager, and helping the team finish essential work can provide stability during a nontechnical emergency. section 10.3.3
Use the emergency-plan example to visualize how response procedures and contacts can be organized. section 10.3.3



