Make sure there are no single responsibilities in your team, if you do this a person leaving shouldn't cause any issue. To give you an example, in our team we try and make sure that everybody touches most parts of the system, so there is always someone with the needed knowledge available. When we introduced a dev-ops role within our team it was only to learn the knowledge, after that everything this person started doing for dev ops was paired with another developer and after a while others were pairing with each other. So eventually the only responsibility left is to make sure things happen, not doing them. This makes planning holidays a lot easier as well :)
Make sure there are no single responsibilities in your team, if you do this a person leaving shouldn't cause any issue. To give you an example, in our team we try and make sure that everybody touches most parts of the system, so there is always someone with the needed knowledge available. When we introduced a dev-ops role within our team it was only to learn the knowledge, after that everything this person started doing for dev ops was paired with another developer and after a while others were pairing with each other. So eventually the only responsibility left is to make sure things happen, not doing them. This makes planning holidays a lot easier as well :)
Sadly. No enough resource. ><
The biggest challenge is time. Sharing require time. But we often have another task.
Maybe the leaders need to find a balance.
Don't underestimate the productivity of pair programming. People in duo advances faster than alone.
You can test it yourself first.
Maybe I should find a chance to test it.
Could you tell me what is pair programming in detail?
I mean this:
"Knowledge is constantly shared between pair programmers..."