As a leader who is responsible for iterative delivery of technology products, you have probably been in a situation when all teams depend on a single DevOps engineer to push that next release or service pack to production.
Perhaps you have also experienced the impossible dilemma of allocating your two experienced data scientists between six projects? Knowing that each of these projects are of a similar priority and each competes for these engineers’ time and contribution. You have probably experienced the ‘Lose/Lose’ situation, knowing that four of the six projects could or will inevitably be delayed, putting an entire roadmap at risk.
Maybe coverage of automated tests remains well below your target, because Test Automation Engineer vacancy has still not been filled, after four months, to the frustration of developers and overload of the manual QA team?
Finally, maybe your knowledgeable and expensive senior developers are constantly diverted to resolve minor support issues, taking them away from delivering critical and strategic project work.