Software delivery & IT project governance
Get the project back to the truth, then deliver it.
Redback is a delivery consultancy for organisations running software and IT projects that matter. We help leaders see where a project really stands, put in governance that teams do not resent, and steer delivery to a release everyone can stand behind.
Field consultancy. We work alongside your teams, in your rhythm, not from a distance.
Signals we are usually called about
The status report is always amber. Nothing is quite failing, nothing is quite on track, and the dates move a fortnight every month.
The supplier and the client disagree on what “done” means. Acceptance has become a negotiation rather than a check.
Governance exists but does not govern. Boards meet, minutes are taken, and decisions still happen in corridors.
Releases are frightening. Each deployment needs a weekend, a war room and somebody's goodwill.
A new programme is about to start and leadership wants to avoid repeating the last one.
The practice
Delivery assurance
An independent view of a live project: plan, scope, team, supplier, technical approach and release process. We interview, read the artefacts, sit in ceremonies and look at the code pipeline.
You receive: a written assessment with evidence, a ranked list of risks, and specific actions with owners.
Project governance
Designing decision rights, reporting and stage gates that fit the size of the work. Lighter than a manual, firmer than goodwill.
You receive: a governance model on two pages, report templates, a RAID approach your team will actually maintain.
Project recovery
Hands-on leadership support for a project in trouble: re-baselining scope, resetting the plan, repairing supplier relationships and getting to a credible release.
You receive: a recovery plan within weeks, then steady presence until the project is stable.
Ten questions. Honest answers. A useful score.
Our delivery health check asks the questions we ask on day one of an assurance review: is there one accountable owner, can the team release on demand, does the plan carry contingency, is acceptance defined? It scores your answers privately in the browser and explains what each gap usually costs.
Governance that earns its meetings
Good governance is a set of decisions made at the right level, at the right time, with the right information. It is not a heavier status report. We look for the decisions a project actually needs — scope trade-offs, release go or no-go, supplier changes, budget release — and design the lightest structure that makes them happen on time.
For a modest internal project this may be a fortnightly thirty-minute review with a single page of evidence. For a multi-supplier programme it may mean formal stage gates, a design authority and change control. Either way, every meeting has a decision it exists to make.
If a board cannot say no to anything, it is an audience, not a board.

What we bring into the room
- Delivery practice across methods. Agile, staged and hybrid — we take the method you have and make it work rather than imposing a new one.
- Technical literacy. We can read a deployment pipeline, a test report and an architecture diagram, and ask the questions engineers respect.
- Commercial awareness. We understand statements of work, change requests and acceptance criteria, and how they shape behaviour.
- Plain writing. Every finding is written so that a director and a developer read the same meaning.
- Discretion. Assurance findings go to the person who commissioned them, and we agree in advance who else sees them.
Engagement shapes
| Format | Suits | Typical length | Output |
|---|---|---|---|
| Rapid review | A single question: is this project on track? | Two to three weeks | Assessment and top risks |
| Governance set-up | New project or programme about to start | Three to six weeks | Governance model, templates, first gate |
| Embedded assurance | Long projects needing a steady independent view | A few days each month | Monthly assurance note |
| Recovery lead | Projects in visible trouble | Agreed in phases | Recovery plan, then steady delivery |
Where our work stops
“Secure delivery” in our name means delivering software safely and predictably. We are not a certified cyber-security provider, do not carry out penetration testing, and do not issue security certifications. Where your project needs those services, we will help you specify and govern them with an accredited specialist.
We do not deliver goods or parcels. We do not act as your supplier's supplier, and we do not take a commission from vendors we recommend. Where a project depends on legal or regulatory interpretation, we work with your advisers rather than in their place.
A typical first month with us
Week one
A conversation with the sponsor to agree the question we are answering, who we will speak to, and who will see the findings. We request the plan, recent reports, the backlog or schedule, and any supplier agreements that shape the work.
Week two
Interviews with the delivery lead, technical lead, product owner, supplier representatives and a handful of users. We observe a planning session or release meeting, and look at how work actually flows from idea to production.
Week three
We test emerging findings privately with the sponsor so nothing arrives as a surprise. Then we write: evidence, risks ranked by consequence, and actions that name an owner and a date.
Week four
We present the findings, agree which actions to take, and decide together whether you need us further — for governance design, embedded assurance or hands-on recovery — or whether your team now has what it needs.
Who we work with
Our clients are the people who will be asked, eventually, why a project went the way it did: directors commissioning a new platform, heads of IT running several suppliers at once, programme sponsors in charities and public bodies, and founders whose growing product now needs more than a heroic lead developer. What they share is a need for an honest outside view from someone who understands both the technology and the organisation around it, and who will still be in the room when the advice becomes difficult to follow.
Questions clients ask first
Will you replace our project manager?
Rarely. Usually we strengthen the person already accountable — with evidence, structure and an independent voice — rather than take their seat. In recovery we may lead for a period, with a planned handback.
Can our supplier see your findings?
That is your decision, made before the work starts. Many clients share a version with suppliers because a common view of the facts helps recovery.
Do you work on site?
Where it helps, yes, by arrangement. Much of the work runs well through video calls and shared documents. Our registered address is not a client meeting location.
How do you charge?
Fixed fees for defined reviews; day rates for embedded and recovery work, with monthly caps agreed in advance.
From the field notes
Tell us what the project is supposed to do, and what it is actually doing.
We will reply within two working days with an initial view and whether a short review would help. No obligation, no sales sequence.
Talk to us