When a release train is getting ready to ship, every deployment request carries deployment request tasks tied to a specific playbook stage and runbook activity. This clip showcases how those tasks get structured, closed out, and mapped back to stages like assessment, move to test, and ready for deployment. In this clip, Robert Fedoruk, ReleaseOps PM walks us through a deployment request with three closed deployment request tasks, trace each one back to its playbook stage and runbook activity, and shows how a release manager can scan every deployment request across a release to spot what's blocking progress, and whether the blocker is a person or a machine. 0:00 - Release trains and deployment request tasks 0:25 - Example: three closed deployment request tasks 0:54 - Mapping runbook activity to playbook stage 1:30 - Deployment request status across the release 1:59 - Spotting human vs. machine blockers as a release manager 2:20 - Runbook task tied to a notify-stakeholders activity This is a highlight on how runbook tasks work inside deployment requests in ReleaseOps.