Forced pair programming is an antipattern. It's a recipe for burning your best workers.
You had better hope that the oft-touted knowledge transfer benefits of pairing are real, because you are going to have to deal with the turnover.
You had better hope that the oft-touted knowledge transfer benefits of pairing are real, because you are going to have to deal with the turnover.
I won't say I totally disagree, but what are your reasons for thinking this?