a practice in operational readiness

Opsasto.

noun | op · sas · to | operational readiness assurance & transition

We help organisations be ready to use, support and operate what their projects have just delivered. Eight areas. One lifecycle. Before go-live.

The Geelen dragon.
// areas
8 assurances
// origin
Shell, 13 years
// posture
before go-live
// methodology
opsasto — since 2016
01the practice

Look past the project’s ending.

A project does not generate value until it has delivered something that can be used. With an agile approach this point comes quicker; with waterfall, slower. Either way the project ends, and the service goes on.

An organisation that does not prepare for this operational phase can be found struggling with issues long after the introduction, and risks a diminished return on its investment.

Opsasto is a structured, risk-based, scalable approach for assuring the quality of an IT service and its operation — written down in eight chapters and rehearsed before the day the project hands over.

02the eight

Eight chapters, one lifecycle.

A project that ends well is one that prepared, from day one, for the day it would hand over. These are the eight assurance areas, sized to risk, rolled into your delivery cadence.

01
1
Budget
Price the running, not just the building.
02
2
Architecture
Design for the second year.
03
3
Support
Who picks up at three a.m.
04
4
Knowledge
What the tenth person needs.
05
5
Contracts
The fine print is the operating manual.
06
6
Process
Small, rehearsed, repeatable.
07
7
Security
Separation, quietly.
08 · Go-Live
8
Cutover
The day the project stops and the service begins.

Before the handover,
not after the incident.

Most engagements begin with a one-day readiness review — a structured walk-through of the eight, sized to your project’s risk, with a deliverable you can hand to your sponsor by Friday.

Begin a Review about Dimitri →