we help organisations be ready to use, support and operate what their projects have just delivered. eight areas. one lifecycle. before go-live.
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. the cost of resolving an issue is significantly higher once the service is in full use.
geelen & company 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.
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 we look at on every engagement — sized to risk, rolled into your delivery cadence.
size the operating cost before signing the build.
choices carry past go-live; the second year is the test.
the support model: written, agreed, rehearsed.
runbooks, training, and named owners — written down.
SLAs and sourcing clauses, written for the ops team.
incident, change, problem — and who runs each.
separation of duties beats one heroic admin.
cutover is the only chapter the audience reads.
writing about the practice — what works, what tends to be misunderstood, and the occasional rant about ITIL in a devops world. the legacy archive lives on at opsasto.blog.
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.