What
Add a page in our team docs about our practices for collaborating to solve a problem on a synchronous call (pairing or mobbing), especially:
- different kinds of sessions we can do
- when to use them or not
- recommendations for structuring the sessions (length, breaks, things to provide ahead of time)
- reassurances about what happens in the sessions (it's OK if they feel slower, if you need to ask questions, if you have to drive but are not 100% sure about what to do...)
The page should probably live under 'How we work' as pairing/mobbing may happen across disciplines.
I can start with just a re-structuring of the points we discussed at dev catch-up and we can build upon those iteratively as we do more pairing/mobbing sessions.
Why
Pairing or mobbing can be a great way to work on a problem collaboratively. They're not suited to all situations and work better with a bit of a frame around them.
Following a discussion at Dev catch-up (internal link), we should document our preferences for this practice in the team docs.
Who needs to work on this
Developers ?
Who needs to review this
Anyone
Done when
What
Add a page in our team docs about our practices for collaborating to solve a problem on a synchronous call (pairing or mobbing), especially:
The page should probably live under 'How we work' as pairing/mobbing may happen across disciplines.
I can start with just a re-structuring of the points we discussed at dev catch-up and we can build upon those iteratively as we do more pairing/mobbing sessions.
Why
Pairing or mobbing can be a great way to work on a problem collaboratively. They're not suited to all situations and work better with a bit of a frame around them.
Following a discussion at Dev catch-up (internal link), we should document our preferences for this practice in the team docs.
Who needs to work on this
Developers ?
Who needs to review this
Anyone
Done when