Software development is subject to risks as soon as it is bound by fixed, contractually agreed conditions; conditions such as delivering a defined scope of functions at a fixed price and by an agreed delivery date. Many of these risks can be mitigated by the principles of agile software development. Planning and controlling to navigate development projects within these parameters also requires methods for effort estimation. To ensure that these do not diminish the advantages of agile development, they must be quickly applicable, ideally automatable, and self-calibrating after each sprint. This book describes how scope metrics can be effectively used in practice within an agile values-oriented software development framework, what differences and limitations exist, how the accuracy of effort estimates can be increased with each sprint, and how automated measurements are possible.