One

Stakeholders should provide information in a timely manner, make decisions in a timely manner, and be as actively involved in the development process through the use of inclusive tools and techniques.

Two

At the beginning of an agile project you will need to do some initial, high-level architectural modeling to identify a viable technical strategy for your solution.

Three

Write deliverable documentation throughout the lifecycle in parallel to the creation of the rest of the solution.

Four

Write deliverable documentation as late as possible, avoiding speculative ideas that are likely to change in favor of stable information.

Five

Specify requirements in the form of executable "customer tests", and your design as executable developer tests, instead of non-executable "static" documentation.

Six

At the beginning of each iteration you will do a bit of modeling as part of your iteration planning activities.

Seven

Just Barely Good Enough (JBGE) artifacts would point towards a model or document needs to be sufficient for the situation at hand and no more.

Eight

Sometimes requirements that are nearing the top of your priority stack are fairly complex, motivating you to invest some effort to explore them before they're popped off the top of the work item stack so as to reduce overall risk.

Nine

Throughout an iteration you will model storm on a just-in-time (JIT) basis for a few minutes to explore the details behind a requirement or to think through a design issue.

Eleven

Agile teams implement requirements in priority order, as defined by their stakeholders, so as to provide the greatest return on investment (ROI) possible.

Fourteen

Write a single test, either at the requirements or design level, and then just enough code to fulfill that test. TDD is a JIT approach to detailed requirements specification and a confirmatory approach to testing.