Declaring an emergency

Watch

You will be able to

• Know what counts as an emergency
• Declare one from any product or team
• Know what happens to sprint work

Step by step

1. Recognise an emergency Product or team › Work
   A data breach, a data leak or a platform crash. Emergency demand trumps everything, including expedite.
2. Declare it Work › Declare an emergency
   Anyone can declare one. Say what has happened in a sentence; add what you know.
3. Sprint work pauses Team › Boards
   The sprint pauses at once and a red banner shows the emergency. Sprint work cannot move until it is resolved.
4. Respond, contain, resolve Emergency › Status
   Declared, Responding, Contained, Resolved. When it is resolved the sprint restarts, with the time lost added back.
5. Close after the review Emergency › Status › Closed
   Close it after the post-incident review, with what was learned recorded on the item.

Try it yourself

Practise as Nina Patel in the demo.
View as Nina Patel. Open EPR team Alpha and read the closed platform-crash emergency: when was Sprint 11 paused, and how much time did it get back?

Open the demo as Nina Patel Password pulse-demo-2026. The demo resets every night.

The examples use a made-up healthcare organisation. DelPulse is not only for healthcare: it can be set up for any industry, with your own names for every portfolio, programme, product and team.

Part of

Requesters · Viewers · Delivery team members · Product Managers and Product Owners · Service management