Business users and engineers should sit together

So engineers solve the business problem directly, instead of a ticket that describes it.

Software should speak the language of the business

When it knows what a claim, an order or an exception means, its agents act instead of guessing.

Software should start from the rules the business lives by

A regulator, a two-week close and a core you can't replace go into the design on day one.

Software should do the next step itself

A system that only records what happened is a filing cabinet. People should decide, and agents should do the rest.

Every system should fit the ones around it

Built from one blueprint, the fourth system costs less than the first.

Software should get better every time it's built

The process that builds software is software too, so every build makes the next one faster.

Software should be judged by what it changes

If people don't use it, or it doesn't move the goal it was built for, it isn't done.

Software should keep changing with the business

What we learn from running it decides what we build next.