Delivery
Deployment and support
Launch is the closing of a release, not a hopeful upload. IncogX deploys with a rollback, watches the system, and hands over enough that the client team is not stranded on the following Monday.
In brief, then in detail
- A release you can undo. The path to production is automated. The path back is known before the window starts. A release note says what changed for users and operators.
- Monitoring before traffic. Errors, latency, and the business event that matters are visible. An alert that nobody owns is not an alert.
- Handover. Runbooks, access, known limits, and the person to call. Knowledge that lives only in a chat thread is not a handover.
- Warranty, then a choice. 30 to 90 days of fixes for defects in the agreed scope. After that, a retainer or a new engagement. Support is not an infinite unspoken promise.
How it is run
Closing a release includes lessons, not only a party. What the forecast got wrong, which risk arrived, and what the next initiative should not repeat. Intellectual property transfers on full payment, as agreed. If a fix is a new feature wearing a defect’s clothes, it is estimated as change, and the sponsor can see the difference.
Warranty30–90 days on agreed scope
ReleaseAutomated, with a rollback
AfterRetainer or a new engagement
Launch checklist
- Release notes
- Rollback
- Monitoring
- Runbooks
- Access handover
- Lessons learned
Terms, in plain language
- Release. A deliberate move of done work into the environment users depend on, with a window, an owner, and a way back.
- Hypercare. The short period after go-live when the team watches closely and fixes defects fast. It has an end date.
- Runbook. The steps an operator follows for a known situation: deploy, restore, rotate a secret, or call someone.
- Lessons learned. What to repeat and what to stop. Written while the release is fresh, and short enough that the next team will read it.