Back tostdlib
blog post
New

Overcoming Resistance to Extreme Programming

The article examines why developers and managers resist Extreme Programming, highlighting common misconceptions and organizational incentives, and offers guidance on addressing these challenges.

Overview
The post explores the sources of resistance to Extreme Programming (XP) from developers, management, systems, and tools. It identifies common misconceptions, such as the belief that XP is chaotic or overly prescriptive, and points out how incentive structures can undermine collaborative practices.
Key Takeaways

  • Misunderstandings about XP often stem from lack of experience and poor communication.
  • Management may verbally support collaboration but enforce metrics that discourage it.
  • Systems and tooling must align with XP practices to be effective.
  • Addressing resistance requires education, clear goals, and supportive incentives.
    Who Would Benefit
  • Engineering managers seeking to adopt XP or agile practices.
  • Team leads who face pushback from developers.
  • Developers interested in collaborative development methods.
  • Organizational leaders aiming to improve software delivery culture.
    Frameworks and Methodologies
  • Extreme Programming (XP)
  • Agile development
Source: benjiweber.co.uk
#technical leadership#engineering management#extreme programming#agile#software engineering#team collaboration

Explore more resources

Check out the full stdlib collection for more frameworks, templates, and guides to accelerate your technical leadership journey.