Ping-pong programming (P3) is an offspring of two well-known extreme programming practices: pair programming and test-driven development. These practices by themselves promote intra-team knowledge sharing. One of the major issues preventing effective pairing is passivity. When used simultaneously with test-driven development, it encourages more frequent switching of roles: one programmer writes a failing unit test, then passes the keyboard to the other who writes the corresponding code, then goes on to a new test.
Showing posts with label Pair Programing. Show all posts
Showing posts with label Pair Programing. Show all posts
Friday, July 25, 2014
Ping Pong Programming
Saturday, August 31, 2013
Fighting Poor Practice - Go Pair Programing
Pair or collaborative programming is where two programmers
develop software side by side at one computer. This practice has been nominated
several times in the last decades as an improved way of developing software.
Why ? Because the end defect content is statistically lower; Programmers solve
problems faster; They are more satisfied ;They learn good techniques and habits
and many more...
תוויות:
Agile,
Agile Practices,
Pair Programing
Subscribe to:
Posts (Atom)
