What Kills Agility?
Why Agile if you already do Scrum, Kanban or SAFe? How you manage an organization defines its quality, and what really kills it.
Extreme Programming: pairing, TDD, and continuous everything.

Why Agile if you already do Scrum, Kanban or SAFe? How you manage an organization defines its quality, and what really kills it.

A practical guide to pair programming that works: roles, rotation, when to pair, common pitfalls, and how to make sessions productive.

The panic around deploying on Fridays. Does banning a whole day of delivering value to your customers actually make sense?

From my talk at the WeAreDevelopers World Congress: my experience with Extreme Programming and the benefits of embracing change.

My interview with devm.io regarding Agile and Extreme Programming. Agile is more about HOW you do certain things, rather than WHAT things you do.

You apply the extreme programming values and practices. So how do you work with the teams around you that are not agile?

What to do when working on "bad software" and you can't improve it because it is against the beliefs of your peers? Should you change the company?

Uncle Bob on the three pillars of craftsmanship: TDD disciplines with examples, standards for teams, and a programmer's ethics.

Software demands non-stop learning. How to create the spaces your team needs to leave the comfort zone and embrace change.

Kent Beck on XP, the most specific agile framework about engineering practice, and how it raises software and team quality.
Embracing change is not optional in software. How to create the spaces your team needs to leave the comfort zone and keep learning.