This line was removed.
This word was removed. This word was added.
This line was added.
Changes (1)View Page History
_Peer_ programming might be considered an extreme version of this practice. The [Definition of DONE! 10 Point Checklist | http://www.agile-software-development.com/2007/07/definition-of-done-10-point-checklist.html] (external content is gone..) seems like a good starting point for defining DoD. Note that that this they accept _pair_ programming as "enough" for done. Pair programming is only that two people is programming together, while peer entails that the two are at equal competence level. Peer programming is a lot better for QA than pair programming, while both support knowledge transfer. We would thus suggest that _peer_ programming automatically entails acceptance of the produced code, while _pair_ does not.