Much like in pair programming, working with a partner through pair writing provides increased support and valuable immediate feedback. But there are additional obstacles when you and your partner are not collocated. Here are some tips on how you can still implement pair writing successfully when you can't collaborate in person.
For many, pair programming delivers benefits such as increased focus, improved team relationships, and better code. Tom Breur and Michael Mahlberg found that pair writing can work, too, and the advantages bear a lot of resemblance to those of pair programming—more concentration, productive feedback, and better writing.
Sarah Johnson explains the role of writing in an agile world and how to educate your team members. Remember, agile takes into account that each situation is unique, and you need to determine what makes the most sense for your particular Scrum team.
Beth Romanik and Jonathan Vanian, who write and edit stories for Software Quality Engineering's websites and publications, present a bonus session for Better Software Conference East 2013 about writing about software. They describe how to contact a publisher, how to write better, how to edit better, some tips on crafting an engaging headline, and advice for getting people interested in your work.
Beth Romanik and Jonathan Vanian, Software Quality Engineering