Pair Programming: Good, Bad and Ugly

  • 3,701 views
Uploaded on

Presentation accompanying workshop for OOP Conference 2012

Presentation accompanying workshop for OOP Conference 2012

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,701
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
66
Comments
2
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Pair Programming The Good, the Bad and the Ugly Ken Fassone @nexusventuri Pat Kua @patkua
  • 2. TageskarteIntroduction to pair programmingDemonstrationRoles we identifiedPairing WorkshopQ&A
  • 3. Introduction
  • 4. RolesIntroduction
  • 5. Roles BenefitsIntroduction
  • 6. Roles Benefits PatternsIntroduction
  • 7. What is pair programming?
  • 8. Driver
  • 9. Driver Navigator
  • 10. Benefits
  • 11. Continuous feedback Benefits
  • 12. Continuous feedback Benefits Merged ideas
  • 13. Continuous feedback Benefits Merged ideasKnowledge spreading
  • 14. Continuous feedback More Focus Benefits Merged ideasKnowledge spreading
  • 15. Continuous feedback More Focus Benefits Merged ideas Better codeKnowledge spreading
  • 16. Continuous feedback More Focus Benefits Merged ideas More consistency Better codeKnowledge spreading
  • 17. Demonstration
  • 18. Roman numbers kataDemonstration
  • 19. Roman numbers kata Behaviour demonstrationDemonstration
  • 20. Roman numbers kata Behaviour demonstration (good, bad and ugly...)Demonstration
  • 21. Demonstration
  • 22. Good Ugly BadRoles
  • 23. “Characteristics people should do less of (but aren’t so much of a problem)...”Bad Roles
  • 24. Alpha male
  • 25. Bunny
  • 26. Rodolfo Valentino
  • 27. “Characteristics people should stop immediately”Ugly Roles
  • 28. Monk
  • 29. Puppet master
  • 30. Auditor
  • 31. “Characteristics people should continue/do more of...”Good Roles
  • 32. Mentor
  • 33. Moleskine
  • 34. Captain
  • 35. Pairing Workshop
  • 36. 1. Form groups of 3 (navigator, driver + observer)Pairing Workshop
  • 37. 1. Form groups of 3 (navigator, driver + observer)2. Navigator and driver (secretly) choose a rolePairing Workshop
  • 38. 1. Form groups of 3 (navigator, driver + observer)2. Navigator and driver (secretly) choose a role3. Navigator and driver make a story using all the wordsPairing Workshop
  • 39. 1. Form groups of 3 (navigator, driver + observer)2. Navigator and driver (secretly) choose a role3. Navigator and driver make a story using all the words4. Observer observes (5 minutes) and suggests improvementsPairing Workshop
  • 40. 1. Form groups of 3 (navigator, driver + observer)2. Navigator and driver (secretly) choose a role3. Navigator and driver make a story using all the words4. Observer observes (5 minutes) and suggests improvements5. After 10 minutes you switch rolesPairing Workshop
  • 41. Write a story that includes these words... Round 1
  • 42. Write a story that includes these words... Round 1 Airplane Protect Teach Minute Parrot Chemical Delay Cracker
  • 43. Write a story that includes these words... Round 2
  • 44. Write a story that includes these words... Round 2 Pink Food Running War Rule Tea Sea Wolf
  • 45. Write a story that includes these words... Round 3
  • 46. Write a story that includes these words... Round 3 Off Cousin Christmas Desert Rubbish Visit Karaoke Morning
  • 47. How to improve
  • 48. Encourage conversationHow to improve
  • 49. Encourage conversationHow to improve Double everything
  • 50. Encourage conversation How to improveIntroduce post-its Double everything
  • 51. Encourage conversation How to improve Introduce post-its Double everythingPing-pong or pomodoro
  • 52. Standard environment Encourage conversation How to improve Introduce post-its Double everythingPing-pong or pomodoro
  • 53. Pairing (well) is a skillWhy it matters
  • 54. Pairing (well) is a skill Skills take time to developWhy it matters
  • 55. Pairing (well) is a skill Skills take time to developConscious awareness is the first step to being betterWhy it matters
  • 56. Q&AKen Fassone @nexusventuri Pat Kua @patkua http://www.thoughtworks.com/current-opportunities We’re hiring!