ZeroBlockers vs Extreme Programming (XP)

In Ron Jeffries’ description of XP, the Customer works with the team, sets priorities, and steers through small releases and acceptance tests. XP puts business judgment inside the team, and Kent Beck’s second edition even names contract practices such as negotiated scope contracts. It does not say how much authority the Customer holds outside the team, or who changes a commitment when evidence contradicts it.

Without that, the Customer is often a business representative. They can order the backlog, but they usually cannot change a contract, stop a funded feature, or overrule a promise sales made to a client. When customer evidence contradicts one of those commitments, the team waits while the representative finds the person who can decide.

Under the ZeroBlockers alignment change, the Product Team, the leadership group for the product, owns strategy and commercial conflicts. A Stream Team, a small, persistent team that owns one part of the customer journey, chooses its solutions within agreed targets. It takes anything outside its authority straight to the Product Manager. When evidence drops a feature a stakeholder wanted, the Product Manager explains the decision to them. The XP Customer’s job splits: the team makes solution decisions, and the Product Manager owns commitments outside the team.

XP gets feedback through small releases and a Customer on the team. It leaves open how the team learns what customers actually do. An acceptance test shows the software follows an agreed rule. A new checkout flow can calculate every price correctly while fewer travelers complete a booking.

ZeroBlockers puts research and outcome checks into the same team’s work. Designers and developers watch customers, test assumptions, and look at live behavior. The Product Team agrees targets such as completed bookings, paired with a second measure such as cancellations to catch harmful side effects.

The team changes the solution as evidence arrives, within its funded scope, and runs the next test without waiting for permission. The Weekly Product Review looks at the decisions it has already made. AI speeds up the code, and regular time with customers makes sure that speed goes into the right changes.

XP’s testing, pairing, continuous integration, refactoring, and collective code ownership make frequent change safe. A ZeroBlockers team needs the same practices, with pairing extended to the whole team. Authority to release is worth little if every release is risky or only one person understands the code.

Enabling Teams, senior specialists who coach the teams, help build missing skills. An Internal Product Team runs a shared self-service capability, such as deployment or monitoring. The Stream Team still owns its own changes in production.