|I find the 'pair programming' item most frightening, not because I'm scared of pair programming, but because of the prerequisites for that item to occur and its most likely outcome:
You can see the obvious outcome for the company. Since I would have been fired in the last step, I would not care.
- Engineering management (dominated by former mechanical engineers) is paying far too much attention to just how the golden goose lays those eggs.
- Management has decided we need to be 'Agile'.
- Management has hired a highly-paid consultant who recommends pair programming as a first step.
- The most productive members of the team are paired with new, 'already-agile' hires.
- The new hires haven't the slightest clue as to how their blithely refactoring those interfaces affects existing products.
- As an end result, all forward progress screeches to a halt, and the customer complaint data base balloons.
- The consultant blames existing team members for their poor adoption of the agile practices.
- All existing team members are terminated 'for cause', which means no termination benefits.
modified 1-Nov-16 9:40am.