We have updated our Privacy Policy and Privacy Options

Got It Button arrow

How to Staff Your Testing Program to Meet Your Velocity Goals


Say you’re getting some work done to your home—you wouldn’t want plumbers painting your walls, right? What about electricians doing your landscaping? Or HVAC technicians repairing your roof?

The same thing goes for your experimentation program.

When your budget is tight, it can be tempting to have members of your team take on multiple roles. For example, your analysts might be okay with managing the entire process of launching a test, developers could do full QA on their own tests, and project managers could oversee both test strategy and the tactical work required to execute tests.

But here’s why this is a bad idea: if you want something done right, you need to not only make sure you have the right people on the job, but also the right amount of people doing the work.

As you finalize your plans for 2019, we’ve put together a free guide to staffing your testing team according to the number of tests you want to launch per month. In it, we’ve analyzed over 4,500 hours of testing project data to help you know exactly how many people you need in each role according to the number of tests you want to launch each month.