Interim Program and Project Management

Interim programme management takes over the steering of a strategic IT initiative at the interface between business strategy, technology architecture and external partners. When internal capacity is missing or several service providers need to be coordinated, programme responsibility is taken over temporarily. The initiative is carried through its critical phase and handed over in an orderly way to internal succession. The goal is not lasting dependency but stable operations that hold without external interim leadership. Functional and entrepreneurial authority stays with the client.

Typical starting points

  • a digital transformation or an MES or ERP rollout in production: a prioritised programme backlog orders phases, milestones and acceptance criteria
  • a portal initiative between agency and ERP vendor: architecture alignment and stakeholder steering align departments, executive management and technology on a shared basis for decisions
  • an outsourcing setup in which no one is steering the service providers: a vendor governance framework leads providers functionally and measures deliveries against acceptance criteria

Outcomes

The programme gains clear steering, a value-ordered roadmap and an orderly handover to internal succession: the initiative is able to decide and deliver again. The concrete artefacts produced are:

  • a prioritised programme backlog with milestones
  • a vendor governance framework with measurable acceptance criteria
  • a handover dossier for internal leadership

Teams are stabilised, suppliers are led against measurable commitments, and once the work is complete the organisation no longer depends on external steering.

Scope of work

le dot sits between client and suppliers: it leads the service providers functionally, keeps progress transparent and hands over in an orderly way at the end.

sequenceDiagram
    accTitle: Interplay in interim programme management
    accDescr: le dot temporarily takes over programme responsibility from the client, leads the service providers with a quality gate, keeps progress transparent and hands over in an orderly way.
    participant A as Client
    participant L as le dot
    participant V as Service provider
    A->>L: programme responsibility (temporary)
    L->>V: functional leadership, quality gate
    V-->>L: delivery, code and architecture check
    L-->>A: transparent progress
    L->>A: orderly handover

Strategic programme steering (program governance) The IT portfolio is structured and prioritised by business value:

  • a resilient sequence with clear phases, milestones and acceptance criteria
  • secured resource allocation across multiple projects instead of parallel permanent construction sites

Vendor and partner governance External service providers, agencies and software suppliers are led functionally and measured against the agreed standards. le dot acts as a technical quality gate:

  • code and architecture checks as well as defined acceptance criteria before go-live
  • transparent progress, instead of getting lost between vendors

Architecture alignment and stakeholder steering The dialogue between departments, executive management and technology is moderated, and technological decisions are aligned with business goals. This brings client and implementers back into the same direction, and decisions are made on a shared basis of facts rather than in escalation mode.

Scope boundaries

This service takes over the ongoing leadership of a complex initiative. An already escalated, acutely endangered project is first stabilised by Project Rescue before an interim leadership takes over regular operations. The sustainable build-up of the delivery and quality capability of a healthy team is provided by Delivery Engineering. Where, instead of programme leadership, the fundamental decision to buy, build or which system is at stake, Make-or-Buy Consulting frames that question.

Key data

The effort depends on the capacity and duration of the mandate:

  • over how many months the role is filled
  • at what workload
  • at what altitude, from project steering to full programme responsibility

A bounded project at part-time capacity is clearly defined, while continuous programme responsibility across many stakeholders demands more. What the mandate costs in a concrete case depends on exactly these factors. The price range gives the frame for your own initiative.

Request pricing

Further information