3 ms·
The part about Extreme Programming not being for everyone and the recommendation to not force it are good, but they’re a small part of the article. I think the
by Aurornis 2y ago
The part about Extreme Programming not being for everyone and the recommendation to not force it are good, but they’re a small part of the article.
I think the most important consideration is to match development practices to the team and to accept that people have different preferences. This author’s preference is clearly for XP practices, but I see little acknowledgement that it’s a personal preference amid the bolded declarations that it’s incredible. The entire article is about convincing people to give it a try with little acknowledgement that maybe the team is right to reject it for their style and working preferences.
I’ve had several managers try to impose forced pairing over the years. Every time, a couple people really like it but everyone else is put on a path to burnout and leaving the company.
XP style practices (pairing, TDD, commit frequency) are also not a good match for certain types of development. If you’re pushing small pieces of a CRUD app and website around then having everyone commit frequently and work “at the speed of conversation” can make sense. If the team is doing complex work that requires deep trains of thought and intense focus over several days then forcing XP principles arbitrarily will not have good results. I last encountered this when a company reassigned a full-stack web dev manager to oversee some developers doing complex low-level work that spanned multiple systems. You could feel the seething rage as the manager demanded that everyone should be checking in releasable code multiple times a day and doing the TDD dance. His entire career was doing simple web apps and he couldn’t understand why we couldn’t just kick out incrementally complete commits every few hours for our complex systems work. Again, it set people up for burnout and quitting.