Project delivery

Governed like a PMP program, delivered like an Agile team, run on ITIL.

A migration or a new fabric is both a project and a service change. We run the project with PMP-aligned governance, deliver it in Agile sprints and waves, and operate it under ITIL 4 practices integrated with your ITSM — so your PMO, your change board and your operations team each see the artefacts they expect.

Frameworks we align to

PMP · PMBOK

Governance and accountability

Every program has a charter, a named accountable lead, a scope baseline per wave, a risk register and a RAID log reviewed weekly. Change to scope goes through a documented change request with cost and schedule impact before it is accepted.

Charter, stakeholder map and communication plan at kickoff
Scope, schedule and cost baselines per wave; earned-value tracking on programs over one quarter
Risk register with owners and triggers; issues escalated within one business day
Formal acceptance criteria and sign-off at every wave and at handover

Agile · Scrum / Kanban

Delivery in waves and sprints

Design and automation work runs in two-week sprints with a visible board; migrations run in waves that are planned, rehearsed on the twin and reviewed in a retrospective before the next wave starts.

Backlog in your tooling or ours, visible to your team
Sprint review every two weeks with working configuration, not slides
Definition of done includes twin validation and documentation
Retrospective after every wave; lessons change the next method of procedure

ITIL 4

Change, incident and problem practices

Our change-enablement practice maps to ITIL 4: standard, normal and emergency changes with risk-based approval, every change rehearsed and recorded, and incidents handled with defined severities, escalation and post-incident reviews.

Change enablement: twin validation as the mandatory risk assessment; CAB attendance where you run one
Incident management: Sev-1 to Sev-4 definitions, 15-minute senior response on Sev-1, status every 30 minutes
Problem management: root-cause analysis and known-error records after any repeat incident
Service-level management: monthly report against agreed SLAs, continual-improvement register

ITSM

Integration with your service management

We work inside your ITSM, not beside it: changes, incidents and CIs are created and updated in ServiceNow, Jira Service Management or Freshservice through their APIs, with the twin results and configuration diffs attached.

Change and incident records opened from our pipeline into your ITSM
CMDB updates from the repository: devices, interfaces, software versions
Approvals follow your workflow; evidence is attached automatically
Reports and the live portal exported to your dashboards where needed

The stages and what each one hands you.

The same eight stages shown on every program, with the governance artefact each produces.

SpineRail · Program stagesSHT PD-02

011–2 weeks
Discovery
Inventory, dependencies, constraints and risk map collected from the running network. Output: inventory workbook and fixed program scope.
02report
Assessment
Current state measured against the target: capacity, resilience, security posture. Findings ranked by risk and effort.
03as code
Design
Target architecture, translation rules and bill of materials — written into the repository you will own.
04dry run
Twin validation
Candidate configuration applied to a digital twin: predicted state, routes and failures proven before any window is booked.
05waves
Build & migrate
Racks, cabling and cutovers in waves with parallel running; rollback tested and rarely used.
06every wave
Verification
Pre/post checks against baselines and application tests; the next wave starts only when this one is signed off.
07repository
Handover
As-builts, runbooks, test results and the repository transferred; your team trained on the pipeline.
08optional
Operations
Live health portal, 15-minute Sev-1 response, changes through the same twin-gated path.

Named output at every stage · acceptance before the next

Kickoff	Charter · stakeholder map · communication plan · RAID log
Design	Design basis · low-level design · BOM · twin baseline report
Planning	Wave plan · method of procedure per wave · rollback plan · change requests
Delivery	Sprint reviews · twin validation records · pre/post verification evidence
Handover	As-builts · runbooks · repository · acceptance sign-off · training record
Operations	Monthly SLA report · incident post-mortems · continual-improvement register

Who runs it

Accountable lead

A PMP- or PRINCE2-certified program lead for engagements over a quarter; a senior engineer leads shorter projects. One name owns schedule, scope, risk and communication.

Engineering team

Expert-certified engineers (JNCIE, CCIE, PCNSE) doing the design and the cutovers; the people who scope the work are the people who deliver it.

Your side

A sponsor, a change manager and the operations lead, named at kickoff, with a weekly 30-minute status call and a written report you can forward without editing.

Need a program your PMO will recognise?

Talk to a program lead

Governed like a PMP program, delivered like an Agile team, run on ITIL.

Frameworks we align to

Governance and accountability

Delivery in waves and sprints

Change, incident and problem practices

Integration with your service management

The stages and what each one hands you.

Discovery

Assessment

Design

Twin validation

Build & migrate

Verification

Handover

Operations

Who runs it

Accountable lead

Engineering team

Your side

Need a program your PMO will recognise?