Pairing should be a given. Even before you take into account the time spent fixing defects produced by lone wolfs, very few programmers (who don’t have too big an ego to do it) will fail to be twice as productive with a pair. Once you add the knowledge sharing and mix in a bit of time you are starting to get massive gains. Why? Because although we are smart, a single programmer can’t see both the wood and the trees.
Come say hello at...
No upcoming events
- @MrABriggs @cheltenhamgeeks Hi, it’s dormant atm I’m afraid. Not really sure when I’ll be able to resurrect, curren… twitter.com/i/web/status/1… 6 months ago
- Today’s bread came out with teeth! https://t.co/6MNnPfFJB9 7 months ago
- RT @teamrivertweets: Is sharing meaningful data the key to unlocking productivity in your business? Download our new report to find out >>… 9 months ago
- RT @teamrivertweets: This isn't just a continuous improvement tool. This is the only product that combines your business data with social c… 11 months ago
- RT @teamrivertweets: White Paper | Get our free white paper to learn how to unlock a culture of 'Innovation Everywhere'. @diaryofscrum expl… 11 months ago