Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add charter about using pairing/mobbing #119

Open
1 task
romaricpascal opened this issue Jan 6, 2025 · 0 comments
Open
1 task

Add charter about using pairing/mobbing #119

romaricpascal opened this issue Jan 6, 2025 · 0 comments

Comments

@romaricpascal
Copy link
Member

romaricpascal commented Jan 6, 2025

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

  • A page in the team docs describes our pairing/mobbing practices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant