Difference between revisions of "Pair working"
Jump to navigation
Jump to search
m (terse/full) |
(+= {{quote|Pair programming strategy isn’t “go faster”, it’s “waste less” (which often results in going faster)|@KentBeck}}) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=spread all knowledge while being productive and collectively own the product | |||
|stage=Sparkle | |stage=Sparkle | ||
|theme=Agile, Lean, Extreme Programming | |theme=Agile, Lean, Extreme Programming | ||
|context=joint venture. | |context=joint venture. | ||
| | |wish=Be independent of a single person by knowledge spreading and collective ownership. | ||
|so=Pair up in a master apprentice way. Or just pair. | |so=Pair up in a master apprentice way. Or just pair. | ||
|wish full=Be independent of a single person by knowledge spreading and collective ownership. | |wish full=Be independent of a single person by knowledge spreading and collective ownership. | ||
| Line 13: | Line 14: | ||
If one dies, the other can take over. If you want to leave (e.g. for another company) and leave your knowledge behind, you can do so because the other one can take over. | If one dies, the other can take over. If you want to leave (e.g. for another company) and leave your knowledge behind, you can do so because the other one can take over. | ||
|therefore full=Pair up in a master apprentice way. Or just pair. | |therefore full=Pair up in a master apprentice way. Or just pair. | ||
|new=Joined at the hip with {{p|swarm the issue}} and {{p|andon cord}}. | |||
}} | }} | ||
{{quote|Pair programming strategy isn’t “go faster”, it’s “waste less” (which often results in going faster)|Kent Beck}} | |||
==Sources== | ==Sources== | ||
*{{web|url=http://www.infoq.com/articles/agile-lean-mindset|site=InfoQ|title=Interview with Yves Hanoulle on the Agile and Lean Mindset}} | *{{web|url=http://www.infoq.com/articles/agile-lean-mindset|site=InfoQ|title=Interview with Yves Hanoulle on the Agile and Lean Mindset}} | ||
*See Joe Justice's project wikispeed, 06:45, share all the knowledge while working without them having to up-train someone afterwards. | |||
{{WebSourceListItem | |||
|url=https://www.infoq.com/articles/pair-programming-no-panacea | |||
|site=InfoQ | |||
|person=Wes Higbee | |||
|title=Pair Programming is no Panacea | |||
}} | |||
{{Source}} | {{Source}} | ||
Latest revision as of 13:32, 9 June 2016
…joint venture.
✣ ✣ ✣
Be independent of a single person by knowledge spreading and collective ownership.
Pair working is done by:
- policemen; and
- pilots;
- television and radio presenters often have a sidekick
- product owner and scrum master.
If one dies, the other can take over. If you want to leave (e.g. for another company) and leave your knowledge behind, you can do so because the other one can take over.
Therefore:
Pair up in a master apprentice way. Or just pair.
✣ ✣ ✣
Joined at the hip with swarm the issue and andon cord.
✣ ✣ ✣
- Pair programming strategy isn’t “go faster”, it’s “waste less” (which often results in going faster)
Sources
- See Joe Justice's project wikispeed, 06:45, share all the knowledge while working without them having to up-train someone afterwards.
- InfoQ » Wes Higbee » Pair Programming is no Panacea