Security findings and delivery performance
Fix security findings on time, accept a risk properly when you must, and measure delivery honestly. Video ready
Watch
That is the last video in this track
Well doneYou will be able to
- Read security findings and their fix-by dates
- Follow a finding to its defect on the backlog
- Accept a risk with a reason and an end date
- Read the four DORA measures
Step by step
- Security findings Pipeline › Security findings
Fix by: critical 7 days, high 30, medium 90, low 180. Critical and high become defects. - The gate Pipeline › The gate to live
Open critical findings, and high ones past their date, stop a deployment to live. - Accept a risk Security findings › Accept the risk
Product Manager, Service Owner, SRO, Technical Lead or Solution Architect; a reason and an end date; recorded as a decision. - Delivery performance Pipeline › Delivery performance
Deployments a week, lead time, change failure and time to restore. Mark a deployment as failed if it caused a problem in live.
Try it yourself
Practise as Priya Shah in the demo.
Open the Pipeline tab for the Portal team. What is stopping a deployment to live?
Open the demo as Priya Shah 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.