docs: adopt and fade out mob programming

This commit is contained in:
Stefan Rotsch
2024-06-21 17:24:37 +02:00
committed by Stefan Rotsch
parent 5eef6c0b8d
commit 0523bcacf9
4 changed files with 23 additions and 18 deletions

View File

@@ -2,10 +2,13 @@
title: "Pair Working"
ring: trial
quadrant: methods-and-patterns
tags: [agile, coding, devops]
---
We summarized the practices of pair programming and administrating as pair working.
We have summarized the practices of pair programming and administrating as pair working.
Derived as a practice from eXtreme Programming (XP), pair programming is a method/pattern that aims for fine-scaled feedback within a team.
Derived as a practice from eXtreme Programming (XP), pair programming is a practice that aims for fine-grained feedback within a team.
At AOE, some developers and operators work in pairs, not constantly, but from time to time. Most teams have positive experiences using this method, but not all teams tried the by-the-book-approach (driver and navigator principle). Especially for non-trivial tasks, pair working results in rapid knowledge exchange and better results with fewer bugs. We encourage the teams to try this approach more often.
At AOE, some developers and operators work in pairs, not constantly, but from time to time. Most teams have positive experiences using this method, but not all teams have tried the by-the-book approach (e.g., driver/navigator pattern). Especially for non-trivial tasks, pair working leads to rapid knowledge sharing and better results with fewer bugs. We encourage the teams to try this approach more often.
By incorporating pair working into regular routines, teams can improve collaboration and boost productivity. In addition, this practice can help foster a culture of continuous learning and mutual support within the organization.