Pairing in SDC

[Poonam-raj]

Not to be confused with the ticket for mob programming

Which module(s) and week(s) does this change affect?
Module(s): All modules in SDC for at least one sprint

What is the work that needs to be done?
Enforce pair programming as a backlog item for at least one sprint per module.
This would work much the same as ITP pairing backlog items

• Create a issue in at least one sprint per module (if multiple sprints exist I reckon the middle of a sprint could be a good landing point so any issues can be caught, if 4 or more sprints exist in a module add this into two sprints). Ensure the issue has linked into the backlog on the curriculum.

Why is this work important to do?
Pairing enables students to have a dedicated place to check in with their progress and understanding. It also gives us a chance to see if anyone is having some serious problems we haven't spotted. Pairing is also a continuous skill and we see SDC students often drop it when they leave ITP.

Additional context
This was originally discussed as a dayplan slot to engage students further but the mob programming might cover this and the logistics of a class of students pairing didn't make sense.