This document discusses specification by example, a technique where examples are used to specify requirements, enable acceptance testing, and serve as documentation. It recommends writing examples one iteration ahead, a few days before planning, during planning, and inside iterations. It provides tips for how to write good examples, such as finding missing concepts, using domain language, selecting a suitable format, including only key examples, and getting feedback. It also distinguishes between software and business models and test design versus software design. Additionally, it outlines an effect mapping technique to link business goals to stakeholder activities and epics.