Ron Jeffriesperson

manifesto-signatoryextreme-programmingxpcoaching
2 min read · Edit on Pyrite

Ron Jeffries is a co-creator of extreme-programming (with kent-beck and ward-cunningham) and a signatory of the agile-manifesto at snowbird-meeting-2001. He was the first XP coach on the C3 project (Chrysler Comprehensive Compensation System) — the project that served as the original proving ground for XP as a complete methodology.

The C3 Project

The C3 project at Chrysler is XP's origin story. Jeffries served as the on-site coach, working alongside Kent Beck (who had been brought in as a consultant) to apply and develop the XP practices. C3 was eventually cancelled, and the project's history — including whether it ultimately succeeded — became a point of contested interpretation in the XP literature. Jeffries remained candid about C3's mixed outcome, distinguishing what the practices produced from what organizational forces ultimately decided.

Key Intellectual Contributions

Jeffries was instrumental in developing and teaching XP practices in a coaching context — translating Beck's framework into day-to-day practice on a real project. His role was primarily that of practitioner and coach rather than theorist, which gave his writing a practical grounding.

Later critical stance on Scrum — One of Jeffries' most notable contributions to post-Agile discourse was his publicly stated regret about the way Scrum had developed. He wrote critically about "Dark Scrum" — the phenomenon of Scrum being used to pressure developers while stripping out the technical practices. He argued that Scrum without the XP engineering practices was actively harmful to developers.

Key Works

  • "Extreme Programming Adventures in C#" (2004) — a practitioner account of applying XP in a Microsoft C# context, notable for its transparency about difficulties
  • Prolific blogger at ronjeffries.com, writing into the 2020s on XP, Scrum criticism, and post-agile-era themes
  • Movement Role

    Jeffries is a signatory who bridged practice and advocacy. His honest accounting of C3's difficulties, and his later willingness to criticize dark-agile patterns in Scrum adoption, gave him a distinct voice in the post-Agile discourse. His criticism of scrum without engineering practices aligned with a broader argument that extreme-programming's technical discipline had been the casualty of Scrum's organizational dominance. He was associated with agile-alliance and remained active in the community through the post-agile-era.