Cloud & platform
Google Cloud Platform (GCP) readiness, landing zone, migration, Google Kubernetes Engine (GKE)/Cloud Run, data platform, Financial Operations (FinOps) baseline.
Phase 2: Assessment & Scoping
Phase goal: Produce sufficient technical understanding for scope, delivery phases, estimates, and risks—without locking implementation detail that should be proven in sprint.
Prerequisites
Section titled “Prerequisites”- Non-Disclosure Agreement (NDA) signed (if applicable)
- Read-only access: architecture diagrams, application inventory, Identity and Access Management (IAM)/network policy, Software Development Life Cycle (SDLC) tooling
- Workshops with platform, application, security, and finance (Financial Operations (FinOps)) teams as topics require
Main activities
Section titled “Main activities”Application & integration
Domain model, Application Programming Interface (API), ERP/payment/market data, non-functional requirements (NFR).
Development, Security, and Operations (DevSecOps) & security
Existing pipelines, Snyk/GitLab/GitHub, Cloud-Native Application Protection Platform (CNAPP) posture (Wiz), audit controls.
FinTech (if relevant)
Latency, Disaster Recovery (DR), institutional onboarding, control evidence for counterparties.
- Architecture workshop — current vs target state, dependencies, migration waves.
- Gap analysis — against Google Cloud Platform (GCP) best practice and client internal policy.
- Phase backlog — high-level waves/sprints with outcome per phase.
- Risk register — technical, operational, regulatory; mitigation and owners.
- Draft Statement of Work (SOW) input — deliverables, assumptions, out-of-scope, high-level acceptance criteria.
Phase 2 deliverables
Section titled “Phase 2 deliverables”| Deliverable | Contents |
|---|---|
| Assessment report | Findings, recommendations, priorities |
| Initial architecture decision records (Architecture Decision Record (ADR)) | Major decisions requiring approval |
| Scope & phase plan | Phases 0–n with outcomes and dependencies |
| Effort & timeline estimate | Range with explicit assumptions |
| Responsible, Accountable, Consulted, Informed (RACI) draft | See Roles & responsibilities |
Artifact details: Artifacts catalog.
Exit criteria
Section titled “Exit criteria”- Client sponsor approves architecture direction and delivery phases (formal sign-off or email)
- Critical risks have mitigation or documented acceptance
- Input for commercial proposal (Phase 3) is complete
Typical duration
Section titled “Typical duration”2–6 weeks depending on scope (single workload vs multi-team program).
Previous: Phase 1: Discovery · Next: Phase 3: Commercial