From request to outcome
“Move to cloud” describes a solution but does not explain the problem. Ask which capability is missing, what risk must be reduced, who uses the service, and how the outcome will be measured. Record what is outside the change as well. A useful mandate identifies the sponsor, service owner, expected benefits, constraints, and acceptance authority.
End-to-end scope
Break delivery into verifiable outcomes: approved architecture, environments, connectivity, identity, data, observability, recovery, documentation, and handover. Include retirement and obsolescence work when they are part of the objective. Define evidence and an acceptance owner for each outcome. “Server installed” is not “service ready”: an application may start while support access or demonstrated recovery is still missing.
Requirements that enable decisions
Separate functional needs from performance, availability, security, and operational requirements. Replace “fast” with an agreed measure, load, percentile, and observation window. Trace needs to requirements, tests, and approval. Example numbers are fictional; actual limits must be agreed with the business and the organization’s architecture authorities.
Workplace application
For a fictional fund service, create a table linking need, criterion, test, and acceptance owner. For processing before 07:00, include complete data, reconciliation, and external dependencies. Add retirement as a deliverable with identified retention and costs. When a new need emerges, assess its effect on scope and forecast before updating the commitment.
A fund valuation service must finish before 07:00 Lisbon time. Instead of writing “migrate five machines,” define the processing chain, representative volumes, dependencies, reconciliation, and evidence of completion before cutoff. Infrastructure is part of delivery, not the final acceptance criterion.
Common pitfalls
Accepting machines instead of the service; omitting retirement and retention.
Related topics: Plan effort, capacity, and forecasts · Address risk, obsolescence, and recovery
Scope should connect a business need to verifiable outcomes and an acceptance authority.
Reference: What is project management? · DR Technical Project Manager 2026.4; independent professional curriculum