Skip to content

Delivery management and governance

Know where the project stands, every week.

Good governance is not paperwork. It is how you know what is happening, why decisions were made, and what is coming next. Every Blacklight engagement has a named delivery lead, an agreed plan and regular demonstrations of working software. The arrangements scale with the work: a small change needs a light touch, a multi-system programme needs more.

What delivery management gives you

Each arrangement exists so you can make decisions with the facts in front of you.

Clear ownership

A named Blacklight delivery lead and a named owner on your side. Responsibilities for decisions, content, testing, data and sign-off are written down at the start.

Scope, priorities and acceptance

An agreed scope with priorities, so the most valuable work comes first. Acceptance criteria are set before work starts, so "finished" means the same thing to both sides.

Risks, assumptions, issues and dependencies

A shared log that both sides can see. Risks have owners and actions. Dependencies on your teams or other suppliers are named early, with dates.

Progress reporting and demonstrations

Regular progress updates in plain language, and demonstrations of working software at agreed points. You see real progress, not a percentage complete.

Budget visibility and change control

Effort and spend tracked against the plan. When something changes, you see the impact on cost, time and scope before you agree to it.

Architecture, security and data decisions

Significant technical decisions are recorded with the reason and the alternatives considered. Security and data-handling choices are agreed with your IT and information governance leads.

Testing, acceptance and release readiness

A test approach agreed early, user acceptance testing supported by the team, and a readiness check before each release. Go-live happens when the agreed criteria are met.

Escalation and operational handover

A known route for escalation on both sides. Before go-live, ownership, support arrangements and documentation are handed over so nothing falls between the project and business as usual.

Proportionate, not heavyweight

Not every engagement needs a programme board. A small enhancement may need a short scope note, a demonstration and a sign-off. A multi-department implementation needs a plan, a steering group, a risk log and formal acceptance. The level of governance is agreed with you at the start and reviewed as the work changes.

Governance supports good decisions. It does not, on its own, make a system compliant with regulation. Where regulatory requirements apply, they are captured as requirements and acceptance criteria, and your compliance owners stay part of the decision.

Evidence

Benoy: one portal, several delivery partners

  1. Problem

    Benoy's intranet had grown across 11 studios in five countries. Offices outside London kept their own copies of files because access was so slow.

  2. Delivery

    Blacklight designed and delivered a bespoke .NET portal, working alongside Oracle and Deloitte, who handled the accounts data integration.

  3. Result

    Synchronised, local-speed access to documents across all 11 studios, with one place for contacts, projects and internal communications.

See the full delivery journey

The ten stages from discovery to business as usual, with what you receive and what you decide at each one.

See how we deliver →

Frequently asked questions

Can Blacklight deliver one part of a larger programme?

Yes. Blacklight can take responsibility for the whole delivery or for a clearly defined part of it, such as the Dynamics 365 workstream or an integration, working with your own team and other suppliers. The boundaries and hand-offs are agreed at the start.

How do you handle changes to scope?

Changes are expected. Each one is described, its impact on cost, time and risk is assessed, and you decide whether to go ahead. Nothing is added to the budget without your agreement.

Do you work with our project methodology?

Yes. Blacklight can work within your organisation's project and change governance, or bring a lighter structure where none exists. What matters is that both sides use the same plan and the same definition of done.

Talk to us

Talk to us about the delivery, not only the technology.

Tell us what you need to deliver and the constraints around it. We will explain how we would run it and what we would need from you.

Get in contact