Estimate the effort and team to containerise an application estate on cloud
For modernisation solutioning teams who need phase-wise activities, sizing rules and a resource pyramid for containerisation work.
- Engagement type
- Solo Pod
- Experts
- 1 lead · 1 consulted
- Hours
- ~30
- Duration
- 2 weeks
What the client needed
A firm needed the solution aspects of containerising applications to cloud: the scenarios in which an application is considered containerised, the phases and phase-wise activities, how small, medium and large containerisation efforts differ, and the general rules for effort estimation and the resource pyramid for the work.
The brief
The questions on the table
As the client wrote them, lightly shortened. Client and respondents are not named.
- Q1
In which scenarios is an application considered containerised on cloud, and what is out of scope?
- Q2
What are the phases and phase-wise activities of a containerisation?
- Q3
How do small, medium and large containerisations differ in characteristics?
- Q4
What are the effort-estimation rules and the typical resource pyramid?
The hours
What the work involved
- 01
Scenario definitions
Lift-and-shift into containers, refactor-to-containers and platform re-hosting on Kubernetes or OpenShift, with the characteristics that make an estate small, medium or large.
- 02
Phase model
Assessment, platform readiness, packaging, pipeline integration, testing and cutover, with activities per phase from the lead’s modernisation programmes.
- 03
Estimation rules
Effort per application by scenario and size, plus the platform and pipeline work shared across applications, with the pyramid used.
- 04
Cross-check
A cloud solution architect who ran OpenShift migrations at scale reviewed the rules.
- 05
Working session
With the client’s modernisation practice.
Deliverables
What the client received
- Scenario and size definitionsWith characteristics.
- Phase modelActivities per phase.
- Estimation rules and pyramidBy scenario and size.
- One working sessionWith notes.
The terms
What an engagement like this costs
You buy hours in blocks and can change the expert at the end of any block, at no extra cost. Longer projects run in stages: pause after a block, pick up the next stage when you are ready.
- Rate band
- $65–$250 /hr
- Senior specialists can be up to $500
- Hour blocks
- 1 · 2 · 5 · 10 · 20 · 50 · custom
- This engagement
- Solo Pod · ~30 hours · 2 weeks
More in IT services
Scoping a containerisation?
Describe what you needFor example: “We have 140 applications to containerise onto Kubernetes and need the effort rules and pyramid for the proposal.”
We aim to come back with matched experts within 24 to 72 hours.