Webinar: Pairing – What and Why? Month, Year Time

1. Webinar: Pairing – What and Why?Month, YearTime Please note: The audio portion of this webinar is only accessible through the telephone dial-in number that you received in your registration confirmation email.

2. Arlo Belshee Founder Code Foundry a+caiwebinar@arlim.org • Michael Milutis • Director of Marketing • Computer Aid, Inc. (CAI) • Michael_milutis@compaid.com

3. About Arlo • Inspires courage. • Does both management and highly-technical coding. • Does both Agile and Plan-driven. • Believes in self-discipline, flexibility, change as the only constant, punctuated continuity, and people uberalles. • Challenges every assumption – continuously helps people learn to change. • Best recent compliment: Company Jester. Arlo always has permission to laugh at the King.

4. About Computer Aid, Inc. (CAI) • CAI is a global IT outsourcing firm currently managing active engagements with over 100 Fortune 1,000 companies and government agencies around the world. • CAI is a leader in IT Best Practices for legacy support and new development application management. • CAI’s focus is directed toward practical implementations that track and measure the right activities in software activity management • CAI consistently promises and delivers double digit productivity in its outsourcing and consulting engagements. • CAI makes all of this possible through the use of: • Standard processes • Management by metrics • SLA compliance management • Detailed cost, resource, and time tracking • Capacity management • Standard estimation • A unique, metrics based methodology along with a proprietary, real time data repository and management system (TRACER®).

5. NOW AVAILABLE! ONLINE WEBINAR RECORDINGS ANYTIME ACCESS! WWW. ITMPI.ORG / LIBRARY

6. PDU CREDITS FOR THIS WEBINAR • The Project Management Institute’s ISSIG group has accredited this webinar with PDUs • Stay tuned! Your PDU code will be displayed at the conclusion of this webinar.

7. Pairing – What and Why? What is Pairing? Why pair? Why does it work? Pairing in context. What do you do? What do you do as you get better? Advanced pairing.

8. What is Pairing?

9. What is Pairing? A discussion between two people that happens in parallel with, and comments on, performing a shared activity. • A change accelerator. • A development pace accelerator. • A learning accelerator. • A communications enhancer. • A way to build trust.

10. Is this Pairing? Yes No A programmer observing and commenting on another coder’s work while the code is being written. • A coder and a customer designing a UI together with paper prototyping. • A coder and a tester trying to track a bug symptom back to its cause, talking about experiments to run and hypothesis to date. • A coach helping an athlete position himself. There is no shared activity. The two programmers are involved in different activities.

11. Why Pair? • Measured results: • 10% defect rate. • 40% improvement in lead time. • 50% WIP inventory. • Reduced risk (many types). • This means about 80% of the features released per team-day, but at higher quality level and responsiveness. • Why? Beginner’s Mind. Pair Net.

12. What is Beginner’s Mind? Flow Beginner’s Mind Associative pattern-matching to create and learn new patterns. High variance, including failures. Requires lots of input. Hard. High mental effort. Feels scary! Requires modesty. Computers can’t do this. • Execute a fixed mental pattern. • No variance. • Fast and efficient. • Requires there be no inputs. • Sustainable. Low mental effort. • Feels good. • What computers do best.

13. What’s needed for Beginner’s Mind? • Understand the context. • Don’t understand the situation at hand. • Confidence. “I think I can learn this.” • Insufficient time or calmness to apply theory and reason. • The task must matter – it must be worth the energy it’ll take to learn and do it.

14. Pairing in Context

15. What to do – Beginning Pairing. Pairing Practice Other Practices Retrospectives. 1 week iterations, with full product release. 10 minute, asynchronous build. Basic TDD. One code base, project, and vision per team. Each person is on only one team. 0 bugs. No legacy code (defined as anything scary or hard to change). • 100% of the people pair, esp. including managers. • Managers pair 60-80% of their time. • Others pair 100% of their time. • Commit every hour. Roll back if reach 90 min. • Swap at least once per 24 hours. • No one stays with any feature through to its completion. Ever. • Everyone has equal power to change every piece of the system.

16. ++ Pairing • Management tasks become just “stuff the team has to do”. • Managers pair 100% of the time. • 2 minute, synchronous build with async backup build. • 20 minutes between commits. Roll back at 30 minutes. • Managers probably still have accountability to people outside the team, but they delegate not just tasks but full responsibilities. • Develop team captains. They know the ropes, keep an eye out, and flag an interrupt when they notice something. The team then resolves the interrupt. • Least qualified implementer. • Rotate pairs more often. • Rotate roles within each pair more often.

17. Promiscuous Pairing • All tasks are team owned. No individual accountability, ever. • Swap pairs every 90 min. Always boot the one who’s been there longest. • Least qualified implementer. • Everyone’s a team captain. • Work tiny: commit every 5 min on average. Roll back at 10 min. • Work tiny: finish a card every 2-4 commits. • 10 sec (or less), synchronous build with async backup build. • Should feel like you’re always going at an amazing pace. • Should feel like you are on task 7.5 hours per day (5 x 90 min). • Anyone should be able to take a vacation at any time, with no notice. • When they come back, they should feel hopelessly behind the new ideas – and feel caught up by lunchtime. • Should be able to fully ramp-up a new hire in 2-3 weeks (to 100% capability).

18. More Info • Belshee, Arlo. “Promiscuous Pairing – Embrace Inexperience”. Experience report, Agile 2005. http://svn.arlim.org/arlo_papers/Promiscuous%20pairing/Agile%202005. • Lacy, Mitch. “Adventures in Promiscuous Pairing: Seeking Beginner’s Mind.” Experience report, Agile 2006. • Friedlander, Wendy, et al. “Gentle Introduction to Pairing”. Agile 2007. • Shore, James and Warden, Shane. The Art of Agile Development. Published 2007. • Come to Agile 2009, where I’ll talk more on the subject.

19. Questions?

20. CAI Sponsors The IT Metrics Productivity Institute: Clearinghouse repository of best practices: WWW.ITMPI.ORG Weekly educational newsletter: WWW.ITMPI.ORG / SUBSCRIBE Weekly webinars hosted by industry leaders: WWW.ITMPI.ORG / WEBINARS ACCESS WEBINAR RECORDINGS ANYTIME AT WWW.ITMPI.ORG / LIBRARY 20

21. Software Best Practices Conferences Around the World 2009 Dates and Locations Mar. 10 Orlando, FL Mar. 19 Princeton, NJ Mar. 31 Albany, NY Apr. 9 Baton Rouge, LA Apr. 21 Detroit, MI Apr. 28 Tallahassee, FL May 5 New York, NY May 14 Tampa, FL May 19 Philadelphia, PA Sep. 15 Toronto, ON Sep. 22 Chicago, IL Sep. 29 New York, NY Oct. 6 Baltimore, MD Oct. 20 Philadelphia, PA Nov. 17 Miami, FL WWW.ITMPI.ORG / EVENTS

22. Arlo Belshee Founder Code Foundry a+caiwebinar@arlim.org • Michael Milutis • Director of Marketing • Computer Aid, Inc. (CAI) • Michael_milutis@compaid.com