Morgan Dutemple
All expertise areas

Delivery management: scope, decide, deliver

Across more than 80 clients and roughly 200 projects, redesigns, business tools and digital strategies, my role is to be the bridge between the client's vision and the team's execution. I speak developers' language, I can read a specification, a DNS record or a performance report: that is what lets me decide fast and deliver without nasty surprises.

Why project management still matters, even with good tools

Most digital projects that go off track are not short of tools. Jira, Notion, Confluence: most teams already have them. What is missing is arbitration: who decides when two priorities clash, who documents why a choice was made, who is accountable when a milestone slips.

Scoping concentrates most of the risk: an incomplete specification costs little to fix before development, and a lot after. Prioritising by real impact rather than perceived urgency, documenting every trade-off, and building SEO, accessibility and AI into scoping rather than leaving them as late fixes: these are the levers that reduce risk, not another tracking tool.

My method

Across roughly 200 projects, I have seen the same drift whenever scoping skips a step: the problem does not surface straight away, it surfaces three weeks before delivery. Here is how I avoid it.

  1. Scope

    Workshops, functional and technical specifications, a brief checked before any development.

  2. Prioritise and plan

    A backlog sorted by impact, a realistic workload and calendar.

  3. Manage risks and decide

    Risks written down, business and technical decisions documented, steering committees that actually decide.

  4. Deliver and hand over

    Acceptance testing, go-live, handover to run and user support through to adoption.

In a web agency: working prototypes to write the specification

On a web project run in an agency, I used AI to produce working prototypes rather than static mock-ups, and to help write the functional specification. Decisions were made on a journey people could actually use, not on a picture.

The specification then started from that prototype: AI suggested a first breakdown into business rules and edge cases, which I reviewed and completed before handing it to the developers. Scoping gains what it most often lacks: questions asked before development, not during it.

Frequently asked questions

What is delivery management?

Delivery management covers the end-to-end operational management of a digital project or programme: requirements scoping, backlog prioritisation, coordination of technical and business teams, risk management and reporting. The delivery manager is the bridge between the client's strategic vision and the concrete execution of teams.

Project Manager, Scrum Master, Delivery Manager: what's the difference?

These titles often cover the same scope depending on the organisation. The Project Manager handles planning, budget and coordination. The Scrum Master facilitates an agile framework at team level. The Delivery Manager covers both: agile or waterfall, arbitration between stakeholders, end-to-end delivery. In practice, I fill all three, and I understand the technology they manage.

Why is project management a job in its own right?

Because most drift comes from decisions not taken, not from a lack of technical skill. Keeping the pace, getting the right person to decide at the right time and keeping a record of every choice takes a dedicated role, especially when several projects share the same teams.