Difference between revisions of "Pair working"
Jump to navigation
Jump to search
m (all) |
(+= InfoQ » Wes Higbee » Pair Programming is no Panacea) |
||
| Line 21: | Line 21: | ||
*See Joe Justice's project wikispeed, 06:45, share all the knowledge while working without them having to up-train someone afterwards. | *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}} | ||
Revision as of 13:29, 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.
✣ ✣ ✣
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