3 ms·
Pivotal has nearly 100% of developer time spent pairing. This requires entire teams to be in sync on in/out and lunch schedules, else there will be non-pairing
by ohwaitnvm 10y ago
Pivotal has nearly 100% of developer time spent pairing. This requires entire teams to be in sync on in/out and lunch schedules, else there will be non-pairing time. That's not the end of the world, but most teams don't have code review, favoring the live review of paired development.
While at Pivotal, I did observe the rare team with an 8AM start instead of 9, but as far as I know everyone opted into being on an alternative schedule, and it was for out-of-time-zone client work to enable better communication with the client.