Home
Gerry 's Library tagged → View Popular
I Love Pair-Programming » Absolutely No Machete Juggling
"I see pairing work so well every day that I consider my career prior to my current job to have consisted mostly of wasting time. "
Digaboard
New open source digital whiteboard for Scrum/Kanban teams
How to Pair Program
Guideline Summary:
Share everything. All contributions, whether great results and errors, are “ours”, not “yours” or “mine”.
Play fair. One person “drives” (has control of the keyboard or is recording design ideas) while the other is continuously reviewing the work and planning ahead. Stay fairly close to 50-50 on driving. Let the less experienced partner start and maybe drive a little more.
Don’t hit your partner. But make sure your partner stays focused and on-task.
Put things back where they belong. Put negative judgments in the trash: Be positive about you and your partner. For both, this is an opportunity to improve.
Clean up your mess. >Watch over the shoulder and you are really likely to find a large number of your errors!
Don’t take things too seriously. If your partner picks out a bunch of errors as you type, be glad. But do not always agree. Have healthy disagreement/debate. Finding the fine balance takes adjustment.
Say you’re sorry when you hurt somebody while moving furniture. Sit side-by-side and program, simultaneously viewing the computer screen and sharing the keyboard and mouse. Slide the keyboard -- don't move the chairs.
Wash your hands of skepticism before you start. Being skeptical can be a self-fulfilling prophesy. Buying in and “jelling” can lead to a whole that is greater than the sum of the parts.
Flush. If you work on some parts independently either discard them (flush) and start over together or have the partner very carefully review the work with you.
Warm cookies and cold milk are good for you. Periodically, taking a break is important for maintaining the stamina for another round of productive pair programming.
Be aware of the power of two brains. Experiences show that, together, a pair will come up with more than twice as many possible solutions than the two would have working alone. They will then proceed to more quickly narrow in on the “best” solution and will implement it more quickly and with better quality.
The Heart of Scrum « Agile Anarchy
Tobias offers a passionate, inspiring take on the task board being the heart of Scrum.
SpringerLink - Journal Article
Case study of 4 teams @ MSoft and IBM. Documents reduction in defects, increase in initial development time
YouTube - Introduction to Pair Programming, version 2
Profesionally produced vid aimed at students on dos and don'ts of pair programming. A bit cheesy, but useful content.
Selected Tags
Related Tags
Sponsored Links
Top Contributors
-
Lean SW Quality
Links and notes related to ...
Items: 55 | Visits: 39
Created by: juha riissanen
-
Agile
Agile Programming and Process
Items: 12 | Visits: 43
Created by: Lakshminarayanan Venugopal
-
IT Management Conference & Expo in NYC Oct.14-16
http://www.manageit.me ---T...
Items: 2 | Visits: 42
Created by: Jackie Fields
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo