Capacity Allocation for Platform, Data, and AI
Three directors each submit a reasonable plan, and all three depend on the same two engineers. How to count capacity by skill, order dependencies, staff, and reallocate.
-
-
Program Management Across Projects
Eleven projects reported green, yet the combined forecast missed a regulatory deadline. The recovery plan makes integration, decisions, and readiness visible.
-
Migration Strategy and Estate Assessment
The register mapped 203 systems to 299 hosts. Discovery found 340 hosts, including 41 unregistered ones; the initial migration plan had missed their dependencies.
-
Migration Wave
In a fictional hospital, the pharmacy system had few dependencies in the list. The nightly batch that read it was in neither the list nor the wave. The morning shift found out first.
-
Technology Roadmaps and Strategic Planning
A fictional insurer confused deadlines, promises, and forecasts. Its roadmap now shows obligations, uncertainty, trade-offs, and review responsibilities.
-
Software Bill of Materials
A parts list is not a verdict. Knowing a component is present is a different statement from knowing you are affected by a vulnerability in it.
-
Dependency Confusion
Your build asked for an internal package name. A public candidate met the selection rules and displaced the intended package.
-
Configuration Management Database (CMDB)
The estate changes through pipelines and cloud APIs. The database is updated by people and by scans. That gap is the whole problem.
-
Backlog Coupling
Backlog coupling links one team’s progress to another team’s queue. Reduce handoffs and measure waiting alongside the work and dependencies that remain.