Difference between revisions of "Pair working"
Jump to navigation
Jump to search
(Joined at the hip with {{p|swarm the issue}} and {{p|andon cord}}.) |
m (all) |
||
| Line 1: | Line 1: | ||
{{Oyster | {{Oyster | ||
|goal=spread knowledge while being productive and collectively own the product | |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 | ||
Revision as of 09:14, 16 June 2013
…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.