How do you keep Devs, QAs and Testers constantly busy?I understand where this question comes from. But it's the wrong question.
This question came up in a recent LinkedIn thread:
“How do you keep Developers constantly working, QAs and testers constantly testing, without impeding each teams work progress?”
I understand where this question comes from. But it’s the wrong question.
No, it’s worse than that. The question isn’t even in about the right problem in the first place.
Our goal is not to keep our Devs, QAs and Testers busy. Our goal is to solve problems for customers.
What if fully utilizing your Devs, QAs and Testers isn’t the best way to solve problems for customers? What if the best way to solve problems for customers is to do less work sometimes? What if sending the Testers home for a day is the best way to serve customers? What if a 3-hour lunch break is the best way for Devs to solve customer problems?
Maybe you think those are silly examples. Maybe they are. But at least now you’re thinking about the right question. Think about your customers. Not your utilization.
Why do devs want more devs?
Almost always, more team mates means slower output, not faster. So what's the proper solution?