How do you handle fixed-deadline projects with Agile?

Fixed-deadline Agile requires managing the Iron Triangle trade-off (Scope/Quality/Time — fix two, the third is variable): (1) Fix time, flex scope — the Agile approach. Deadline is fixed; the team delivers the most valuable work within that time. Ruthless backlog prioritization ensures the must-haves are done first; nice-to-haves are deferred. Release the best possible product on the fixed date; (2) Release planning — create a release plan by dividing backlog by velocity. If 200 story points remain and velocity is 25/sprint, forecast 8 sprints. Regularly reforecast as velocity stabilizes; (3) MoSCoW prioritization — categorize requirements as Must Have, Should Have, Could Have, Won't Have. Guarantee Must Haves; be clear about what's in the Won't Have category; (4) Early de-risking — tackle risky, high-uncertainty stories first so scope adjustments can be made with maximum time available; (5) Scope negotiation — maintain ongoing conversations with stakeholders about scope vs. deadline tradeoffs. Never promise fixed scope AND fixed date — this is the root cause of Waterfall death marches; (6) Technical quality protection — never sacrifice quality (DoD) to meet deadlines; technical debt compounds interest and makes future sprints slower.