LEARN. PRACTICE. GROW.Concept and mechanism
A Delivery Manager helps create conditions for a team to deliver outcomes predictably and adaptively. The role works on impediments, dependencies, communication, planning, and improvement of working practices. Agree the actual mandate with the organization: the title does not automatically grant authority over product priorities, architecture, or risk acceptance. Public British and Scottish government references illustrate collaboration with Product Managers and Service Owners but do not define a bank’s internal rules. Start by understanding the intended outcome, participants, required decisions, and boundaries within which the team can act autonomously.
Guided application
In a fictional scenario, a funds application needs an infrastructure migration without interrupting daily processing. Product participants define the business outcome; engineers assess options; APS clarifies operating conditions. The Delivery Manager makes visible who depends on whom, which decision is pending, and when it is needed. Facilitate discussion with the right people instead of indefinitely relaying messages between groups. Explain trade-offs in understandable language, confirm understanding, and record the decision. A useful question in an international meeting is: “Who can resolve this dependency, and by when do we need the decision?” The answer should produce ownership and a next step rather than merely another status meeting.
A dependency needs an owner, a required outcome, and a decision date.
Common pitfalls
Title treated as universal authority; permanent message relaying; meetings without decisions; implicit priorities.
Related topics: Planning, capacity, and forecasting · Flow, dependencies, and impediments · Governance, risks, and decisions
Support autonomy and connect people, decisions, and outcomes.
Reference: Delivery Manager · Service Manual current public guidance; Kanban Guide May2025; DORA five-metric model; primary references reviewed 2026-09-30