PP = fast developing + less error/bugs

Concept?

Disadvantages?

Print Friendly, PDF & Email
Swipe to start

PP is simple:

+ 2 persons sitting/standing in front of 1 computer/notebook

+ developing together code to which everyone has access at every time

Print Friendly, PDF & Email
Computer-Maus

Computer-Maus

It’s about developing ideas together, not who is developing which part!

Print Friendly, PDF & Email

cross-functional teams = shared knowledge

PP combinations:

+ developer | developer
+ developer | graphic designer
+ developer | usability designer
+ developer | …

Goal: having better, bug free and clean code at the end

Print Friendly, PDF & Email

duo teams are not writing code twice as much as a single person

BUT: they are more efficient and faster
BECAUSE: of less bugs, less technical meetings, less documentation, …

Print Friendly, PDF & Email

only 1 developer writes the code
but has to explain

+ corrects code while drafting
+ gets immediate feedback from the second person

Print Friendly, PDF & Email

-> more errors occur before
-> chance to get second approach to solving a problem

no one is working on its own anymore!

Print Friendly, PDF & Email

Start

  • Pair Programming is
  • 2 DEVs, 1 PC
  • 2 Mouses, 2 Screens, 1 Keyboard
  • X-functional Team
  • Dynamic Duo
  • 1 Coder
  • Not alone
Share Tweet
Pair Programming