
WPS MANAGEMENT GMBH
CTO at WPS MANAGEMENT // wescale
Chief Technology Officer
Relevance
Why this case matters
This framing makes the decision signal explicit: impact, proof, fit, and AI / delivery relevance for hiring or collaboration.
System impact
Strengthened a delivery system across 15 teams, scaled 100+ developers remotely, and replaced activity metrics with flow-based execution.
AI / delivery relevance
Established delivery rules, golden paths, and guardrails for a large-scale engineering system under real operational pressure.
Proof
15 teams
led cross-functionally
100+ devs
scaled remotely
~70%
faster deployments
Especially relevant for
- Hiring
- Head of Engineering
- CTO-level
- Fractional transformation
Case context
Overview
WPS MANAGEMENT needed remote product development at 100+ developer scale to stay steerable without adding another coordination layer. I led 15 cross-functional Scrum teams with FaST Agile, flow signals (cycle time, lead time), and cloud-native architecture on GCP/Azure.
The work shifted attention from output steering to better delivery frequency, higher team autonomy, and clearer golden paths. The important part is not the framework. It is that product development can stay steerable even in large remote scaling.
Responsibility
Activities
- Remote leadership of 15 Scrum teams with 100+ developers without adding another coordination layer
- FaST Agile implementation: flow signals, team autonomy, golden paths
- Cloud-native transformation (GCP/Azure): Kubernetes, CI/CD, infrastructure-as-code
- Microservices architecture: Spring Boot, Docker, Kubernetes, service mesh
- DevOps culture: "You build it, you run it", automated testing, monitoring
- Product thinking: Outcome-focused development, user value measurement
- Team enablement: shared ownership and cross-functional collaboration
Operating mode
Methodology
- FaST Agile: flow signals, team autonomy, outcome focus
- Scrum: Cross-functional teams, sprint planning, retrospectives
- DevOps: Continuous integration/deployment, infrastructure-as-code
- Product thinking: User value, impact measurement, iterative development
- Team enablement: shared ownership and golden paths
Technical context
Technology stack
The tools are not the point by themselves. What matters is which system layers had to work together.
Backend
7Frontend
3DevOps
11Data & AI
3Tools
4Next step
If you want to explore similar leverage for hiring, collaboration, or a concrete transformation, this is the right starting point.
Send a short note about the situation you are trying to assess. I reply personally and will be direct about fit.