Usually tools used for requirements, coding, code review, testing and change management and project management, have built-in reports. These are useful for understanding the status and issues in a project in a timely manner. These may require customization to conform to the specifics of process followed by the organization. If the tools are not integrated, consolidation of metrics requires additional effort and possibly use of spreadsheets again with their inherent advantages and disadvantages. Software analytics is a good alternative when the tools are not integrated.
Open source communities are leveraging tools like MetricsGrimoire (See sample figure above from Dashboard of Wikimedia Development Community) to mine repositories associated with configuration management, bug tracking and mailing list for projects and extract useful metrics and present them visually for analysis and action. These metrics are useful to identify top contributors, aging of artifacts, velocity of development as well as provide insight into issues.
What is the level of non spreadsheet tools usage in your organization? How much time is spent in generating the metrics? Is there an opportunity to deploy additional tools, deploy software analytics tools and develop automation scripts to extract metrics? These are all valid questions which can lead to improved productivity and project success.