| Pros | Cons | |
|---|---|---|
| Build a Slack Channel | easy setup
easy workflow no new tool to learn |
public feedback
difficult to get data out maybe not super enjoyable to use |
| Google Sheet Doc | easy setup, easy to learn | no one likes google sheet docs
no connected to main communication tool |
| Pre-exisiting slack bot github.com/techieshark/slack-pair | already built | customization? |
| git-duet | Records pairings in a commit | easy to forget to duet-commit, what happens when you squash commits? |
| physical stickers | Unicorn stickers!!! Hearts and Trucks!!! | Gross, on my monitor? |
| karma | we already use it | Doesn't track pairings |
| Pair Programming Matrix from Piv https://blog.pivotal.io/labs/labs/pair-programming-matrix | So super sweet | Dang you Pivotal Labs |
# Initiate the Pair
> /sw @emily
# this is sent to both people as a direct message...
@swifty > "You have been set as pairing with Piper/Emily. (if this is not correct you can type /sw oops to cancel, or /sw oops @someone to set your pair as someone different.
@swifty > Is there anything you would like to share with Piper/Emily, type /sw share @emily "my message"
> @emily feedback: You should read this article www.example.com
# when one person responds
@swifty > Emily has shared something with you. Once you've shared something with her you can have it.
Em's Workflow here
In the case of totally equal pairing: If two people do not report and two people always report, and Reporters report pairing with Non-Reporters, it will seem like pairing of two Reporters are hot spots and pairing of two Non-Reporters never happens, when that is not the case.
| R-Amy | ||||
|---|---|---|---|---|
| Reporter Amy | x | R-Sam | ||
| Reporter Sam | 3 | x | NR-Bill | |
| Non-Reporter Bill | 3 | 3 | x | NR-Jen |
| Non-Reporter Jen | 3 | 3 | 0 | x |