Not everything that counts can be counted. Not everything that is counted counts. Albert Einstein This is a book about software measurement from the practitioner’s point of view and it is a book for practitioners. Software measurement needs a lot of practical guidance to build upon experiences and to avoid repeating errors. This book t- gets exactly this need, namely to share experiences in a constructive way that can be followed. It tries to summarize experiences and knowledge about software measurement so that it is applicable and repeatable. It extracts experiences and lessons learned from the narrow context of the specific industrial situation, thus facilitating transfer to other contexts. Software measurement is not at a standstill. With the speed software engine- ing is evolving, software measurement has to keep pace. While the underlying theory and basic principles remain invariant in the true sense (after all, they are not specific to software engineering), the application of measurement to specific contexts and situations is continuously extended. The book thus serves as a ref- ence on these invariant principles as well as a practical guidance on how to make software measurement a success.

“As projects get more complicated, managers stop learning from their - perience. It is important to understand how that happens and how to change it…. Fallible estimates: In software development, initial estimates for a project shape the trajectory of decisions that a manager makes over its life. For ex- ple, estimates of the productivity of the team members influence decisions about the size of the team, which in turn affect the team’s actual output. The trouble is that initial estimates usually turn out to be wrong. ” (Sengupta, 2008) This book aims directly to increase the awareness among managers and practitioners that estimation is as important as the work to be done in so- ware and systems development. You can manage what you can measure! Readers will find in this book a collection of lessons learned from the worldwide “metrics community,” which we have documented and enhanced with our own experiences in the field of software measurement and estimating. Our goal is to support our readers to harvest the benefits of estimating and - prove their software development processes. We present the 5 ISO/I- acknowledged Functional Sizing Methods with variants, experiences, counting rules, and case studies – and most importantly, illustrate through practical - amples how to use functional size measurement to produce realistic estimates. The book is written in a practical manner, especially for the busy practitioner community. It is aimed to be used as a manual and an assistant for everyday work.

“As projects get more complicated, managers stop learning from their - perience. It is important to understand how that happens and how to change it…. Fallible estimates: In software development, initial estimates for a project shape the trajectory of decisions that a manager makes over its life. For ex- ple, estimates of the productivity of the team members influence decisions about the size of the team, which in turn affect the team’s actual output. The trouble is that initial estimates usually turn out to be wrong. ” (Sengupta, 2008) This book aims directly to increase the awareness among managers and practitioners that estimation is as important as the work to be done in so- ware and systems development. You can manage what you can measure! Readers will find in this book a collection of lessons learned from the worldwide “metrics community,” which we have documented and enhanced with our own experiences in the field of software measurement and estimating. Our goal is to support our readers to harvest the benefits of estimating and - prove their software development processes. We present the 5 ISO/I- acknowledged Functional Sizing Methods with variants, experiences, counting rules, and case studies – and most importantly, illustrate through practical - amples how to use functional size measurement to produce realistic estimates. The book is written in a practical manner, especially for the busy practitioner community. It is aimed to be used as a manual and an assistant for everyday work.

Not everything that counts can be counted. Not everything that is counted counts. Albert Einstein This is a book about software measurement from the practitioner’s point of view and it is a book for practitioners. Software measurement needs a lot of practical guidance to build upon experiences and to avoid repeating errors. This book t- gets exactly this need, namely to share experiences in a constructive way that can be followed. It tries to summarize experiences and knowledge about software measurement so that it is applicable and repeatable. It extracts experiences and lessons learned from the narrow context of the specific industrial situation, thus facilitating transfer to other contexts. Software measurement is not at a standstill. With the speed software engine- ing is evolving, software measurement has to keep pace. While the underlying theory and basic principles remain invariant in the true sense (after all, they are not specific to software engineering), the application of measurement to specific contexts and situations is continuously extended. The book thus serves as a ref- ence on these invariant principles as well as a practical guidance on how to make software measurement a success.

“As projects get more complicated, managers stop learning from their - perience. It is important to understand how that happens and how to change it…. Fallible estimates: In software development, initial estimates for a project shape the trajectory of decisions that a manager makes over its life. For ex- ple, estimates of the productivity of the team members influence decisions about the size of the team, which in turn affect the team’s actual output. The trouble is that initial estimates usually turn out to be wrong. ” (Sengupta, 2008) This book aims directly to increase the awareness among managers and practitioners that estimation is as important as the work to be done in so- ware and systems development. You can manage what you can measure! Readers will find in this book a collection of lessons learned from the worldwide “metrics community,” which we have documented and enhanced with our own experiences in the field of software measurement and estimating. Our goal is to support our readers to harvest the benefits of estimating and - prove their software development processes. We present the 5 ISO/I- acknowledged Functional Sizing Methods with variants, experiences, counting rules, and case studies – and most importantly, illustrate through practical - amples how to use functional size measurement to produce realistic estimates. The book is written in a practical manner, especially for the busy practitioner community. It is aimed to be used as a manual and an assistant for everyday work.

“As projects get more complicated, managers stop learning from their - perience. It is important to understand how that happens and how to change it…. Fallible estimates: In software development, initial estimates for a project shape the trajectory of decisions that a manager makes over its life. For ex- ple, estimates of the productivity of the team members influence decisions about the size of the team, which in turn affect the team’s actual output. The trouble is that initial estimates usually turn out to be wrong. ” (Sengupta, 2008) This book aims directly to increase the awareness among managers and practitioners that estimation is as important as the work to be done in so- ware and systems development. You can manage what you can measure! Readers will find in this book a collection of lessons learned from the worldwide “metrics community,” which we have documented and enhanced with our own experiences in the field of software measurement and estimating. Our goal is to support our readers to harvest the benefits of estimating and - prove their software development processes. We present the 5 ISO/I- acknowledged Functional Sizing Methods with variants, experiences, counting rules, and case studies – and most importantly, illustrate through practical - amples how to use functional size measurement to produce realistic estimates. The book is written in a practical manner, especially for the busy practitioner community. It is aimed to be used as a manual and an assistant for everyday work.