We’re setting up a new team and decide to do full pair programming (8 hr straight with a little break except 1 hr lunch) for past 2 sprints (around month).
I feel exhausted and my mental health is going down so I would like to discuss solution with team but I didn’t have something good in my mind yet.
I saw other teams (in the company) use partial pair like 1 dev hold 1 ticket, works in pair for solution and test planning and testing, and works individually for implementation phase. But it might be the case that a dev is on leave and that ticket has to stop (which full pair programming supposed to solve this issue).
I also saw other people mentioned partial pair programming here (top comment) and there but they did not mentioned how to separate tickets effectively.
Question about partial pair:
- How many ticket should a pair hold at a time? (1 per pair or 1 per developer)
- If 1 ticket per pair, how not to mess up with version control in individual phase, we are fully remote.
- If 1 ticket per dev, how to defense this solution about the ticket has to stop when someone on leave
Thanks in advance!
Panida Wiriyachaiporn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.