Describe the system and business constraint
Prepare an inventory of applications, runtimes, data stores, integrations, and current owners. Explain the problem driving the work: unsupported technology, slow changes, recurring incidents, or a business capability the system cannot support. Avoid asking a provider to modernize everything without a measurable target.
Attach evidence such as a blocked runtime upgrade, a reproducible build failure, or a diagram of a tightly coupled workflow. Identify constraints on downtime, data movement, and access. These details help distinguish a bounded engineering task from a migration program that needs sustained coordination across teams.
Separate sprint-sized work from a wider program
A focused task might update one supported dependency path, isolate one module, or add checks around a fragile interface. It needs repository access, a defined acceptance condition, and available product ownership. Feasibility depends on the actual code and environment; calendar duration alone cannot establish it.
A full platform replacement, enterprise data migration, or ongoing operating commitment requires separate planning and expertise. Do not interpret a small cleanup engagement as a promise to deliver those outcomes. Qualify unknown dependencies and responsibilities before committing to a fixed delivery period.
Agree on evidence and handover
Specify deliverables in terms of reviewed changes and checks: an upgrade branch that builds, a tested adapter, or documented rollback steps. Assign decisions about data correctness, production release, and domain behavior to named roles. Unclear acceptance criteria make even a small engagement difficult to evaluate.
To use Getzilla for repository work, start with the README installation and the read-only project plan. The team still owns its backlog, review decisions and release conditions. Any separately contracted engagement needs its own agreed migrations, access requirements and operating responsibilities; using the workflow does not create that contract.
Working sheet
| Request | Qualification question | Scope implication |
|---|---|---|
| Dependency update | Can relevant integration checks run? | Potential bounded backlog item |
| Module isolation | Is behavior documented and testable? | Potential focused refactoring |
| Database replacement | Who owns migration and reconciliation? | Separate migration program assessment |
| Enterprise transformation | How many systems and teams depend on it? | Broader program and governance |
| Ongoing operation | What response and availability duties apply? | Separate support arrangement |
Questions about qualify the scope of legacy modernization work
Does Getzilla offer a complete modernization program here?
No. The README describes the open source Getzilla workflow and paid Trust CI access for private repositories. It does not establish an enterprise modernization service or a fixed-duration engineering engagement.
What should a modernization brief include?
Include the system inventory, business problem, dependencies, access constraints, acceptance checks, and ownership of rollout and data migration.
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.
