Separate planned engineering from operational support

List the work you expect: reproducible defects, dependency upgrades, small refactors, incident response, monitoring, or user support. These activities require different staffing and access. A provider completing a code backlog does not automatically own the deployed application's operation or respond to incidents outside the agreed engagement.

Illustrative scenario: a team needs three known export defects fixed and also expects someone to answer production alerts overnight. The defect work may be a bounded engineering scope. Alert response requires a separate operating arrangement with explicit coverage, escalation, access, and responsibilities for recovery decisions.

Prepare a maintenance backlog that can be accepted

For each planned item, include the affected workflow, reproduction or current constraint, acceptance condition, and relevant checks. Provide repository and CI status, supported environments, and an available domain owner. Group related issues only when they share a useful boundary and can be verified together.

Identify unknowns before committing to a duration. Missing build instructions, unsupported dependencies, and inaccessible integrations can dominate an apparently small repair. Qualify these conditions first rather than assuming that every maintenance request fits a fixed sprint merely because the ticket description is short.

Agree on ownership after delivery

Specify who reviews changes, deploys them, monitors the result, and owns remaining issues. Include handover notes and rollback considerations appropriate to the work. If a defect affects existing records, assign data reconciliation separately from the code patch so it does not disappear between teams.

A team can use Getzilla to plan, check and independently review changes from its existing backlog. The team still owns maintenance and release decisions. Ongoing operations, availability duties and response expectations need an explicit arrangement with the responsible provider; this page does not establish such an offer.

Working sheet

Clarify the maintenance engagement
NeedDefine before startingEngagement implication
Known bug repairReproduction and acceptance testPotential bounded backlog
Dependency upgradeCompatibility and integration accessDiscovery may be required
Incident responseCoverage and escalation ownershipSeparate support agreement
Production monitoringAlert routing and action authorityExplicit operating responsibility
HandoverMaintainer and release ownerRequired delivery transition
Download this worksheet (CSV)

Questions about define the software maintenance support you need

Does this page promise 24/7 Getzilla support?

No. The README describes a repository workflow and Trust CI access, not a continuous support service, an availability guarantee or a response commitment.

What makes a maintenance item sprint-ready?

A clear existing repository, reproducible issue or defined constraint, acceptance checks, available access, and a reviewer who can resolve domain questions.

How should I use the working sheet?

Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.

Sources and further reading

Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.

Make the next change verifiable.

Getzilla is an open source workflow for changes to existing repositories. Inspect the project, define acceptance checks, and keep independent review in the loop.

See the repository workflow See current access and pricing