Before we make changes
How we scope the initial work.
The first conversation helps us understand the context. Before changing the infrastructure, we agree the activities, checks and deliverables with the team, based on the environment involved.
- Starting information
- An overview of the architecture, the AWS or Azure environments involved, dependencies on on-premises systems, observed issues and planned changes.
- Scope to agree
- We decide whether to start with an architecture review, a landing zone, a service migration or an automation task. We agree which resources are involved, the activities, constraints and verification criteria.
- Deliverables to define
- We define what to document: the proposed architecture and technology decisions, the sequence of activities and the checks. Configurations and operating instructions cover only the agreed work.
- What is not included
- Migrating the entire environment and changing systems outside the agreed scope are not implied by the first conversation: additional activities and checks must be agreed before proceeding.