I would not do it all the time, but I imagine one benefit could be that the whole team is on one page, when it comes to a central complex part of the application's logic.
Everybody is invested as everybody had (probably) their say and was part of the decision. Institutional knowledge is high across the whole team.
This for the cost of single threading the team. It is a business call and might be a valuable and valid approach in some cases.
I think it is a tool. A tool with a specific problem it solves. And if you use it all the time you are the worker that only has a hammer so that every problem looks like a nail (not you personally, but generally speaking).
Being a data analyst I remember great sessions of pair and team analysis of a specific data problem. Some sucked and were unproductive but most were great if facilitated well.
Everybody is invested as everybody had (probably) their say and was part of the decision. Institutional knowledge is high across the whole team.
This for the cost of single threading the team. It is a business call and might be a valuable and valid approach in some cases.
I think it is a tool. A tool with a specific problem it solves. And if you use it all the time you are the worker that only has a hammer so that every problem looks like a nail (not you personally, but generally speaking).
Being a data analyst I remember great sessions of pair and team analysis of a specific data problem. Some sucked and were unproductive but most were great if facilitated well.